Card Transactions
Simulate authorization, decline, settlement, and reversal scenarios in the Core sandbox.
Use these test cases to validate how your integration handles card transaction events — approvals, declines by reason, withdrawals, partial settlements, reversals, refunds, and reconciliation.
This page is a sandbox scaffold. The full version will include deterministic test cases (specific test card numbers or amounts that trigger each scenario) for every event type in the card transaction webhook catalog.
Test scenarios
| Scenario | Description | Test case |
|---|---|---|
| Authorization approved | The card transaction is authorized and the balance is charged. | To be documented |
| Authorization declined — insufficient funds | The transaction is declined because the account balance is too low. | To be documented |
| Authorization declined — fraud | The transaction is declined due to a fraud flag. | To be documented |
| Authorization declined — limit exceeded | The transaction is declined because a spending limit is reached. | To be documented |
| Withdrawal | An ATM withdrawal is authorized, including the withdrawal_fee. | To be documented |
| Partial settlement (credit adjustment) | An authorized amount is partially refunded at settlement. | To be documented |
| Debit adjustment | The authorized amount is increased at settlement. | To be documented |
| Reversal | An authorization is fully reversed and the charge is returned. | To be documented |
| Refund | A refund is issued to the account. | To be documented |
| Reconciliation | The settled amount differs from the authorized amount after final network settlement. | To be documented |
Next steps
- Card transaction webhooks — the event payloads fired for each scenario above.
- Cards — set up a sandbox card before running transaction scenarios.