Scenario 3: Incremental Authorizations
A debit cardholder calls a ride-share service through its app, and the cost of the proposed destination is $25. After arriving at the first destination the cardholder requests a second destination for $15, and then after arriving at the second destination requests a third, for $10.
- The initial available balance is $1000.
- The cardholder pays using a mobile wallet.
- The network is Visa.
Sequence of events
Events in the same step have the same timestamp.
- Visa sends an authorization request for –25.00.
- Galileo approves the request and places a 25.00 hold on the account. The available balance is now 975.00. Galileo sends the
BAUT: authevent message. - Visa sends an incremental authorization request for –40.00.
- Galileo approves the request, backs out the previous 25.00 hold, and places a new 40.00 hold on the account. The available balance is now 960.00. Galileo sends the
BAUT: authevent message. - Visa sends another incremental authorization request for –50.00.
- Galileo approves the request, backs out the previous 40.00 hold, and places a new 50.00 hold on the account. The available balance is now 950.00. Galileo sends the
BAUT: authevent message. - Visa sends a clearing file with the –50.00 settlement.
- Galileo backs out the 50.00 hold and posts –50.00 to the account. The available balance is still 950.00. Galileo sends the
SETL: setlevent message.
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.
Note
See Enhanced incremental authorization reporting in the Authorization guide for additional fields that Galileo can enable for you.
Auth API
| auth_type | transaction_type | trans_amount | auth_id | original_id | available_funds | incremental_auth | timestamp |
|---|---|---|---|---|---|---|---|
| Auth | Auth | 25.00 | 3333 | 0 | 1000.00 | False | 20210617:142135MST |
| Auth | Auth | 40.00 | 6666 | 3333 | 975.00 | True | 20210617:162917MST |
| Auth | Auth | 50.00 | 9999 | 6666 | 960.00 | True | 20210617:170840MST |
Authorization/Settlement Events
| msg_id | type | amount | auth_id | act_type | otype | original_auth_id | original_ incremental_id | open_to_buy | local_currency _amount | visa_trans_id | timestamp |
|---|---|---|---|---|---|---|---|---|---|---|---|
| BAUT | auth | 25 | 3333 | VI | A | 0 | 0 | 975 | 25 | 381381381381381 | 2021-06-17 14:21:35 MST |
| BAUT | auth | 40 | 6666 | VI | A | 3333 | 3333 | 960 | 15 | 381381381381381 | 2021-06-17 16:29:17 MST |
| BAUT | auth | 50 | 9999 | VI | A | 6666 | 3333 | 950 | 10 | 381381381381381 | 2021-06-17 17:08:40 MST |
| SETL | setl | 50 | 9999 | VS | A | 6666 | 3333 | 950 | 0 | 381381381381381 | 2021-06-19 17:47:19 MST |
Authorized Transactions RDF
- For Visa incremental authorizations, the value
3900is present inDE63_BRN. - The
ASSOCIATION TRANS IDis the same for all Visa transactions in an incremental series. - The
TRANSACTION AMOUNTfield contains the cumulative amount, andLOCAL AMOUNTcontains the increment.
| TRANSACTION AMOUNT | AUTHORIZATION CODE | TRANSACTION CODE | AUTH TRANSACTION CODE | REVERSAL ID | TRANSACTION DATE/TIME | LOCAL AMOUNT | ASSOCIATION TRANS ID | DE63_BRN |
|---|---|---|---|---|---|---|---|---|
| -25.00 | 3333 | 5 | VIA | 0 | 2021-06-17 14:21:35 | -25.00 | 381381381381381 | 2-------- |
| -40.00 | 6666 | 5 | VIA | 3333 | 2021-06-17 16:29:17 | -15.00 | 381381381381381 | 2----3900 |
| -50.00 | 9999 | 5 | VIA | 6666 | 2021-06-17 17:08:40 | -10.00 | 381381381381381 | 2----3900 |
Posted Transactions RDF
Use the ASSOCIATION TRANS ID to link the settlement to the incremental series.
| TRANSACTION AMOUNT | AUTHORIZATION CODE | REVERSAL ID | TRANSACTION CODE/TYPE | SOURCE ID | AUTH TRANSACTION CODE | LOCAL AMOUNT | TRANSACTION DATE/TIME | POST DATE | ASSOCIATION TRANS ID |
|---|---|---|---|---|---|---|---|---|---|
| -50.00 | 9999 | 6666 | VSA | 9999 | VIA | -50.00 | 2021-06-17 17:08:40 | 2021-06-19 17:47:19 | 381381381381381 |
Get Authorization History response
This endpoint returns only transactions that have not settled or expired. These transactions are also returned by Get Account Overview. This example shows all three authorizations; however, in Production you would get only the most recent transaction. The local_amt field contains the amount of the increment and amt contains the cumulative amount.
| amt | auth_id | original_auth_id | type | local_amt | timestamp |
|---|---|---|---|---|---|
| -25 | 3333 | 0 | A | 0000000002500 | 2021-06-17 14:21:35 |
| -40 | 6666 | 3333 | A | 000000001500 | 2021-06-17 16:29:17 |
| -50 | 9999 | 6666 | A | 000000001000 | 2021-06-17 17:08:40 |
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 | local_amt | auth_ts | post_ts |
|---|---|---|---|---|---|---|
| -50 | 9999 | 6666 | VSA | 0 | 2021-06-17 16:45:02 | 2021-06-19 17:47:19 |
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 | local_amt | calculated_balance | credit_ind | auth_ts | post_ts |
|---|---|---|---|---|---|---|---|---|---|
| -25 | 3333 | 0 | VIA | 3333 | 25 | 975 | Y | 2021-06-17 14:21:35 | 2021-06-17 14:21:35 |
| 25 | None | None | PVPV | 3333 | null | 1000 | None | None | 2021-06-17 16:29:17 |
| -40 | 6666 | 3333 | VIA | 6666 | 15 | 960 | Y | 2021-06-17 14:21:35 | 2021-06-17 16:29:17 |
| 40 | None | None | PVPV | 6666 | null | 1000 | None | None | 2021-06-17 16:45:02 |
| -50 | 9999 | 6666 | VIA | 9999 | 10 | 950 | Y | 2021-06-17 16:45:02 | 2021-06-17 17:08:40 |
| 50 | 9999 | 6666 | BVA | 9999 | null | 1000 | Y | 2021-06-17 16:45:02 | 2021-06-19 17:47:19 |
| -50 | 9999 | 6666 | VSA | 9999 | null | 950 | Y | 2021-06-17 16:45:02 | 2021-06-19 17:47:19 |