# 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 <a href="#method-1-fixed-card-numbers-for-specific-responses" id="method-1-fixed-card-numbers-for-specific-responses"></a>

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 `cardID`s from these mock cards to enroll into AU or provision NT via independent endpoints if your account is configured for **manual** enrollment.

| Test Card Number                                | Test CardIDs                                         | Expiration Date | Expected Responses                                                                                                                                                                                                                             | HTTP Status Code |
| ----------------------------------------------- | ---------------------------------------------------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- |
| 5100260000019206                                | CRDKfukrUmMsUdotydKS4euZ1v2exoN617mWi7avaehqkYh2J5JP | Any Future Date | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Card Enrollment Successful Notification<br>3. GET response: Card, Account Updater (enrolled status) and Network Token (active status) objects are available</p> | 201              |
| 5100260000009207                                | CRDqL55P51GVUMbZMDgYakHQTJSoFP2e8NoMXzhQpVPgLh91ZEQo | Any Future Date | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Card Enrollment Failed Notification<br>3. GET response: Card, Account Updater (failed status) and Network Token (failed status) objects are available</p>       | 201              |
| 5100260000059210                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Unauthorized)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                            | 401              |
| 5100260000049211                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Forbidden)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                               | 403              |
| 5100260000019214                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Internal Server)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                         | 500              |
| 5100260000009215                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Bad Gateway)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                             | 502              |
| 5100260000099216                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Service Unavailable)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                     | 503              |
| 5100260000089217                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Gateway Timeout)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                         | 504              |
| 4000210000089208                                | CRDrc6FX3HbucdEvQCHha7Tkqa2TMT66xV9QDrNzh72NB5mw2R7u | Any Future Date | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Card Enrollment Successful Notification<br>3. GET response: Card, Account Updater (enrolled status) and Network Token (active status) objects are available</p> | 201              |
| 4000210000079209                                | CRDoy9WqbTDwadttfKbWSTcbSnYddb8i5naGmDprK4BLBzbCawHg | Any Future Date | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Card Enrollment Failed Notification<br>3. GET response: Card, Account Updater (failed status) and Network Token (failed status) objects are available</p>       | 201              |
| 4000210000029212                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Unauthorized)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                            | 401              |
| 4000210000019213                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Forbidden)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                               | 403              |
| 4000210000089216                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Internal Server)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                         | 500              |
| 4000210000079217                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Bad Gateway)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                             | 502              |
| 4000210000069218                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Service Unavailable)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                     | 503              |
| 4000210000059219                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Gateway Timeout)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                         | 504              |
| <p>3400000000099200<br><br><br></p>             | CRDKfukrUmMsUdotydKS4euZ1v2exoN617mWi7avaehqkYh2J5J0 | Any Future Date | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Enrollment Successful Notification<br>3. GET response: Card and Account Updater (enrolled status) objects are available</p>                                     | 201              |
| 3400000000179200                                | CRDqL55P51GVUMbZMDgYakHQTJSoFP2e8NoMXzhQpVPgLh91ZEQ1 | Any Future Date | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Enrollment Failed Notification<br>3. GET response: Card and Account Updater (failed status) objects are available</p>                                           | 201              |
| 3400000000259200                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Unauthorized)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                            | 401              |
| 3400000000339200                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Forbidden)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                               | 403              |
| 3400000000419200                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Internal Server)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                         | 500              |
| 3400000000589200                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Bad Gateway)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                             | 502              |
| 3400000000669200                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Service Unavailable)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                     | 503              |
| 3400000000749200                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Gateway Timeout)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                         | 504              |
| <p>6599990001539200<br><br><br><br><br><br></p> | CRDKfukrUmMsUdotydKS4euZ1v2exoN617mWi7avaehqkYh2J5J2 | Any Future Date | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Card Enrollment Successful Notification<br>3. GET response: Card and Account Updater (enrolled status) objects are available</p>                                | 201              |
| 6599990001619200                                | CRDqL55P51GVUMbZMDgYakHQTJSoFP2e8NoMXzhQpVPgLh91ZEQ3 | Any Future Date | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Card Enrollment Failed Notification<br>3. GET response: Card and Account Updater (failed status) objects are available</p>                                      | 201              |
| 6599990001799200                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Unauthorized)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                            | 401              |
| 6599990001879200                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Forbidden)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                               | 403              |
| 6599990001959200                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Internal Server)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                         | 500              |
| 6599990002039200                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Bad Gateway)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                             | 502              |
| 6599990002119200                                |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Service Unavailable)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                     | 503              |
| <p>6599990002299200<br></p>                     |                                                      | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Gateway Timeout)<br>2. Async notification: No<br>3. GET response: Not applicable</p>                                                                                                         | 504              |

