# 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 Card Number | Test CardIDs | Expiration Date | Notification Event-Triggered | VGS Event | Expected Responses | | ---------------- | ---------------------------------------------------- | --------------- | ---------------------------- | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 5100260000079200 | CRDnKQt89XXFRQVBEzcRvkhvmhs5rpBvxkv3PbeAFPB52zFFqjCR | 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 | CRDqKgQbzM9cUWNUAQR5EFu9BrZuSLP5tgqxadbJBJdqgc2iKQ5i | 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 | CRDoy3ak2ipNi9Fac1tugukHQQi2JWkKdutozwHdd9MWZk9tj31J | 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 | CRDnedYQWP8U4qLZ8dELJTPa3iC3A9ANryT53dAeL8Nmdg21YnZ0 | 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 | CRDnExWG9xEu5khrT6Xw3pqi6CEtVei3yeogHgD8GG7jR6fxK2af | 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 | CRDrcHw9DHbRtEQxzWbh86qnAinGiah7QVbFDnZX9jCUqCX78J30 | 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 | CRDKfukrUmMsUdotydKS4euZ1v2exoN617mWi7avaehqkYh2J5JP | 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 | CRDqL55P51GVUMbZMDgYakHQTJSoFP2e8NoMXzhQpVPgLh91ZEQo | 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 | CRDqoPvUouevmR2sqLGixGh8W7mzwPoveweDNoWSbYRQoWdUbCzd | 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

| | 4000210000059201 | CRDoy8VqBYLSYpnYXQcgQuQpTfcT9LtQxaBmUrJdZNckTDoE4Xk5 | 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

| | 4000210000049202 | CRDM6fByTJLfGy6fPTp8g65JmWLBJ35hH9AsjU2vz2mY2C4rx87q | 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

| | 4000210000039203 | CRDnEyXHMB8oWJg7ij2gHUkLCzZz8NaXjSB4GkJkwJqNUNNDEEbo | 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 | CRDnER9L5RRdhgLpJH96hNEizvAqhvkRswXYfsS4dspXaAVaHmtM | 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

| | 4000210000019205 | CRDnExMybKBt8N1R3TWjzAyRr8UAbYNJEMpgWguoYBiLxU5rmDpu | 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

| | 4000210000009206 | CRDneB3zHjoDQW9xLKBeF9KtjJhb6eR134XjfPPyisqpcQpmAEHx | 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

| | 4000210000099207 | CRDoCww5soTmXA7sqtUQ3mS8b8ZAmhHCguWyvMhWMAQLU9UJcFUn | 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 | CRDrc6FX3HbucdEvQCHha7Tkqa2TMT66xV9QDrNzh72NB5mw2R7u | 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

| | 4000210000079209 | CRDoy9WqbTDwadttfKbWSTcbSnYddb8i5naGmDprK4BLBzbCawHg | 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

| | 3400000000829200 | CRDqoPvUouevmR2sqLGixGh8W7mzwPoveweDNoWSbYRQoWdUbCz0 | 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

| | 3400000000909200 | CRDoy8VqBYLSYpnYXQcgQuQpTfcT9LtQxaBmUrJdZNckTDoE4Xk1 | 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

| | 3400000001089200 | CRDM6fByTJLfGy6fPTp8g65JmWLBJ35hH9AsjU2vz2mY2C4rx872 | 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 | CRDnEyXHMB8oWJg7ij2gHUkLCzZz8NaXjSB4GkJkwJqNUNNDEEb3 | 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

| | 3400000001169200 | CRDoCww5soTmXA7sqtUQ3mS8b8ZAmhHCguWyvMhWMAQLU9UJcFU2 | 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 | CRDnER9L5RRdhgLpJH96hNEizvAqhvkRswXYfsS4dspXaAVaHmt4 | 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

| | 3400000004219200 | CRDnExMybKBt8N1R3TWjzAyRr8UAbYNJEMpgWguoYBiLxU5rmDp5 | 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

| | 6599990002379200 | CRDnER9L5RRdhgLpJH96hNEizvAqhvkRswXYfsS4dspXaAVaHmt5 | 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 | CRDqoPvUouevmR2sqLGixGh8W7mzwPoveweDNoWSbYRQoWdUbCz6 | 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

| | 6599990002529200 | CRDoy8VqBYLSYpnYXQcgQuQpTfcT9LtQxaBmUrJdZNckTDoE4Xk7 | 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

| | 6599990002609200 | CRDM6fByTJLfGy6fPTp8g65JmWLBJ35hH9AsjU2vz2mY2C4rx878 | 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

| | 6599990002869200 | CRDneB3zHjoDQW9xLKBeF9KtjJhb6eR134XjfPPyisqpcQpmAEHb | 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

| | 6599990002949200 | CRDnExMybKBt8N1R3TWjzAyRr8UAbYNJEMpgWguoYBiLxU5rmDpb | 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 | CRDoCww5soTmXA7sqtUQ3mS8b8ZAmhHCguWyvMhWMAQLU9UJcFUc | 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 | CRDnEyXHMB8oWJg7ij2gHUkLCzZz8NaXjSB4GkJkwJqNUNNDEEbc | 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

| 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](/cmp/developer-resources/notifications.md) 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 |

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

| | 510026\*\*\*\*\*\*9201 | 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

| | 510026\*\*\*\*\*\*9202 | 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

| | 510026\*\*\*\*\*\*9203 | 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

| | 510026\*\*\*\*\*\*9204 | 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

| | 510026\*\*\*\*\*\*9205 | 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

| | 510026\*\*\*\*\*\*9206 | 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

| | 510026\*\*\*\*\*\*9207 | 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

| | 400021\*\*\*\*\*\*9200 | 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

| | 400021\*\*\*\*\*\*9201 | 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

| | 400021\*\*\*\*\*\*9202 | 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

| | 400021\*\*\*\*\*\*9203 | 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

| | 400021\*\*\*\*\*\*9204 | 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

| | 400021\*\*\*\*\*\*9205 | 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

| | 400021\*\*\*\*\*\*9206 | 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

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

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

| | 400021\*\*\*\*\*\*9209 | 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

| ### 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](https://www.dcode.fr/luhn-algorithm) #### 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](https://www.dcode.fr/luhn-algorithm). | 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](/cmp/developer-resources/api/account-updater-events.md). --- # 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/account-updater-webhooks.md?ask= ``` 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.