Drive one simulated authorization against a named card
/v1/simulated-spendsRequires an API client bearer token.
Drives one simulated authorization against a card the operator issued and funded, over the same wire path a real network would use. The caller passes a card id, never a PAN — the PAN is resolved server-side against a single-use grant and never returned. NOT idempotency-keyed: each accepted call is a deliberately distinct wire transaction (press twice = two payments); the console disables the button while a request is in flight instead. Returns 202 with an acceptance handle plus the wire identity (stan/rrn, null only when the simulator leg failed before a message was built) — the decision itself is queryable via GET /v1/simulated-spends/{id} and arrives asynchronously as an authorization.decided event. A simulator-leg failure is recorded and reported through that same GET endpoint rather than surfacing as an error response here.
Request body
+ show properties− hide properties
+ show properties− hide properties
Non-negative canonical decimal, at most 16 integer digits. Fractional digits must not exceed the minor-unit precision of `currency` (2 for EUR/GBP/USD), because the amount has to be representable in ISO 8583 DE4.
Example
curl -X POST https://api.rigid.fi/v1/simulated-spends \
-H "Authorization: Bearer $RIGID_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"card_id": "string",
"amount": {
"amount": "string",
"currency": "EUR"
},
"mcc": "string",
"merchant_name": "string",
"channel": "pos"
}'Responses
202The simulated spend was accepted for transmission.
400Validation error
401Authentication required
403Forbidden
404Card not found
409Card is not active
500Internal server error