Skip to main content

AccountUpdater

POST 

/AccountUpdater

This endpoint accepts a list of card data that will be checked for updated card expiration. You can pass either tokens or PANs in the data field of the request. There is a maximum of 100 cardData objects that can be included per request.

Test Card Numbers

Important Test PAN Numbers

TokenEx test PANs can be leveraged to verify that the call to the Account Updater endpoints and subsequent response codes are successful. Some of the test cards are NOT Luhn compliant and will not pass validation for tokenization. When tokenizing these test cards, please select a token scheme that does not require Luhn validation i.e. sixANTOKENfour. The requests to trigger the specific response codes are outlined in the REQUEST section.

PANDescription
4327390068355738Account Number Updated
4680056031099387Account Expiration Date Updated
4207670264522669Valid Account, No Update
4403933787254356Account is Closed
4000220720915104Contact Cardholder
4929423647273009No Match
4549612182636736Non-Participating Account

Response Code and Message Mappings

Response codeDescription
801Account Number Updated
802Account Expiration Date Updated
800Valid Account, No Update
803Account is Closed
804Contact Cardholder
805Cardholder Opt Out
806No Match
807Non-participating Account
808Error Occurred Updating Account
809Rejected

Error cases

ErrorDescription
8014Cannot update accounts. CardData items cannot exceed 100
8015Sequence numbers must be unique for each card
8016Connection error occurred within the chain of communication required to obtain account update. Please retry request
8017Sequence numbers must be numeric
2100Input data not Luhn compatible
3000Token does not exist

Request

Header Parameters

    tx-tokenize boolean

    Specifies that the incoming data is a PAN and should be tokenized

    tx-token-scheme stringrequired

    Specifies the token scheme to be used when tokenizing

    tx-account-updater-merchantid string

    Specfies the merchantID to be used

    tx-return-plaintext-pan boolean

    Specifies that plaintext PANs should be returned if there is an Account Number Update. AllowPlainTextPan permission must be enabled to utilize this functionality.

    tx-acquirer-segment-id string

    Specifies which Visa region to send the request to when needed. The US and EU endpoints default to the appropriate value. The sandbox value is 2. The US Prod value is 973. The EU Prod value is 982.

Body

    cardData

    object[]

    required

    The card data to be processed

  • Array [

  • data stringrequired

    The PAN to be tokenized or the token to be detokenized

    Default value: 4111111111111111
    expiration stringrequired

    The expiration for the card in MMYY format

    Default value: 1123
    sequenceNumber stringrequired

    The sequence number used for keeping track of which cards succeeded and which failed. Each sequenceNumber must be unique per request.

    Default value: 01
  • ]

  • subMerchantName string

    The Sub-merchant name to be used in the request.

    acquirerOrMerchantProprietaryInfo string

    If provided, it contains merchant proprietary information such as a customer ID that is carried in the merchant’s back-end system

Responses

200

Schema

    oneOf

    cardData

    object[]

  • Array [

  • success boolean
    Default value: true
    Example: true
    sequenceNumber string
    Example: 01
    token string
    Example: token
    expiration string
    Example: 1123
    updatedExpiration string
    Example: 1124
    message string
    Example: Account Expiration Date Updated
    responseCode integer
    Default value: 0
    Example: 802
  • ]

  • referenceNumber string
    Example: 2201291553541132129
    success boolean
    Default value: true
    Example: true
    error string
    Example:
    message string
    Example:
Loading...