Account Updater Webhooks

Account Updater Webhooks - Mock Testing

You can test the various Account Updater notifications using the the mocks and the following methods:

Method 1: Fixed Card Numbers for Specific Responses

Using specific card numbers with the Create Card API, you can simulate fixed Account Updater notifications. The following table lists card numbers and the corresponding Account Updater notifications you will receive upon making enrollment/create card request:

Test Cards

Expiry Date

Notification Event-Triggered

VGS Event

Expected Responses

5100260000079200

Any Future Date

Valid

cmp_au_card.enrolled

1. Sync response: Card Object Creation Successful 2. Async notification: Enrollment Valid/Successful Notification 3. GET response: Card and Account Updater (enrolled status + event = valid field (same card data)) objects are available

5100260000069201

Any Future Date

Updated

cmp_au_card.updated

1. Sync response: Card Object Creation Successful 2. Async notification: Card Update Notification 3. GET response: Card and Account Updater (enrolled status + event = updated field (new pan and expiration date)) objects are available

5100260000059202

Any Future Date

Expired

cmp_au_card.expired

1. Sync response: Card Object Creation Successful 2. Async notification: Card Expired Notification 3. GET response: Card and Account Updater (enrolled status + event = expired field (new expiration date)) objects are available

5100260000049203

Any Future Date

Closed

cmp_au_card.closed

1. Sync response: Card Object Creation Successful 2. Async notification: Card Closed Notification 3. GET response: GET response: Card and Account Updater (enrolled status + event = closed field (same card data)) objects are available

5100260000039204

Any Future Date

Non_participating

cmp_au_card.non_participating

1. Sync response: Card Object Creation Successful 2. Async notification: Card Non_Participating Notification 3. GET response: Card and Account Updater (enrolled status + event = non_participating field (same card data)) objects are available

5100260000029205

Any Future Date

Unknown

cmp_au_card.unknown

1. Sync response: Card Object Creation Successful 2. Async notification: Card Unknown Notification 3. GET response: Card and Account Updater (enrolled status + event = unknown field (same card data)) objects are available

5100260000019206

Any Future Date

Enrolment Successful

cmp_au_card.enrolled

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

5100260000009207

Any Future Date

Enrolment Failed

cmp_au_card.enrollment_failed

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

4000210000069200

Any Future Date

Updated

cmp_au_card.updated

4000210000059201

Any Future Date

Expired

cmp_au_card.expired

4000210000049202

Any Future Date

Closed

cmp_au_card.closed

4000210000039203

Any Future Date

Contact cardholder advice

cmp_au_card.contact_cardholder_advice

