Introduction
Digital Wallet Token Simulations
Digital Wallet Token simulations are intended to mock the usage of provisioning a card to a digital wallet. A successful simulation call will return a 202 status. An object id will not be returned, but you will receive a digital_wallet_token.create
webhook with the object id. This object id can be used on the /digital_wallet_token/{id}
endpoint. There is currently one simulation below.
Simulation type | Token message type | Explanation |
---|---|---|
digital_wallet_token.provisioning | provisioning | Simulate a card getting added to a digital wallet |
Create a Digital Wallet Token Simulation
Initiate a Digital Wallet Token simulation.
Digital Wallet Token Request Body
Provisioning
Parameter | Type | Required? | Description |
---|---|---|---|
card_id | string | Required | ID of the card to use as the source for simulated tokens. |
fulfillment | object | An object that defines additional fields for fulfillment of the token. | |
token_service_provider | object | An object that defines additional fields for requestor of the token. |
Fulfillment Sub-Object
Parameter | Type | Description |
---|---|---|
status | string | Provisioning status of the token. One of decision_green , decision_red , decision_yellow , rejected , or provisioned . |
Token Service Provider Sub-Object
Parameter | Type | Description |
---|---|---|
token_requestor_name | string | Name of the token requestor within the card network. One of APPLE_PAY or ANDROID_PAY . |
token_requestor_id | string | Unique numerical identifier of the digital wallet token requestor within the card network. These IDs map to a token_requestor_name. 50110030273 for Apple Pay, 50120834693 for Google Pay, and 50139059239 for Samsung Pay. |
Example Request
Example Response
Success
There will be no response body. The response code will be a 202 - accepted
Error
Was this page helpful?