accountUpdater
The accountUpdater element is an optional child of the authorizationResponse, captureResponse, echeckSalesResponse, echeckcreditResponse, echeckVerificationResponse, forceCaptureResponse, and saleResponse elements. This element is included in the response messages when the submitted account information has changed.
In the case of Direct Debit accounts, the system automatically updates the information sent to the ACH network and includes the original and updated information in the response. Similarly, if you use the Account Updater service (for credit cards), the system automatically repairs the card information sent to the card networks and depending upon the option you select, can return the info to you.
Parent Elements:
authorizationResponse, captureResponse, forceCaptureResponse, echeckCreditResponse, echeckRedepositResponse, echeckSalesResponse, saleResponse
Attributes:
None
Child Elements:
accountUpdateSource, extendedCardResponse, newAccountInfo, newCardInfo, newCardTokenInfo, newTokenInfo, originalAccountInfo, originalCardInfo, originalCardTokenInfo, originalTokenInfo
When using Account Updater (any variation), you must always code to receive the extendedCardResponse element and its children. Worldpay always returns this information whenever applicable regardless of whether you receive other account updater information in the transaction response message.
Example: accountUpdater Structure - Credit Cards without extendedCardResponse
<accountUpdater>
<originalCardInfo>
<type>Card Type</type>
<number>Old Account Number</number>
<expDate>Old Expiration Date</expDate>
</originalCardInfo>
<newCardInfo>
<type>Card Type</type>
<number>New Account Number</number>
<expDate>New Expiration Date</expDate>
</newCardInfo>
<accountUpdateSource>R or N</accountUpdateSource>
</accountUpdater>
Example: accountUpdater Structure - Credit Cards with extendedCardResponse
<accountUpdater>
<originalCardInfo>
<type>Card Type</type>
<number>Old Account Number</number>
<expDate>Old Expiration Date</expDate>
</originalCardInfo>
<newCardInfo>
<type>Card Type</type>
<number>New Account Number</number>
<expDate>New Expiration Date</expDate>
</newCardInfo>
<extendedCardResponse>
<message>Code Description</message>
<code>Either 501 or 504</code>
</extendedCardResponse>
<accountUpdateSource>R or N</accountUpdateSource>
</accountUpdater>
Example: accountUpdater Structure - Credit Cards only extendedCardResponse
<accountUpdater>
<extendedCardResponse>
<message>Code Description</message>
<code>Either 501 or 504</code>
</extendedCardResponse>
<accountUpdateSource>R or N</accountUpdateSource>
</accountUpdater>
Example: accountUpdater Structure - Credit Cards (tokenized Merchant)
This structure can also include the <extendedCardResponse> element.
<accountUpdater>
<originalCardTokenInfo>
<cnpToken>Old Token</cnpToken>
<type>Card Type</type>
<expDate>Old Expiration Date</expDate>
<bin>Old Card BIN</bin>
</originalCardTokenInfo>
<newCardTokenInfo>
<cnpToken>New Token</cnpToken>
<type>Card Type</type>
<expDate>New Expiration Date</expDate>
<bin>New Card BIN</bin>
</newCardTokenInfo>
<accountUpdateSource>R or N</accountUpdateSource>
</accountUpdater>
Example: accountUpdater Structure - Direct Debit (for non-Tokenized Merchant)
<accountUpdater>
<originalAccountInfo>
<accType>Original Account Type</accType>
<accNum>Original Account Number</accNum>
<routingNum>Original Routing Number</routingNum>
</originalAccountInfo>
<newAccountInfo>
<accType>New Account Type</accType>
<accNum>New Account Number</accNum>
<routingNum>New Routing Number</routingNum>
</newAccountInfo>
</accountUpdateFileRequestData>
Example: accountUpdater Structure - Direct Debit (for Tokenized Merchant)
<accountUpdater>
<originalTokenInfo>
<accType>Original Account Type</accType>
<cnpToken>Original Token</cnpToken>
<routingNum>Original Routing Number</routingNum>
</originalTokenInfo>
<newTokenInfo>
<accType>New Account Type</accType>
<cnpToken>New Token</cnpToken>
<routingNum>New Routing Number</routingNum>
</newTokenInfo>
</accountUpdateFileRequestData>