Create Card

Create Card API - Mock Testing

You can test the Create Card API using mocks and the following methods:

Method 1: Fixed Card Numbers for Specific Responses

Using specific card numbers, you can simulate fixed responses for the Create Card API. The following table lists card numbers and the corresponding responses you will receive upon making API requests.

With this set of Fixed Cards, you’ll always receive the same card ID, regardless of whether Duplicate Card Check is enabled or disabled. While the card ID remains constant, the user metadata will reflect the values you send. Please note, however, that in both sandbox and production, user metadata cannot be updated or deleted.

Note: The test cards in this method only work for accounts set up with the on-create enrollment type. Do not use the cardIDs from these mock cards to enroll into AU or provision NT via independent endpoints if your account is configured for manual enrollment.

Card Number

Expiration Date

Expected Responses

HTTP Status Code

5100260000019206

Any Future Date

1. Sync response: Card Object Creation Successful 2. Async notification: Card Enrollment Successful Notification 3. GET response: Card, Account Updater (enrolled status) and Network Token (active status) objects are available

201

5100260000009207

Any Future Date

1. Sync response: Card Object Creation Successful 2. Async notification: Card Enrollment Failed Notification 3. GET response: Card, Account Updater (failed status) and Network Token (failed status) objects are available

201

5100260000059210

Any Future Date

1. Sync response: Card Object Creation Failed (Unauthorized) 2. Async notification: No 3. GET response: Not applicable

401

5100260000049211

Any Future Date

1. Sync response: Card Object Creation Failed (Forbidden) 2. Async notification: No 3. GET response: Not applicable

403

5100260000019214

Any Future Date

1. Sync response: Card Object Creation Failed (Internal Server) 2. Async notification: No 3. GET response: Not applicable

500

5100260000009215

Any Future Date

1. Sync response: Card Object Creation Failed (Bad Gateway) 2. Async notification: No 3. GET response: Not applicable

502

5100260000099216

Any Future Date

1. Sync response: Card Object Creation Failed (Service Unavailable) 2. Async notification: No 3. GET response: Not applicable

503

5100260000089217

Any Future Date

1. Sync response: Card Object Creation Failed (Gateway Timeout) 2. Async notification: No 3. GET response: Not applicable

504

4000210000089208

Any Future Date

201

4000210000079209

Any Future Date

201

4000210000029212

Any Future Date

1. Sync response: Card Object Creation Failed (Unauthorized) 2. Async notification: No 3. GET response: Not applicable

401

4000210000019213

Any Future Date

1. Sync response: Card Object Creation Failed (Forbidden) 2. Async notification: No 3. GET response: Not applicable

403

4000210000089216

Any Future Date

1. Sync response: Card Object Creation Failed (Internal Server) 2. Async notification: No 3. GET response: Not applicable

500

4000210000079217

Any Future Date

1. Sync response: Card Object Creation Failed (Bad Gateway) 2. Async notification: No 3. GET response: Not applicable

502

4000210000069218

Any Future Date

1. Sync response: Card Object Creation Failed (Service Unavailable) 2. Async notification: No 3. GET response: Not applicable

503

4000210000059219

Any Future Date

1. Sync response: Card Object Creation Failed (Gateway Timeout) 2. Async notification: No 3. GET response: Not applicable

504

3400000000099200

Any Future Date

1. Sync response: Card Object Creation Successful 2. Async notification: Enrollment Successful Notification 3. GET response: Card and Account Updater (enrolled status) objects are available

201

3400000000179200

Any Future Date

1. Sync response: Card Object Creation Successful 2. Async notification: Enrollment Failed Notification 3. GET response: Card and Account Updater (failed status) objects are available

201

3400000000259200

Any Future Date

1. Sync response: Card Object Creation Failed (Unauthorized) 2. Async notification: No 3. GET response: Not applicable

401

3400000000339200

Any Future Date

1. Sync response: Card Object Creation Failed (Forbidden) 2. Async notification: No 3. GET response: Not applicable

403

3400000000419200

Any Future Date

1. Sync response: Card Object Creation Failed (Internal Server) 2. Async notification: No 3. GET response: Not applicable

500

3400000000589200

Any Future Date

1. Sync response: Card Object Creation Failed (Bad Gateway) 2. Async notification: No 3. GET response: Not applicable

502

3400000000669200

Any Future Date

1. Sync response: Card Object Creation Failed (Service Unavailable) 2. Async notification: No 3. GET response: Not applicable

503

3400000000749200

Any Future Date

1. Sync response: Card Object Creation Failed (Gateway Timeout) 2. Async notification: No 3. GET response: Not applicable

504

6599990001539200

Any Future Date

1. Sync response: Card Object Creation Successful 2. Async notification: Card Enrollment Successful Notification 3. GET response: Card and Account Updater (enrolled status) objects are available

201

6599990001619200

Any Future Date

1. Sync response: Card Object Creation Successful 2. Async notification: Card Enrollment Failed Notification 3. GET response: Card and Account Updater (failed status) objects are available

201

6599990001799200

Any Future Date

