Skip to main content
POST
Push Cards to Token Requestors

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

x-audit-user
string

Optional audit user header

Body

application/json
tokenRequestorId
string
required

Unique identifier of the token requestor.

Example:

"50123456789"

cardIds
string<uuid>[]
required

List of card IDs to be added to the token requestor server.

Required array length: 1 - 5 elements
callbackURL
string

The token requestor's mobile or web application URI.

Example:

"http://www.tokenIssuer1.com/pushtoken"

locale
string

Cardholder's preferred locale (language and country). This information is useful to the token requestor to provide an optimised user experience. Format: Two letter ISO 639-1 language in lowercase, with a underscore (”_”), followed by two letter ISO 3166-1 country code in uppercase.

Example:

"en_US"

includeAccountHolderData
enum<string>[]

Account holder's information. Information included in this list is sent to the token requestor, only when requestor supports supportedAccountHolderData. Otherwise the values are filtered out. Possible values are:

  • ALL_SUPPORTED: The Token Requestor's accepts supportedAccountHolderData object.
  • NAME: The first and the last name of the account holder.
  • ADDRESS: The billing address for the account holder.
  • EMAIL_ADDRESS: The email address for the account holder.
  • MOBILE_PHONE_NUMBER: The mobile phone number for the account holder.
Available options:
ALL_SUPPORTED,
NAME,
ADDRESS,
EMAIL_ADDRESS,
MOBILE_PHONE_NUMBER
tokenRequestorSessionId
string

The session Id provided by the token requestor; applicable when the card is added through pull provisioning method.

Required string length: 3 - 64
Example:

"dbc55444-496a-4896-b41c-5d5e2dd431e2"

Response

OK

signatureAccountData
string

Mastercard-signed package that validates the authenticity of the push provisioning response. Your application infrastructure uses this data before redirecting the cardholder to the digital wallet/merchant (for example, through a redirect or SDK call). The wallet can verify the response originated from Mastercard MDES.

Example:

"ew0KImFsZyI6ICJSUzI1NiIsDQoNCiJraWQiOiAiYXNkZmctcXdlcnR5LXp4Y3ZiIg0KfQ.ew0KDQrCoCJwdXNoQWNjb3VudFJlY2VpcHQiOiAiTUNDLVNUTC0xMzQzMTNCRi01NTg1LTRFNzEtQUIyNC1FQ0RCQzI4RjIzRjEiLA0KImlzc3VlckNhbGxCYWNrIjogImh0dHBzOi8vaXNzdWVyY2FsbGJhY2sudXJsIiwNCiJjYWxsYmFja1JlcXVpcmVkIjogdHJ1ZSwNCiJjb21wbGV0ZVdlYnNpdGVBY3RpdmF0aW9uIjogdHJ1ZSwNCiJhY2NvdW50SG9sZGVyRGF0YVN1cHBsaWVkIjogdHJ1ZSwNCiJsb2NhbGUiOiAiZW5fVVMiDQoNCn0.dBjftJeZ4CVP-"

pushAccountReceipts
object[]

Returned for each card added to the digital wallet/merchant.

availablePushMethods
object[]

Array of push methods supported by the token requestor. Present only when the push operation is successful.