Scenario 15: Tokenization Authorization
A debit cardholder installs a meal-delivery service app and specifies a card in a mobile wallet as the payment method. The app validates the card before approving it for use. The following are true:
- The initial available balance is $1000.
- The network is Visa.
Sequence of events
Events in the same step have the same timestamp.
- Visa sends an authorization and AVS check request for 0.00. The Merchant Description field contains "Visa Provisioning Service."
- Galileo performs an AVS check and the check passes. Galileo returns
Yfor the AVS check (address and zip code match) and response code85, which is approval for a non-financial transaction. Galileo sends theAAAU: authwebhook. - The app accepts the card as payment.
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 | Tokenization | 0.00 | 4455 | 0 | 1000 | 20210617:074449MST |
Authorization/Settlement Events webhooks
| msg_id | type | amount | auth_id | original_auth_id | open_to_buy | timestamp |
|---|---|---|---|---|---|---|
| AAAU | auth | 0.00 | 4455 | 0 | 1000 | 2021-06-17 07:44:49 MST |
Authorized Transactions RDF
| TRANSACTION AMOUNT | AUTHORIZATION CODE | TRANSACTION CODE | REVERSAL ID | TRANSACTION DATE/TIME |
|---|---|---|---|---|
| 0.00+ | 4455 | 5 | 0 | 2021-06-17 07:44:49 |
Posted Transactions RDF
This transaction does not appear in this RDF.
Get Authorization History response
This transaction is not returned by this endpoint.
Get Transaction History response
This transaction is not returned by this endpoint.
Get All Transaction History response
This transaction is not returned by this endpoint or the CST.