1. Sync response: Card Object Creation Successful 2. Async notification: CardHolder Advice Notification 3. GET response: Card and Account Updater (enrolled status + event = contact_cardholder_advice field (same card data) objects are available

4000210000029204

Any Future Date

Valid

cmp_au_card.enrolled

4000210000019205

Any Future Date

Non participating

cmp_au_card.non_participating

4000210000009206

Any Future Date

Unknown

cmp_au_card.unknown

4000210000099207

Any Future Date

Opt out

cmp_au_card.opt_out

1. Sync response: Card Object Creation Successful 2. Async notification: Card Opt_Out Notification 3. GET response:Card and Account Updater (enrolled status + event = opt_out field (same card data)) objects are available

4000210000089208

Any Future Date

Enrolment Successful

cmp_au_card.enrolled

4000210000079209

Any Future Date

Enrolment Failed

cmp_au_card.enrollment_failed

3400000000829200

Any Future Date

Updated

cmp_au_card.updated

3400000000909200

Any Future Date

Expired

cmp_au_card.expired

3400000001089200

Any Future Date

Closed

cmp_au_card.closed

1. Sync response: Card Object Creation Successful 2. Async notification: Card Closed Notification 3. GET response: Card and Account Updater (enrolled status + event = closed field (same card data)) objects are available

3400000001329200

Any Future Date

Contact Cardholder Advice

cmp_au_card.contact_cardholder_advice

3400000001169200

Any Future Date

Opt Out

cmp_au_card.opt_out

1. Sync response: Card Object Creation Successful 2. Async notification: Card Opt_Out Notification 3. GET response: Card and Account Updater (enrolled status + event = opt_out field (same card data)) objects are available

3400000001249200

Any Future Date

Enrolment Successful

cmp_au_card.enrolled

3400000004219200

Any Future Date

Enrolment Failed

cmp_au_card.enrollment_failed

6599990002379200

Any Future Date

Valid

cmp_au_card.enrolled

1. Sync response: Card Object Creation Successful 2. Async notification: Card Enrollment Valid/Successful Notification 3. GET response: Card and Account Updater (enrolled status + event = valid field (same card data)) objects are available

6599990002459200

Any Future Date

Updated

cmp_au_card.updated

6599990002529200

Any Future Date

Expired

cmp_au_card.expired

6599990002609200

Any Future Date

Closed

cmp_au_card.closed

6599990002869200

Any Future Date

Unknown

cmp_au_card.unknown

6599990002949200

Any Future Date

Enrolment Successful

cmp_au_card.enrolled

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

6599990003109200

Any Future Date

Enrolment Failed

cmp_au_card.enrollment_failed

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

6599990003289200

Any Future Date

Contact cardholder advice

cmp_au_card.contact_cardholder_advice

Known Fact about Account Updater Notifications Mock Implementation:In the mock environment, the synchronous response from the Create Card API returns the expected cardID—which matches the Account Updater notifications—and accurately replicates the card number, BIN, first 8 digits, and last 4 digits as provided in the request. However, the address and expiration date fields in the mock response will not match the values from the original request.

Method 2: Any PAN with Specific Mastercard or Visa Bins + Last4

You can also test Account Updater notifications by using any PAN (Primary Account Number) that starts with the Mastercard BIN (510026) or Visa BIN (400021) and ends with a last4 in the range 9200-9209. Simply trigger the Create Card/Enrollment process using these PANs. In the Account Updater notifications, three new fields have been added to provide more detailed card information: "card_first8", "card_bin", and "card_last4". These fields will appear in the following Account Updater notifications:

cmp_au_card.contact_cardholder_advice
cmp_au_card.closed
cmp_au_card.expired
cmp_au_card.updated

To receive these notifications please ensure to set up the webhook URL on the dashboard. See here for details on notification set-up.

Test Cards

Expiry Date

Notification Event-Triggered

VGS Event

Expected Responses

510026******9200

Any Future Date

Valid

cmp_au_card.enrolled

510026******9201

Any Future Date

Updated

cmp_au_card.updated

510026******9202

Any Future Date

Expired

cmp_au_card.expired

510026******9203

Any Future Date

Closed

cmp_au_card.closed

510026******9204

Any Future Date

Non participating

cmp_au_card.non_participating

510026******9205

Any Future Date

Unknown

cmp_au_card.unknown

510026******9206

Any Future Date

Enrolment Successful

cmp_au_card.enrolled

510026******9207

Any Future Date

Enrolment Failed

cmp_au_card.enrollment_failed

400021******9200

Any Future Date

Updated

cmp_au_card.updated

400021******9201

Any Future Date

Expired

cmp_au_card.expired

400021******9202

Any Future Date

Closed

cmp_au_card.closed

400021******9203

Any Future Date

Contact cardholder advice

cmp_au_card.contact_cardholder_advice

400021******9204

Any Future Date

Valid

cmp_au_card.enrolled

400021******9205

Any Future Date

Non participating

cmp_au_card.non_participating

400021******9206

Any Future Date

Unknown

cmp_au_card.unknown

400021******9207

Any Future Date

Opt-out

cmp_au_card.opt_out

1. Sync response: Card Object Creation Successful 2. Async notification: Card Opt_Out Notification 3. GET response: Card and Account Updater (enrolled status + event = opt_out field (same card data)) objects are available

400021******9208

Any Future Date

Enrolment Successful

cmp_au_card.enrolled

400021******9209

Any Future Date

Enrolment Failed

cmp_au_card.enrollment_failed

Method 3: Account Updater Mock Webhook Notifications with Networks

Visa, Amex and Discover: Account Updater notifications cannot be tested because Visa, Amex and Discover network do not provide a mock environment for webhook notifications.

Mastercard: For Mastercard Account Updater Notification Cards, you can use any Mastercard numbers ending in the following digits:

12: Account Expiration Date Change Notification
22: Account Number Updated Notification
32: Account Closed Notification:
- You can generate random luhn valid card numbers here

Examples of Cards for Triggering Events (Expired, Updated, and Closed)

Below are sample card numbers ending in 12, 22, and 32 that will trigger the respective card events: expired, updated, and closed.

Important Notes:

You will only receive event notifications for cards that generate a 201 - Card Created Successfully response.
For cards that already exist and generate a 303 HTTP Response (i.e., card already exists), no notifications will be sent.
To test the event notifications again, please use a new card number ending in 12, 22, or 32 each time. You can generate these numbers using the Luhn Algorithm tool here.

Example Test Cards

Expiry Date

Network Event

Expected Response

5522351100074512

7/25

Card expiration date change notification will be sent

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

5522351100054522

8/25

Card number updated notification will be sent

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

5522351100034532

9/25

Card closed notification will be sent

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

Account Updater Enrollment Failure Reason Codes

Reason Code

Reason Text

card-brand-not-supported

XXX card brand is not supported.Currently, only Visa and Mastercard cards are supported. This error will be returned if an Amex, Discover, or any other card scheme is used.

declined

Vgs merchant not found. This error typically indicates that the customer has not been onboarded to use the account updater with the provided vault credentials.

internal-server-error

Something went wrong.

Notifications Set Up

You can configure a webhook to receive updates for Account Updater. For detailed instructions on setting up notifications, click here.

PreviousRequest Cryptogram NextNetwork Tokens Webhooks

Last updated 19 days ago