1. Sync response: Card Object Creation Failed (Unauthorized) 2. Async notification: No 3. GET response: Not applicable

401

6599990001879200

Any Future Date

1. Sync response: Card Object Creation Failed (Forbidden) 2. Async notification: No 3. GET response: Not applicable

403

6599990001959200

Any Future Date

1. Sync response: Card Object Creation Failed (Internal Server) 2. Async notification: No 3. GET response: Not applicable

500

6599990002039200

Any Future Date

1. Sync response: Card Object Creation Failed (Bad Gateway) 2. Async notification: No 3. GET response: Not applicable

502

6599990002119200

Any Future Date

1. Sync response: Card Object Creation Failed (Service Unavailable) 2. Async notification: No 3. GET response: Not applicable

503

6599990002299200

Any Future Date

1. Sync response: Card Object Creation Failed (Gateway Timeout) 2. Async notification: No 3. GET response: Not applicable

504

Method 2: Any PAN with Specific Mastercard or Visa Bins

Alternatively, you can use any PAN (Primary Account Number) that starts with the Mastercard bin (510026), Visa bin (400021), Amex bin (340000) and Discover bin (659999) to test the Create Card API. The response will depend on the validity of the request payload and the credentials used:

Successful Requests: Appropriate success responses (e.g., 201 - Created) will be returned.
Error Responses: Depending on the request payload and credentials, various error messages (e.g., 4XX errors) will be returned.
- Testing tips:
  - For 422 - remove a required field or provide an invalid value such has 13 as the month in the request.
  - For 400 - malform the json such as removing a comma.

Notes:

5XX errors cannot be triggered using this method. Please use the fixed card numbers from Method 1 to trigger 5XX errors.
Static test cards will return static cardholder information.
To receive the provided cardholder information in the mock success response, use the static bin method.
In this method, both Duplicate Card Check and fingerprinting are enforced.
For accounts set up with the manual enrollment-type, you can create cards with this method, but must trigger AU updates or provision NT separately using the card’s cardID generated by this method.

Card Number

Expiration Date

Expected Responses

HTTP Status Code

510026********** Well formed request payload is sent with no validation errors

Any Future Date

1. Sync response: Card Object Creation Successful 2. Async notification: No 3. GET response: Only card object are available

201

510026********** Request payload is sent with incorrect auth token (token has incorrect creds)

Any Future Date

1. Sync response: Card Object Creation Failed (Unauthorized) 2. Async notification: No 3. GET response: Not applicable

401

510026********** Request payload sent without a required field or an invalid value such as 13 as the month in the request

Any Future Date

1. Sync response: Card Object Creation Failed - 422 Unprocessable Entity) 2. Async notification: No 3. GET response: Not Applicable

422

510026********** Request payload sent with malformed json such as without a comma

Any Future Date

1. Sync response: Card Object Creation Failed - 400 Bad Request) 2. Async notification: No 3. GET response: Not Applicable

400

400021********** Well formed request payload is sent with no validation errors

Any Future Date

1. Sync response: Card Object Creation Successful 2. Async notification: No 3. GET response: Only card object are available

201

400021********** Request payload is sent with incorrect auth token (token has incorrect creds)

Any Future Date

1. Sync response: Card Object Creation Failed (Unauthorized) 2. Async notification: No 3. GET response: Not applicable

401

400021********** Request payload sent without a required field or an invalid value such as 13 as the month in the request

Any Future Date

1. Sync response: Card Object Creation Failed - 422 Unprocessable Entity) 2. Async notification: No 3. GET response: Not Applicable

422

400021********** Request payload sent with malformed json such as without a comma

Any Future Date

1. Sync response: Card Object Creation Failed - 400 Bad Request) 2. Async notification: No 3. GET response: Not Applicable

400

340000********** Well formed request payload is sent with no validation errors

Any Future Date

1. Sync response: Card Object Creation Successful 2. Async notification: No 3. GET response: Only card object are available

201

340000********** Request payload sent without a required field or an invalid value such as 13 as the month in the request

Any Future Date

1. Sync response: Card Object Creation Failed - 422 Unprocessable Entity) 2. Async notification: No 3. GET response: Not Applicable

422

340000********** Request payload sent with malformed json such as without a comma

Any Future Date

1. Sync response: Card Object Creation Failed - 400 Bad Request) 2. Async notification: No 3. GET response: Not Applicable

400

659999********** Well formed request payload is sent with no validation errors

Any Future Date

1. Sync response: Card Object Creation Successful 2. Async notification: No 3. GET response: Only card object are available

201

659999********** Request payload sent without a required field or an invalid value such as 13 as the month in the request

Any Future Date

1. Sync response: Card Object Creation Failed - 422 Unprocessable Entity) 2. Async notification: No 3. GET response: Not Applicable

422

659999********** Request payload sent with malformed json such as without a comma

Any Future Date

1. Sync response: Card Object Creation Failed - 400 Bad Request) 2. Async notification: No 3. GET response: Not Applicable

400

Method 3: Account Updater Enrollment for Visa/Mastercard Cards with Networks

Webhook notifications for the listed events will not be triggered. However:

