Scenario 16: Settlement Without Authorization
A debit cardholder purchases $35 worth of goods from a retail outlet. The merchant clears the transaction 10 days later, but authorizations for this merchant type and amount expire after seven days. The following are true:
- The initial available balance is $1000.
- The merchant validates the debit card with a signature.
- The network is Visa.
Sequence of events
Events in the same step have the same timestamp.
- Visa sends an authorization request for –35.00.
- Galileo approves the request and places a 35.00 hold on the account. The available balance is now 965.00. Galileo sends a
BAUT: authwebhook. - After seven days the authorization expires. Galileo sends a
BEXP: auth_expwebhook and releases the 35.00 hold. The available balance is now 1000.00. - Three days later, Visa sends a clearing file that contains the –35.00 transaction.
- Galileo adds new authorization and backout entries to the ledger and then posts –35.00 to the account. The available balance is now 965.00. Galileo sends a
SETL: setlwebhook.
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 | Auth | 35.00 | 2266 | 0 | 1000.00 | 20210610:101354MST |
Authorization/Settlement Events webhooks
By request you can have the expired_auth_id field added to SETL: setl webhooks.
| msg_id | type | amount | auth_id | original_auth_id | expired_auth_id | open_to_buy | timestamp |
|---|---|---|---|---|---|---|---|
| BAUT | auth | 35 | 2266 | 0 | 0 | 965 | 2021-06-10 10:13:54 MST |
| BEXP | auth_exp | 35 | 2266 | 0 | 0 | 1000 | 2021-06-17 04:22:02 MST |
| SETL | setl | 35 | 9911 | 0 | 2266 | 965 | 2021-06-20 15:14:45 MST |
Authorized Transactions RDF
| TRANSACTION AMOUNT | AUTHORIZATION CODE | AUTHORIZATION RESPONSE | TRANSACTION CODE | REVERSAL ID | TRANSACTION DATE/TIME |
|---|---|---|---|---|---|
| 35.00- | 2266 | 00 | 5 | 0 | 2021-06-10 10:13:54 |
| 35.00- | 9911 | 11 | 5 | 0 | 2021-06-20 15:14:45 |
Posted Transactions RDF
By request you can have the EXPIRED AUTH CODE field added to your standard Posted Transactions RDF. The new Secondary RDFs already have this field included.
| TRANSACTION AMOUNT | AUTHORIZATION CODE | TRANSACTION CODE/TYPE | SOURCE ID | EXPIRED AUTH CODE | TRANSACTION DATE/TIME | POST DATE |
|---|---|---|---|---|---|---|
| 35.00- | 9911 | VSM | 9911 | 2266 | 2021-06-20 15:14:45 | 2021-06-20 15:14:45 |
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 |
|---|---|---|---|---|---|
| -35 | 2266 | 0 | A | 000000003500 | 2021-06-10 10:13:54 |
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 |
|---|---|---|---|---|---|
| -35 | 9911 | 0 | VSM | 2021-06-20 15:14:45 | 2021-06-20 15:14:45 |
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 |
|---|---|---|---|---|---|---|---|---|
| -35 | 2266 | 0 | VIA | 2266 | 965 | Y | 2021-06-10 10:13:54 | 2021-06-10 10:13:54 |
| 35 | None | None | VXA | 2266 | 1000 | None | None | 2021-06-17 04:22:02 |
| -35 | 9911 | 0 | VIM | 9911 | 965 | Y | 2021-06-20 15:14:45 | 2021-06-20 15:14:45 |
| 35 | 9911 | 0 | BVM | 9911 | 1000 | Y | None | 2021-06-20 15:14:45 |
| -35 | 9911 | 0 | VSM | 9911 | 965 | Y | 2021-06-20 15:14:45 | 2021-06-20 15:14:45 |