Push multiple accounts

Push card and account(s) to a token requestor.

A token requestor is an entity that initiates the tokenization process. Wallets, merchants, payments service providers (PSPs) are collectively referred to as token requestors.

Notes:

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
number
required

Card ID

accounts
object
required
string
required
length ≤ 11

Token requestor ID (TRID), a numeric 11-digit value.

A token requestor is an entity that initiates the tokenization process. Wallets, merchants, payments service providers (PSPs) are collectively referred to as token requestors.

Card networks use TRIDs to enforce usage boundaries at the network level, know who is reponsible if fraud occurs, and to prevent tokens from being used elsewhere.

string
required

Consumer preferred locale (language and country).

Format: two-letter ISO-639-1 language in lowercase + underscore ("_") + two-letter ISO 3166-1 country code in uppercase.

string
length ≤ 256

Callback URL token requestor uses to pass control back to the issuer.

boolean
Defaults to false

Should token requestor complete app activation if provisioning request receives a REQUIRE_ADDITIONAL_AUTHENTICATION and the cardholder chooses the CARDHOLDER_TO_USE_ISSUER_MOBILE_APP authentication method?

boolean
Defaults to false

Should token requestor complete website activation if provisioning request receives a REQUIRE_ADDITIONAL_AUTHENTICATION and the cardholder chooses the CARDHOLDER_TO_VISIT_WEBSITE authentication method?

boolean
Defaults to false

Is cardholder information stored in MDES along with funding account information?

boolean
Defaults to false

Return issuer initiated digitization data?

number
enum
5 to 15
Defaults to 15

Push account receipts validity period in minutes. If issuer is pushing more than one account, the provided value is applicable to all receipts.

Default is 15. Must be greater or equal to 5 and less than or equal to 15.

Headers
string
required

Access token. Tokens can expire quickly, which can result in a 401 Unauthorized error.

int64
required

Account ID

integer
required

Customer ID

string
required

Pismo organization/tenant ID

Responses

400

Bad request

500

Internal server error

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json