### Method 2: Any PAN with Specific Mastercard or Visa Bins <a href="#method-2-any-pan-with-specific-mastercard-or-visa-bins" id="method-2-any-pan-with-specific-mastercard-or-visa-bins"></a>

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 |
| --------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------- |
| <p>510026\*\*\*\*\*\*\*\*\*\*<br>Well formed request payload is sent with no validation errors</p>                                            | Any Future Date | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: No<br>3. GET response: Only card object are available</p>         | 201              |
| <p>510026\*\*\*\*\*\*\*\*\*\*<br>Request payload is sent with incorrect auth token (token has incorrect creds)</p>                            | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Unauthorized)<br>2. Async notification: No<br>3. GET response: Not applicable</p>              | 401              |
| <p>510026\*\*\*\*\*\*\*\*\*\*<br>Request payload sent without a required field or an invalid value such as 13 as the month in the request</p> | Any Future Date | <p>1. Sync response: Card Object Creation Failed - 422 Unprocessable Entity)<br>2. Async notification: No<br>3. GET response: Not Applicable</p> | 422              |
| <p>510026\*\*\*\*\*\*\*\*\*\*<br>Request payload sent with malformed json such as without a comma</p>                                         | Any Future Date | <p>1. Sync response: Card Object Creation Failed - 400 Bad Request)<br>2. Async notification: No<br>3. GET response: Not Applicable</p>          | 400              |
| <p>400021\*\*\*\*\*\*\*\*\*\*<br>Well formed request payload is sent with no validation errors</p>                                            | Any Future Date | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: No<br>3. GET response: Only card object are available</p>         | 201              |
| <p>400021\*\*\*\*\*\*\*\*\*\*<br>Request payload is sent with incorrect auth token (token has incorrect creds)</p>                            | Any Future Date | <p>1. Sync response: Card Object Creation Failed (Unauthorized)<br>2. Async notification: No<br>3. GET response: Not applicable</p>              | 401              |
| <p>400021\*\*\*\*\*\*\*\*\*\*<br>Request payload sent without a required field or an invalid value such as 13 as the month in the request</p> | Any Future Date | <p>1. Sync response: Card Object Creation Failed - 422 Unprocessable Entity)<br>2. Async notification: No<br>3. GET response: Not Applicable</p> | 422              |
| <p>400021\*\*\*\*\*\*\*\*\*\*<br>Request payload sent with malformed json such as without a comma</p>                                         | Any Future Date | <p>1. Sync response: Card Object Creation Failed - 400 Bad Request)<br>2. Async notification: No<br>3. GET response: Not Applicable</p>          | 400              |
| <p>340000\*\*\*\*\*\*\*\*\*\*<br>Well formed request payload is sent with no validation errors<br><br><br><br></p>                            | Any Future Date | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: No<br>3. GET response: Only card object are available</p>         | 201              |
| <p>340000\*\*\*\*\*\*\*\*\*\*<br>Request payload sent without a required field or an invalid value such as 13 as the month in the request</p> | Any Future Date | <p>1. Sync response: Card Object Creation Failed - 422 Unprocessable Entity)<br>2. Async notification: No<br>3. GET response: Not Applicable</p> | 422              |
| <p>340000\*\*\*\*\*\*\*\*\*\*<br>Request payload sent with malformed json such as without a comma</p>                                         | Any Future Date | <p>1. Sync response: Card Object Creation Failed - 400 Bad Request)<br>2. Async notification: No<br>3. GET response: Not Applicable</p>          | 400              |
| <p>659999\*\*\*\*\*\*\*\*\*\*<br>Well formed request payload is sent with no validation errors<br><br><br><br></p>                            | Any Future Date | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: No<br>3. GET response: Only card object are available</p>         | 201              |
| <p>659999\*\*\*\*\*\*\*\*\*\*<br>Request payload sent without a required field or an invalid value such as 13 as the month in the request</p> | Any Future Date | <p>1. Sync response: Card Object Creation Failed - 422 Unprocessable Entity)<br>2. Async notification: No<br>3. GET response: Not Applicable</p> | 422              |
| <p>659999\*\*\*\*\*\*\*\*\*\*<br>Request payload sent with malformed json such as without a comma</p>                                         | Any Future Date | <p>1. Sync response: Card Object Creation Failed - 400 Bad Request)<br>2. Async notification: No<br>3. GET response: Not Applicable</p>          | 400              |

