Real-time Account Updater FAQs

What card brands are supported on Real-time Account Updater?

Only Visa cards are supported for real-time Account Updater with TabaPay.

📘

Want to know why?

Email us at [email protected] and we can geek out on why we only support Visa cards at this time.

Why does real-time account updater only work when there is no CVV2?

  • Real Time VAU is a service that updates card information automatically during the authorization process for transactions where the CVV2 is not present.
  • CVV2 is a security feature that verifies the physical possession of the card and is used for transactions where the card is present or the cardholder enters the CVV2 online.
  • Real Time VAU does not work when the CVV2 is present because it would compromise the security of the transactions and the cardholders.

Are all Visa cards covered with Real-time Account Updater?

All Visa cards, domestic and international, participate in Real-time Account Updater

Can 3D-Secure and Real-time Account Updater co-exist in a transaction?

No; the reasoning is analogous to CVV2.

⚠️

Mitigating Excessive Retries

TabaPay Clients who choose to enable Real Time Account Updater must be aware of Visa Excessive Retry Fees as well as MasterCard Transaction Processing Excellence programs. Without proper controls against updated credentials, excessive retry fees may increase.

The efficacy of tools TabaPay Risk & Fraud tools are heavily dependent on the client consuming the response back from the card network when the card, and only attempting a re-try on the card when they are allowed to.

If a payment credential is in bad standing because of it being invalid/closed/expired etc, re-attempting an authorization with TabaPay will result in undesired Excessive Retry Fees.

Category 1 - Issuer Will Never Re-approve Attempts TabaPay clients must not reattempt a transaction declined with a Category 1 decline response code; any reattempt to authorize will be assessed a fee.

  • 14 (Invalid account number)
  • 46 (Closed account)

Category 3 - Data Quality where re-attempt is permitted up to 15 times in 30 days.

  • 54 (Expired card)

What to do for Network Response Code 14/46/54:

TabaPay will return Payment Account Reference in Create Transaction API Response, and this reference will help the client avoid re-trying on the same card.

TabaPay Real Time Visa Account Updater enables you to securely process transactions using TabaPay's Unified API using the most up-to-date card credential. You can access issuer-provided updates when card credentials change, therefore reducing the need to rely on customers to provide updates themselves. TabaPay responds and provides account number or expiration date updates, closed account advices, and contact cardholder advices in real-time using TabaPay's Unified API response

This drives incremental value by increasing speed-to-update payment information.


Real Time Account Updater Response

Possible Real Time Account Updates

CodeValue
AAccount number change message
CClosed account advice
EExpiration date change message
NNon-Participating BIN
OOpt out a cardholder
QContact cardholder advice
PParticipating BIN, No Match
VMatch made, account number and expiration date unchanged.

Error Codes

Response CodeDescription
VAU001Transaction did not qualify for Real Time VAU because the transaction contains token
VAU002Real Time VAU is supported only for Visa branded PAN.
VAU003Real Time VAU is not supported for this network
VAU004Transaction is not original purchase, bill payment, account funding, or original credit.
VAU005Transaction contains CVV2.
VAU006Transaction is not a qualifying transaction type. It needs to be recurring or installment type or Credential-on-file transaction.
VAU007Real Time VAU is not supported for this merchant category code (MCC).
VAU008Acquirer or processor is not activated for Real Time VAU.
VAU009Issuer does not support Real Time VAU
VAU010Issuer or Visa blocked the merchant
VAU011Preauthorized Payment Cancellation Service (PPCS) stop-payment order for this transaction.
VAU012Credentials in the authorization request is the latest VAU data
VAU013Transaction did not qualify for Real Time VAU as the expiry date in the authorization request is later than the expiry date in VAU data.
VAU014PAN has been opted out of VAU.
VAU015Transaction is a face-to-face transaction type.
VAU016PAN has stop advice setup

Billable Events

Only the following codes result in a billable event.

CodeValue
AAccount number change message
CClosed account advice
EExpiration date change message
QContact cardholder advice


Did this page help you?