For accounts set up with the manual enrollment-type, you can create cards with this method, but must trigger AU updates or provision NT separately using the card’s cardID generated by this method.
For accounts set up with the on-create enrollment-type, Account Updater enrollment will generate a success notification, and Network Token provisioning will generate success or failure notifications (note that provisioning usually fails for these cards). The “Expected Response” in the table below applies when these cards are used with accounts configured in on-create mode.

Amex and Discover do not offer sandbox test cards for network testing in sandbox environments.

Test Cards

Expiry Date

Network Event

Expected Response

4680056031099387

8/26

Expired

1. Sync response: Card Object Creation Successful 2. Async notification: Enrollment Successful + Network Token Provision Failed Notifications 3. GET response: Card, Account Updater (enrolled status) and Network Token (failed status) objects are available New Expiration Date

4403933787254356

9/26

Closed

4000220720915104

1/25

Contact cardholder advice

4207670264522669

10/26

Valid

4327390068355738

12/23

Updated

4549612182636736

3/23

Account non-participating

5122350100384503

5/25

Updated

5122351100114502

6/25

Valid

5122351100004505

7/25

Expired

5022351100004506

8/25

Failed

1. Sync response: Card Object Creation Successful 2. Async notification: Enrollment Failed + Network Token Provision Failed Notifications 3. GET response: Card, Account Updater (failed status) and Network Token (failed status) objects are available Same Card Data

Notes:

For Mastercard Account Updater (Account Updater) Enrollment Cards, you can use any Mastercard numbers ending in the following digits, in addition to the above mentioned Mastercard card numbers.
- 0, 3: Any future date → Account update response.
- 2: Any future date → No change response (card is still valid).
- 5: Any future date → Account expiry date update response.
- 6, 8, 9: Any future date → Example error response.

The above-mentioned Visa cards are also available here.

Method 3a : Network Token Provisioning for Visa/Mastercard Cards with Networks

Webhook notifications for the listed events will not be triggered. However, a Network Token provisioning success notification will be sent, and Account Updater enrollment success or failure notifications will be generated (note that Account Updater enrollment typically could fail for these cards).

For test cards to validate Visa Network Tokens, please contact VGS Support or your designated VGS implementation representative.

Amex and Discover Network Tokens - Coming Soon! Stay tuned for updates.

Card Number

Expiration Date

Expected Response

2222690420064574

6/27

1. Sync response: Card Object Creation Successful 2. Async notification: Enrollment Successful/Failure + Network Token Provision Successful (+ sometimes Activated) Notifications 3. GET response: Card, Account Updater (enrolled or failed status) and Network Token (active or activated status) objects are available

2222690420064582

7/27

5120350100064594

8/27

Method 4 : Discover Test Cards

Use Case

Test Card Number (xxxx=6011)

HTTP Status

Error Code

Token Provisioning / Single Token - Happy Path Bulk Provision Token Request - Happy Path

xxxx000025883707 xxxx012015750069 xxxx000024700456 xxxx000068300544 xxxx012021880256

200

Token Provisioning / Single Token - Happy Path - NO PAR Bulk Provision Token Request - Happy Path - NO PAR

xxxx222244446666 xxxx222244449728

200

Token Provisioning / Multiple Tokens - Happy Path

xxxx000088618537

200

Token Provisioning - Invalid Card

xxxx005199449433

400

10001

Token Provisioning - Ineligible PAN

xxxx005199449441

400

10002

Token Provisioning - Provisioning Count Exceeded

xxxx005199449458

400

10003

Token Provisioning - Cryptographic Error

xxxx005199449466

400

10004

Token Provisioning - Card Identifier Validation Failed

xxxx005199449474

400

10006

Token Provisioning - Account/User Cannot Be Added

xxxx005199449482

400

10007

Token Provisioning - Account is already provisioned in the wallet

xxxx005199449490

400

10009

Token Provisioning - Name Verification Failed

xxxx005199449508

400

10010

Token Provisioning - Expired Card

xxxx005199449516

400

10012

Token Provisioning - User Locked

xxxx005199449524

400

10013

Token Provisioning - Incorrect Account Details

xxxx005199449532

400

10014

Token Provisioning - Invalid Token Requestor Id

xxxx005199449540

400

10020

Token Provisioning - API Request Valid/Unexpected Error

xxxx005199449557

400

30001

Token Provisioning - API Request Valid/Downstream System Unavailable

xxxx005199449565

400

30001

RED-FLOW PAN - Declined Response

xxxx012020630389 xxxx000000006548

200

non-zero error code

Note:

We recommend reviewing our Forward-Compatible API Integration Guidelines to ensure your integration remains stable as CMP evolves. Avoid strict schema validation or exact JSON comparisons, as new fields may be added to request and response payloads over time.
When your account is set to manual mode, automatic Account Updater (AU) and Network Tokenization (NT) processes are not triggered when a card is created. For sandbox cards, you must first manually enroll them in AU. After enrollment, performing a GET request by card ID will return the updated AU and NT values.

PreviousPrerequisite NextGet Card

Last updated 23 days ago