Submit Simulator Authorization
POST/api/simulator/authorize
This endpoint can be used to test authorizing a transaction on a simulated card network.
Incremental Authorization
Create an initial authorization then include the requestMsg
from this
response in the request body of a subsequent authorization.
Force Post
In some scenarios a merchant will force an authorization to be accepted. This is
known as force post or force sale. This functionality supports offline
authorizations. To simulate this scenario, set the forcePost
field to true
in your request payload.
Request
- application/json
Body
required
Possible values: [purchase
, refund
]
Transaction type.
Transaction amount as an integer in the smallest denomination of the currency.
Default value: USD
ISO 4217 currency code.
Possible values: Value must match regular expression ^[0-9]{16}$
Card number.
Possible values: Value must match regular expression ^[0-9]{6}$
Card expiry in YYYYMM format.
Possible values: Value must match regular expression ^[0-9]{3}$
Card CVV.
requestMsg of previous authorization returned by this endpoint.
Indicates whether to force post the transaction.
Responses
- 200
- 400
- 403
- application/json
- Schema
- Example (from schema)
Schema
XML formatted ISO 8583 message sent to the simulated card scheme
XML formatted ISO 8583 message returned from the simulated card scheme
ID of the transaction
{
"requestMsg": "string",
"responseMsg": "string",
"transactionId": 0
}
Request fields are invalid
- application/json
- Schema
- Example (from schema)
Schema
{
"statusCode": 400,
"statusName": "Bad Request",
"errorCode": "BAD_REQUEST",
"errors": [
"Expected string, received number"
]
}
No Authorization to access resource.
- application/json
- Schema
- Example (from schema)
Schema
{
"statusCode": 403,
"statusName": "Forbidden",
"errorCode": "FORBIDDEN",
"reason": "Unauthorized"
}