v1

latestOpenAPI 3.1.0Copyright Pismo2026-07-247702,7523.1 MB

MDES Token Connect [Beta]

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:

Pismo acts as a proxy for the <a href="https://developer.mastercard.com/mdes-token-connect/documentation/api-reference/" target="_blank">Mastercard Token Connect API</a>
This endpoint does not generate an event
For more information, refer to the MDES Token Connect guide.

post/v1/token-connect/push-multiple-accounts

Headers

access_tokenstring required

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

x-account-idinteger required

Account ID

x-customer-idinteger required

Customer ID

x-tenantstring required

Pismo organization/tenant ID

Request body

card_idinteger required

Enrolled card ID

token_requestor_idstring required

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.

localestring 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.

callback_urlstring

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

complete_issuer_app_activationboolean

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?

complete_website_activationboolean

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?

account_holder_data_suppliedboolean

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

request_issuer_initiated_digitization_databoolean

Return issuer initiated digitization data?

push_account_receipts_validity_period5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 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.

Example request

{
  "card_id": 6743052,
  "accounts": {
    "holder_details": {
      "name": "Cee Biskit",
      "address": {
        "line1": "1313 Mockingbird Lane",
        "line2": "Apt 4B",
        "country": "USA",
        "country_subdivision": "CA",
        "city": "San Francisco",
        "postal_code": "8675309"
      },
      "contact": {
        "email_address": "barbie_kew@roadhouse.com",
        "country_dial_in_code": "1",
        "phone_number": "4155551234"
      }
    },
    "validity_details": {
      "data_valid_until_timestamp": "2025-12-31T23:59:59Z"
    }
  },
  "token_requestor_id": "01234567890",
  "locale": "en_US",
  "callback_url": "https://callback.example.com",
  "push_account_receipts_validity_period": 15
}

Response

Successful response

signaturestring

JWS signature output. REQUIRED if token_reqiest_signature_support is true and at least one push account receipt is returned.

token_requestor_signature_supportboolean

Does token requestor support signature verification?

Example response

{
  "push_account_receipts": [
    {
      "push_account_id": "pa_123456789",
      "push_account_receipt": "MCC-C307FOAE-298E-48EB-AA43-A7C40B32DDDE"
    }
  ],
  "available_push_methods": [
    {
      "type": "WEB",
      "uri": "https://tokenize.example.com"
    }
  ]
}