Skip to main content
The real time account updater automatically checks for updated card details at the point of a decline. Where new card details are available, the payment method is updated and the transaction is retried with the same connector. This approach requires no integration changes.

​
Setup

To have the real time account updater enabled on your instance please fill out this form. The enrollment happens directly with the card schemes and may take up to two weeks. The customer support team may reach out with more questions if needed. If you’re already enrolled for this service with the schemes, filling out the form is still required to set up the necessary data points in the systems as well as the downstream partner’s system.

​
Usage and limitations

The real-time account updater has the following limitations.
  • Only card PANs are supported. Digital wallet and network tokens are ignored.
  • Only subsequent merchant initiated transactions are supported
  • One of the following error codes is returned, or a MAC 01 is returned
    • canceled_payment_method
    • expired_payment_method
    • incorrect_expiry_date
    • issuer_decline
  • Only Visa & Mastercard are currently supported
  • Cards with pending updates from the batch account updater use the new stored credentials instead
As with other updates, merchants are only charged for cards that are updated.

​
Simulator

Your sandbox instance is automatically enabled to use the real time account updater simulator. You can test different scenarios by using the connection_options property when creating a transaction. Please see the various scenarios and examples below.
Using the card simulator connection is the easiest way to test different scenarios as this connector returns specific decline error codes depending on the transaction amount.
The real time account updater logic only triggers for subsequent merchant initiated transactions so you must first create a stored payment method. Once you have this payment method ID you can use it to test as shown when calling the POST /transactions API. 
{
  "amount": 200005,
  "country": "US",
  "currency": "USD",
  "payment_service_id": "f6933999-362f-468b-83c3-ed16b1a4ca17",
  "merchant_initiated": true,
  "payment_source": "card_on_file",
  "is_subsequent_payment": true,
  "payment_method": {
    "method": "id",
    "id": "f6933999-362f-468b-83c3-ed16b1a4ca17",
    "redirect_url": "https://gr4vy.com/callback"
  },
  "connection_options": {
    "account-updater": {
      "response_code": "updated",
      "account_number": "4242424242424242"
    }
  }
}

​
Examples

The following are a few examples of how to use the connection_options to trigger particular situations. 
{
{
  ...
  "connection_options": {
    "account-updater": {
      "response_code": "updated",
      "account_number": "4242424242424242",
      "expiration_month": "12",
      "expiration_year": "2050"
    }
  }
}