Summary

  • Visa says eligible Real Time VAU transactions can return updated card numbers, expiry dates or account status without the payment being approved. Merchants must apply the information to their billing records.
  • The service carries existing authorized payment relationships across card changes. Issuers also have controls for opting an account out and stopping updates to a particular merchant.

The payment failed. The merchant may nevertheless have acquired something useful: the customer's new card number.

Visa describes that combination in its Account Updater FAQ. An eligible transaction using Real Time VAU does not need to be approved for its response to contain updated account information. A rejected payment and an improved billing record can arrive in the same envelope. The cash drawer stays shut; the address book gets better.

That is an awkward result for a dashboard with only two colours. It also exposes a business function often buried beneath the drama of authorizing a payment. A network can maintain a commercial relationship while the issuer declines the transaction happening right now.

The old relationship gets the new number

Visa Account Updater connects participating issuers, acquirers and qualified merchants. Its service overview lists changes to card numbers and expiration dates, closed-account advice and instructions to contact the cardholder. Renewal and replacement, including replacement after loss or theft, are among the supported circumstances. Names and changes of address are outside that update list.

The practical problem is unglamorous. A customer receives a replacement card. A merchant still has the old credentials on file. Both may want the service and its payments to continue, yet the billing record has fallen behind the account. Someone must bridge the gap before an administrative change becomes a failed renewal.

VAU lets the issuer supply the change, the participating acquirer deliver it and the merchant refresh its records. Visa sells the product as a way to preserve recurring payments and reduce avoidable declines. There is commercial value in sparing customers another form to fill in. There is also value in sparing merchants the discovery that yesterday's perfectly willing customer now has yesterday's card number.

Real Time VAU can do this maintenance during transaction processing. For eligible transactions, account information can be updated before the authorization request goes to the issuer; the response returns updates for the merchant's billing files. The issuer's answer to the payment request has its own job. A decline can coexist with a useful update because the two outcomes answer different questions: will this transaction be approved, and what details now belong in the record?

The merchant still has work to do. Receiving fresh information and using it are separate events. A system that discards everything attached to a declined payment could throw away a repair along with the failure notice.

Continuity is a service, with its own switches

The acquirer services guide describes several delivery paths, including optional Push Subscribe. Through an acquirer, a merchant can subscribe to updates for card numbers it holds. Replacement numbers associated with the same underlying account are automatically included in that subscription. VAU Linking can connect a sequence of submitted changes to the latest account information.

The useful possession is therefore more than one card number. It is the means of keeping an existing billing relationship current as numbers change. A static list ages; an authorized connection to the update system can keep repairing it.

Access has a defined starting point. Visa requires acquirer inquiries to concern accounts for which the merchant has an ongoing customer relationship and the customer has authorized credential-on-file payments. Acquirers qualify merchants, and some merchant categories are excluded. The update serves that existing permission; it supplies no fresh purchasing decision from the customer.

Issuers have controls over the updates themselves. Cardholder opt-out advice can follow a chain of account changes until it is removed or the last relevant update is purged. A more selective Stop Advice can prevent a particular merchant receiving updates for a specified card number while allowing other merchants to receive them. An issuer can also exclude an entire merchant, a wider intervention.

Those are controls over information distribution. Approval governs a transaction. Ending a service relationship has another purpose again. Expecting a replacement piece of plastic to perform all three jobs is a heroic assignment for a small object with a chip in it.

A merchant-level cohort connecting delivered updates to later approved payments and settled receipts is missing from the evidence examined here; that record would establish the value of recovered renewals. The documents establish the mechanism clearly enough to change the questions a business should ask.

Some retained customers have been persuaded to stay. Others always wanted to stay and merely needed their billing record repaired. The revenue matters in both cases. The distinction matters when management decides which department deserves the money for next year's improvement.