---
title: "Push multiple accounts"
method: POST
path: "/v1/token-connect/push-multiple-accounts"
tags: ["MDES Token Connect [Beta]"]
---

# Push multiple accounts

`POST /v1/token-connect/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](https://developers.pismo.io/pismo-docs/docs/mdes-token-connect) guide.

## Headers

- `access_token` string, required
- `x-account-id` integer, required
- `x-customer-id` integer, required
- `x-tenant` string, required

## Request body

- PushAccountsRequest
  - `card_id` integer, required — Enrolled card ID
  - `accounts` AccountData, required
    - `holder_details` HolderDetails, required — Account holder details object
      - `name` string — Account holder name in the format Last name/First name or first name last name.
      - `address` Address
        - `line1` string — Address line one
        - `line2` string — Address line two
        - `country` string, required — Billing address country - ISO-3166-1 3-letter code.
        - `country_subdivision` string — Country subdivision such as state or sultanate
        - `city` string — Billing address city
        - `postal_code` string — Billing address postal code, such as zip code in the United States.
      - `contact` Contact — Contact object
        - `email_address` string, email — Email address
        - `country_dial_in_code` string — International dial-in prefix code associated with country.
        - `phone_number` string — Phone number following `country_dial_in_code` prefix.
    - `validity_details` ValidityDetails, required
      - `data_valid_until_timestamp` string, date-time — Data valid until timestamp. Format: ISO 8601 extended format as one of the following: * YYYY-MM-DDThh:mm:ss[.sss]Z * YYYY-MM-DDThh:mm:ss[.sss]±hh:mm where [.sss] is optional and can be 1 to 3 digits
  - `token_requestor_id` string, 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.
  - `locale` 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.
  - `callback_url` string — Callback URL token requestor uses to pass control back to the issuer.
  - `complete_issuer_app_activation` boolean — 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_activation` boolean — 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_supplied` boolean — Is cardholder information stored in MDES along with funding account information?
  - `request_issuer_initiated_digitization_data` boolean — Return issuer initiated digitization data?
  - `push_account_receipts_validity_period` 5 | 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`.

## Response `200`

Successful response

- PushAccountsResponse
  - `push_account_receipts` PushAccountReceipt[] — Push account receipts
    - `push_account_id` string, required — Push account ID
    - `push_account_receipt` string, required — Push account receipt to token requestor. Contains pushed account details and expires after 15 minutes. A valid receipt = 3-character prefix identifying product associated with funding account + UUID. Prefic values: * `MCC` - Mastercard credit * `DMC` - Mastercard debit * `MSI` - Maestro * `PVL` - Private label
    - `issuer_initiated_digitization_data` string — Base64 encoded string issuer can pass to token requestor proprietary communication. Present if `request_issuer_initiated_digitization_data` is `true` in the request.
  - `available_push_methods` PushMethod[] — Available push methods
    - `type` 'ANDROID' | 'IOS' | 'WEB', required — Push method type * `ANDROID` - Android app intent URI * `IOS` - iOS app intent URI * `WEB` - Browser URL
    - `uri` string, uri, required — URI to open the token requestor's application or website.
  - `signature` string — JWS signature output. **REQUIRED** if `token_reqiest_signature_support` is `true` and at least one push account receipt is returned.
  - `token_requestor_signature_support` boolean — Does token requestor support signature verification?

## Other responses

- `400` — Bad request
- `500` — Internal server error

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/versions/935b62e16de4/schema)