Reversal - emvreverse
This section describes the message parameters for EMV Card Reversal transaction processing, which you can submit using the XML API integration method. Refer to the Integration Methods section for more information.
emvreverse transaction reverses an approved authorization from an
emvchipsale transaction after a decline by card is received from the Chip card. The Chip card may decline the transaction data even after an Issuer approval, in this case a reversal must be sent to restore the funds back to the card. This action can be performed within 5 minutes after an
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 (
|Transaction Result Message|
A result of SUCCESS indicates that transaction was reversed.
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.
- In this example, you will have to change the data values, such as
my_pin, and transaction data to match your Converge account and meet the needs of your website.
- Code samples provided are for demonstration only and should not be used for live transactions. All sensitive merchant data, including transaction amounts and your Converge credentials, should be placed in server side code.
xmldata= <txn> <ssl_merchant_id>my_merchant_id</ssl_merchant_id> <ssl_user_id>my_user_id</ssl_user_id> <ssl_pin>my_pin</ssl_pin> <ssl_transaction_type>emvreverse</ssl_transaction_type> <ssl_txn_id></ssl_txn_id> </txn>