Scenario 1: Authorization with Settlement
A debit cardholder goes to a restaurant and the meal totals $45. The cardholder adds a $10 tip to the receipt. The following are true:
- The initial available balance is $1000.
- The merchant uses a signature to validate the debit card.
- The network is Mastercard Banknet.
Sequence of events
Events in the same step have the same timestamp.
- Mastercard sends a preauthorization request for –45.00.
- Galileo approves the request and places a 45.00 hold on the account. The available balance is now 955.00. Galileo sends a
BAUT: authevent message. - Mastercard sends a batch file with the –55.00 transaction.
- Galileo backs out the 45.00 hold and posts –55.00 to the account. The available balance is now 945.00. Galileo sends a
SETL: setlevent message.
Note
Because the settlement amount is higher than the preauthorization amount, there is a risk that the tip could drive the account negative. See Upcharges in the Authorization guide for a way to mitigate this risk.
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 | Preauth | 45.00 | 8877 | 0 | 1000.00 | 20210411:000435MST |
Authorization/Settlement Events
| msg_id | type | amount | auth_id | original_auth_id | open_to_buy | timestamp |
|---|---|---|---|---|---|---|
| BAUT | auth | 45 | 8877 | 0 | 955 | 2021-04-11 00:04:35 MST |
| SETL | setl | 55 | 8877 | 0 | 945 | 2021-04-12 10:32:04 MST |
Authorized Transactions RDF
| TRANSACTION AMOUNT | AUTHORIZATION CODE | TRANSACTION CODE | REVERSAL ID | TRANSACTION DATE/TIME |
|---|---|---|---|---|
| -45.00 | 8877 | 5 | 0 | 2021-04-11 00:04:35 |
Posted Transactions RDF
| TRANSACTION AMOUNT | AUTHORIZATION CODE | TRANSACTION CODE/TYPE | SOURCE ID | TRANSACTION DATE/TIME | POST DATE |
|---|---|---|---|---|---|
| -55.00 | 8877 | SE5 | 8877 | 2021-04-11 00:04:35 | 2021-04-12 10:32:04 |
Get Authorization History response
This endpoint returns only transactions that have not settled or expired. These transactions are also returned by Get Account Overview.
| amt | auth_id | original_auth_id | type | local_amt | timestamp |
|---|---|---|---|---|---|
| -45 | 8877 | 0 | L | 000000004500 | 2021-04-11 00:04:35 |
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 |
|---|---|---|---|---|---|
| -55 | 8877 | 0 | SE5 | 2021-04-11 00:04:35 | 2021-04-12 10:32:04 |
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 |
|---|---|---|---|---|---|---|---|---|
| -45 | 8877 | 0 | AUL | 8877 | 955 | Y | 2021-04-11 00:04:35 | 2021-04-11 00:04:35 |
| 45 | None | None | BO5 | 8877 | 1000 | None | None | 2021-04-12 10:32:04 |
| -55 | 8877 | 0 | SE5 | 8877 | 945 | Y | 2021-04-11 00:04:35 | 2021-04-12 10:32:04 |
* In this table, calculated_balance displays the value that ought to be displayed. In Production, calculated_balance is often incorrect and should not be considered authoritative.