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: auth webhook.
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: auth webhook.
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: auth webhook.
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: setl webhook.
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
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 webhooks
msg_id
type
amount
auth_id
original_auth_id
open_to_buy
timestamp
BAUT
auth
25
3333
0
975
2021-06-17 14:21:35 MST
BAUT
auth
40
6666
3333
960
2021-06-17 16:29:17 MST
BAUT
auth
50
9999
6666
950
2021-06-17 17:08:40 MST
SETL
setl
50
9999
6666
950
2021-06-19 17:47:19 MST
Authorized Transactions RDF
TRANSACTION AMOUNT
AUTHORIZATION CODE
TRANSACTION CODE
REVERSAL ID
TRANSACTION DATE/TIME
25.00-
3333
5
0
06172021 14:21:35
40.00-
6666
5
3333
06172021 16:29:17
50.00-
9999
5
6666
06172021 17:08:40
Posted Transactions RDF
TRANSACTION AMOUNT
AUTHORIZATION CODE
TRANSACTION CODE/TYPE
SOURCE ID
TRANSACTION DATE/TIME
POST DATE
50.00-
9999
VSA
9999
06172021 17:08:40
06192021
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
auth_ts
post_ts
-50
9999
6666
VSA
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.
