Sending an invalid payment account notification

Understand why a shopper's invalid payment account triggers a notification.

When processing transactions, it's crucial to ensure that the payment information is accurate and up-to-date. There are instances when a payment cannot be processed due to invalid account details, such as when a card has been reported lost or stolen or an account has been closed. In these situations, a specific protocol is triggered, prompting a need for immediate action to update the payment information. This document outlines the process for sending notifications related to invalid payment accounts, ensuring businesses can swiftly rectify any issues and maintain a seamless transaction process.

This notification triggers when the partnering bank returns a "Contact Customer" message for stolen or lost cards or an “Account Closed” message for deactivated accounts. See Card Account Updater for more information. You need to contact the shopper to get updated information.

Notification trigger

When a transaction is processed and encounters issues with the payment account's validity, a notification is triggered to inform the necessary stakeholders. This typically occurs under two circumstances:

• Stolen or Lost Cards: If the partnering bank reports a card as stolen or lost (Contact Customer).

• Deactivated Accounts: If an account has been closed or deactivated (Account Closed).

Upon receiving one of the following response codes from a reconciler job, the system automatically initiates a notification:

• AccountClosed – The payment account associated with the transaction has been closed.

• Contact – Indicates a need to contact the customer for additional information due to potential issues with their payment method, such as a reported lost or stolen card.

It is crucial to promptly contact the customer to obtain updated payment information, ensuring transactions can proceed without unnecessary delays.