Simulate
The simulate endpoints are used for testing authorizations and captures
Simulate Authorization
A merchant authorization can be simulated which affects the available balance on the deposit account. The transaction does not post until simulate/capture is called using the referenceId and cardId returned from simulating an authorization.
POST /debitcards/v1/simulate/authorization
{
"cardId": "00000000-0000-0000-0000-000000000000",
"amount": 100,
"merchantCountryCode": "US",
"merchantName": "ACME CO",
"merchantAddress": "123 Main Street",
"merchantCity": "New York",
"merchantState": "NY",
"merchantZip": "10025"
}
{
"referenceId": 123,
"cardId": "00000000-0000-0000-0000-000000000000"
}
Simulate Capture
Posting the referenceId returned by the authorization endpoint completes the transaction and posts the transaction to the deposit account activity.
POST /debitcards/v1/simulate/capture
{
"cardId": "00000000-0000-0000-0000-000000000000",
"referenceId": 123
}
Simulate Reversal
Posting the referenceId returned by the authorization endpoint reverses the transaction and removes it from the deposit account activity.
POST /debitcards/v1/simulate/reversal
{
"cardId": "00000000-0000-0000-0000-000000000000",
"referenceId": 123,
"amount": 123
}
Simulate Reconcile
Simulates activity settlement process to finalize transaction activity.
POST /debitcards/v1/simulate/reconcile
{
"partnerId": "00000000-0000-0000-0000-000000000000"
}
Updated over 2 years ago