### Method 3: Account Updater Enrollment for Visa/Mastercard Cards with Networks <a href="#method-3-account-updater-enrollment-for-visamastercard-cards-with-networks" id="method-3-account-updater-enrollment-for-visamastercard-cards-with-networks"></a>

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.&#x20;
* **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                   | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Enrollment Successful + Network Token Provision Failed Notifications<br>3. GET response: Card, Account Updater (enrolled status) and Network Token (failed status) objects are available<br>New Expiration Date</p>                     |
| 4403933787254356 | 9/26        | Closed                    | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Enrollment Successful + Network Token Provision Failed Notifications<br>3. GET response: Card, Account Updater (enrolled status) and Network Token (failed status) objects are available<br>Same Card Data</p>                          |
| 4000220720915104 | 1/25        | Contact cardholder advice | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Enrollment Successful + Network Token Provision Failed Notifications<br>3. GET response: Card, Account Updater (enrolled status) and Network Token (failed status) objects are available<br>Same Card Data</p>                          |
| 4207670264522669 | 10/26       | Valid                     | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Enrollment Successful + Network Token Provision Failed Notifications<br>3. GET response: Card, Account Updater (enrolled status) and Network Token (failed status) objects are available<br>Same Card Data</p>                          |
| 4327390068355738 | 12/23       | Updated                   | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Enrollment Successful + Network Token Provision Failed Notifications<br>3. GET response: Card, Account Updater (enrolled status) and Network Token (failed status) objects are available<br>Updated Card Number and Expiration Date</p> |
| 4549612182636736 | 3/23        | Account non-participating | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Enrollment Successful + Network Token Provision Failed Notifications<br>3. GET response: Card, Account Updater (enrolled status) and Network Token (failed status) objects are available<br>Same Card Data</p>                          |
| 5122350100384503 | 5/25        | Updated                   | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Enrollment Successful + Network Token Provision Failed Notifications<br>3. GET response: Card, Account Updater (enrolled status) and Network Token (failed status) objects are available<br>Updated Card Number and Expiration Date</p> |
| 5122351100114502 | 6/25        | Valid                     | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Enrollment Successful + Network Token Provision Failed Notifications<br>3. GET response: Card, Account Updater (enrolled status) and Network Token (failed status) objects are available<br>Same Card Data</p>                          |
| 5122351100004505 | 7/25        | Expired                   | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Enrollment Successful + Network Token Provision Failed Notifications<br>3. GET response: Card, Account Updater (enrolled status) and Network Token (failed status) objects are available<br>New Expiration Date</p>                     |
| 5022351100004506 | 8/25        | Failed                    | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Enrollment Failed + Network Token Provision Failed Notifications<br>3. GET response: Card, Account Updater (failed status) and Network Token (failed status) objects are available<br>Same Card Data</p>                                |

**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](/cmp/developer-resources/guides/testing/3ds.md).

### Method 3a : Network Token Provisioning for Visa/Mastercard Cards with Networks <a href="#method-3a--network-token-provisioning-for-visamastercard-cards-with-networks" id="method-3a--network-token-provisioning-for-visamastercard-cards-with-networks"></a>

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

Note that these are testcards from the networks and not real network BINs, hence the attribute properties may not be accurate or consistent for the test cards.

**For test cards to validate Visa Network Tokens, please contact** [**VGS Support**](mailto:support@vgs.io) **or your designated VGS implementation representative.**

| Card Number      | Expiration Date | Expected Response                                                                                                                                                                                                                                                                                                                      |
| ---------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 2222690420064574 | 6/27            | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Enrollment Successful/Failure + Network Token Provision Successful (+ sometimes Activated) Notifications<br>3. GET response: Card, Account Updater (enrolled or failed status) and Network Token (active or activated status) objects are available</p> |
| 2222690420064582 | 7/27            | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Enrollment Successful/Failure + Network Token Provision Successful (+ sometimes Activated) Notifications<br>3. GET response: Card, Account Updater (enrolled or failed status) and Network Token (active or activated status) objects are available</p> |
| 5120350100064594 | 8/27            | <p>1. Sync response: Card Object Creation Successful<br>2. Async notification: Enrollment Successful/Failure + Network Token Provision Successful (+ sometimes Activated) Notifications<br>3. GET response: Card, Account Updater (enrolled or failed status) and Network Token (active or activated status) objects are available</p> |

### Method 4a : Discover NT Test Cards (Direct to Network) <a href="#method-3a--network-token-provisioning-for-visamastercard-cards-with-networks" id="method-3a--network-token-provisioning-for-visamastercard-cards-with-networks"></a>

