Scenario 20: Card Load Reversal (Maestro)
A cardholder receives $225 from a grocery-delivery company at the end of a shift, but an error on the company's side causes the funds to be reversed a minute later. The following are true:
- The initial available balance is $1000.
- The network is Maestro.
Sequence of events
Events in the same step have the same timestamp.
- Maestro sends a card-load authorization request for 225.00 over network rails.
- Galileo approves the authorization and sends the
AAPM: auth_paymentevent message. Galileo then converts the transaction into a payment, posts 225.00 to the account, and sends theBPMT: pmtevent message. The available balance is now 1225.00. - Maestro sends a card load reversal request for -225.00 over network rails.
- Galileo approves the request, converts the transaction to an adjustment, posts -225.00 to the account and sends the
BADJ: adjevent message. The available balance is now 1000.00.
Transactions
These tables show how the transactions are represented by various Galileo systems. For an explanation of the trans_code field, see Classifying transactions in the About Transactions guide.
Auth API
| auth_type | transaction_type | trans_amount | auth_id | original_id | available_funds | timestamp |
|---|---|---|---|---|---|---|
| Auth | Payment | 225.00 | 1122 | 0 | 1000 | 20230127:000528MST |
| Reversal | Payment | 225.00 | 1123 | 0 | 1225 | 20230127:000529MST |
Authorization/Settlement Events
| msg_id | type | amount | auth_id | source_id | original_auth_id | open_to_buy | timestamp |
|---|---|---|---|---|---|---|---|
| AAPM | auth_payment | 225 | 1122 | 0 | 1000 | 2023-01-27 00:05:28 MST | |
| BPMT | pmt | 225 | 6600 | 0 | 1225 | 2023-01-27 00:05:28 MST | |
| BADJ | adj | 225 | 8899 | 0 | 1000 | 2023-01-27 00:05:29 MST |
Authorized Transactions RDF
The reversal amount is expressed as a positive number even though it's the reversal of a deposit.
| TRANSACTION AMOUNT | AUTHORIZATION CODE | TRANSACTION CODE | REVERSAL ID | TRANSACTION DATE/TIME |
|---|---|---|---|---|
| 225.00+ | 1122 | 28 | 0 | 2023-01-27 0:05:28 |
| 225.00+ | 1123 | 28 | 0 | 2023-01-27 0:05:29 |
Posted Transactions RDF
| TRANSACTION AMOUNT | AUTHORIZATION CODE | TRANSACTION CODE/TYPE | SOURCE ID | TRANSACTION DATE/TIME | POST DATE |
|---|---|---|---|---|---|
| 225.00+ | 6600 | PMMX | 6600 | 2023-01-270:05:28 | 2023-01-27 00:05:28 |
| 225.00- | 8899 | ADMX | 8899 | 2023-01-27 0:05:29 | 2023-01-27 00:05:29 |
Get Authorization History response
The transactions are not returned by this endpoint.
Get Transaction History response
This endpoint returns only settled transactions. These transactions are also returned by Get Account Overview.
| amt | source_id | original_auth_id | trans_code | auth_ts | post_ts |
|---|---|---|---|---|---|
| 225 | 6600 | 0 | PMMX | 2023-01-27 00:05:28 | 2023-01-27 00:05:28 |
| -225 | 8899 | 0 | ADMX | 2023-01-27 00:05:29 | 2023-01-27 00:05:29 |
Get All Transaction History response
This endpoint returns the same transactions as the All Transactions screen of the CST.
| amt | auth_id | prior_id | trans_code | source_id | calculated_balance | credit_ind | auth_ts | post_ts |
|---|---|---|---|---|---|---|---|---|
| 225 | 1122 | 0 | PMMX | 6600 | 1225 | None | 2023-01-27 00:05:28 | 2023-01-27 00:05:28 |
| -225 | 1123 | 0 | ADMX | 8899 | 1000 | None | 2023-01-27 00:05:29 | 2023-01-27 00:05:29 |