Card Update - emvchipupdatetxn
This section describes the message parameters for EMV Card Update transaction processing, which you can submit using the XML API integration method. Refer to the Integration Methods section for more information.
emvchipupdatetxn transaction updates the system with information from the chip card. The chip card may update the transaction data after the Issuer information has been received from the
If the chip card accepts the Issuer authorization (does not decline by card), submit
emvchipupdatetxn to complete the transaction.
In this section:
For the entire list of API endpoints, refer to API Endpoints.
|Field name||Description||Required||Length||Data type|
Elavon-assigned Converge Account ID (AID).
|Required||6 or 7||numeric|
|Converge User ID|
The user ID with Hosted Payment API User status that can send transaction requests through the terminal.
Unique identifier of the terminal that will process the transaction request and submit to the Converge gateway.
Unique identifier of the previously approved Sale (
|[Integrated Circuit Card]|
|Issuer Script Results|
Describes the results of the terminal script processing.
|Transaction Status Information|
Digital version of the cardholder’s signature.
|Signature Image Format|
File format of the signature image.
|Transaction Result Message|
A result of SUCCESS indicates that the system was updated.
Unique identifier of the transaction.
|[Error]||Returned only if an error occurs. Refer to the Error Codes section for more information.|
Typically, when the transaction failed validation or the request is incorrect. This will prevent the transaction from going to authorization. This is a numeric field.
Detailed explanation of the error. This field may be changed based on merchant configuration in the user interface.
Error name or reason for the error.