<table><thead><tr><th width="249.78125">Use Case</th><th width="240.6092529296875">Test Card Number</th><th width="123.9417724609375">HTTP Status</th><th>Error Code</th></tr></thead><tbody><tr><td>Token Provisioning / Single Token - Happy Path<br><br>Bulk Provision Token Request - Happy Path</td><td>6011000025883707<br>6011012015750069<br>6011000024700456<br>6011000068300544<br>6011012021880256</td><td>200</td><td>0</td></tr><tr><td>Token Provisioning / Single Token - Happy Path - NO PAR<br><br>Bulk Provision Token Request - Happy Path - NO PAR</td><td>6011222244446666<br>6011222244449728</td><td>200</td><td>0</td></tr><tr><td>Token Provisioning / Multiple Tokens - Happy Path</td><td>6011000088618537</td><td>200</td><td>0</td></tr><tr><td>Token Provisioning - Invalid Card</td><td>6011005199449433</td><td>400<br></td><td>10001</td></tr><tr><td>Token Provisioning - Ineligible PAN</td><td>6011005199449441</td><td>400</td><td>10002</td></tr><tr><td>Token Provisioning - Provisioning Count Exceeded</td><td>6011005199449458</td><td>400</td><td>10003</td></tr><tr><td>Token Provisioning - Cryptographic Error</td><td>6011005199449466</td><td>400</td><td>10004</td></tr><tr><td>Token Provisioning - Card Identifier Validation Failed</td><td>6011005199449474</td><td>400</td><td>10006</td></tr><tr><td>Token Provisioning - Account/User Cannot Be Added</td><td>6011005199449482</td><td>400</td><td>10007</td></tr><tr><td>Token Provisioning - Account is already provisioned in the wallet</td><td>6011005199449490</td><td>400</td><td>10009</td></tr><tr><td>Token Provisioning - Name Verification Failed</td><td>6011005199449508</td><td>400</td><td>10010</td></tr><tr><td>Token Provisioning - Expired Card</td><td>6011005199449516</td><td>400</td><td>10012</td></tr><tr><td>Token Provisioning - User Locked</td><td>6011005199449524</td><td>400</td><td>10013</td></tr><tr><td>Token Provisioning - Incorrect Account Details</td><td>6011005199449532</td><td>400</td><td>10014</td></tr><tr><td>Token Provisioning - Invalid Token Requestor Id</td><td>6011005199449540</td><td>400</td><td>10020</td></tr><tr><td>Token Provisioning - API Request Valid/Unexpected Error</td><td>6011005199449557</td><td>400</td><td>30001</td></tr><tr><td>Token Provisioning - API Request Valid/Downstream System Unavailable</td><td>6011005199449565</td><td>400</td><td>30001</td></tr><tr><td>RED-FLOW PAN - Declined Response</td><td>6011012020630389<br>6011000000006548</td><td>200</td><td>non-zero<br>error code</td></tr></tbody></table>

### Method 4b: Discover NT Test Cards (VGS Mock Cards) <a href="#method-3a--network-token-provisioning-for-visamastercard-cards-with-networks" id="method-3a--network-token-provisioning-for-visamastercard-cards-with-networks"></a>

| Test Card        | Expiration | Notification Event |
| ---------------- | ---------- | ------------------ |
| 6599991849593102 | 12/99      | Card Updated       |
| 6599993413164757 | 12/99      | Suspended          |
| 6599992553419286 | 12/99      | Activated          |
| 6599993276483500 | 12/99      | Deleted            |
| 6599993056413958 | 12/99      | Active             |
| 6599993767242381 | 12/99      | Failed             |

### Method 5: Amex NT Test Cards (VGS Mock Cards) <a href="#method-3a--network-token-provisioning-for-visamastercard-cards-with-networks" id="method-3a--network-token-provisioning-for-visamastercard-cards-with-networks"></a>

<table><thead><tr><th width="249.78125">Test Card</th><th width="191.9302978515625">Expiration</th><th width="179.850830078125">Notification Event</th></tr></thead><tbody><tr><td>340000104332183</td><td>12/99</td><td>Card Updated</td></tr><tr><td>340000196001332</td><td>12/99</td><td>Suspended</td></tr><tr><td>340000890838633</td><td>12/99</td><td>Activated</td></tr><tr><td>340000794026541</td><td>12/99</td><td>Deleted<br></td></tr><tr><td>340000235116158</td><td>12/99</td><td>Active</td></tr><tr><td>340000594078163</td><td>12/99</td><td>Failed</td></tr></tbody></table>

**Note:**&#x20;

1. We recommend reviewing our [Forward-Compatible API Integration Guidelines](/cmp/platform/overview.md#forward-compatible-api-integration) 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.
2. 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.
3. While American Express (Amex) does not currently support test cards in their sandbox environment Network Tokens, VGS provides mock cards designed to simulate various testing scenarios&#x20;
4. VGS Mock Cards are internally built test cards that do not communicate with the networks.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.verygoodsecurity.com/cmp/developer-resources/guides/testing/create-card.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.