Return - emvchipreturn

EMV return lets Converge users process refunds of a settled transaction. EMV Chip Return is available for both credit card and debit card EMV chips.

EMV Chip Returns can only affect a settled transaction.

Users can make partial returns linked to the same transaction. Converge will return an error 5091 if a return would cause the total returns issued on a settled transaction to exceed the original amount paid on the settled transaction.

In this section:


Field name Description Required Length Data type
ssl_merchant_id Merchant ID
Elavon-assigned Converge account ID.
Required 15 numeric
ssl_user_id Converge User ID
The user ID with Hosted Payment API User status that can send transaction requests through the terminal.
Required 15 alphanumeric
ssl_pin Terminal ID
Unique identifier of the terminal that will process the transaction request and submit to the Converge gateway.


The ssl_user_id sending the transaction request must be associated with the terminal that will process the request.

Required 64 alphanumeric
ssl_transaction_type Transaction Type
Valid value: emvchipreturn
Required 20 alphanumeric
ssl_txn_id Transaction ID
Unique identifier of the approved EMV Chip Sale (emvchipsale) transaction to be refunded or the approved EMV Chip Auth Only (emvchipauthonly) transaction to be completed.
Required 46 alphanumeric
ssl_tlv_enc Encrypted Tag Length Value
Data defining the EMV record. The data includes the following:
Total Authorization Amount
Tip Amount (if available)
Required 4 hex
ssl_pos_mode POS Device Data Entry Capability
Indicates how the POS device captures card data.
Valid values:
02 - Swipe-capable
03 - Proximity or contactless-capable
Optional 2 numeric
ssl_entry_mode Transaction Entry Indicator
Indicates how the track data was captured.
Valid values:
03 - Swiped (default)
04 - Proximity/Contactless
Optional 2 numeric




  • In this example, you will have to change the data values, such as my_merchant_id, my_user_id, 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.