Sale - cashsale

This section describes the message parameters for Cash Sale transaction processing, which you can submit using the XML API integration method. Refer to the Integration Methods section for more information.

The cashsale transaction enters a purchase by cash.

In this section:

For the entire list of API endpoints, refer to API Endpoints.


Field nameDescriptionRequiredLengthData type
ssl_merchant_idMerchant ID
Elavon-assigned Converge Account ID (AID).
Required6 or 7numeric
ssl_user_idConverge User ID
The user ID with Hosted Payment API User status that can send transaction requests through the terminal.
ssl_pinTerminal 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.
ssl_transaction_typeTransaction Type
Valid value:  cashsale
ssl_amountTransaction Amount
The Sale amount that includes the Net and Sales Tax amounts.
For Tip Processing, the Sale amount must not include the Tip amount.
Format: Number with 2 decimal places.
[Tip Processing]Use only on terminals that are set up with the Market Segment set to Service
ssl_tip_amountTip or Gratuity Amount
Amount to add or update to the transaction amount.
Format: Number with 2 decimals places
ssl_serverServer ID
Unique identifier of the clerk, waiter, waitress or cashier.
ssl_shiftShift ID
Unique identifier of the time period, course or service type.
Phone number on the cardholder’s / customer’s account or billing address.
Format: Accepts dashes.


Field nameDescription
ssl_resultTransaction Outcome
An ssl_result = 0 indicates an approved transaction.
An ssl_result not equal to 0 indicates a declined and unauthorized transaction.
ssl_result_messageTransaction Result Message
Refer to the Debit Card Response Codes section for an extensive list of possible returned messages.
ssl_txn_idTransaction ID
Unique identifier of the transaction.
ssl_txn_timeProcessing Date and Time
Indicates when Converge processed the transaction.
Format: MM/DD/YYYY hh:mm:ss AM/PM
Example: 03/18/2010 10:34:10 AM
ssl_amountTotal Authorized/Approved Transaction Amount
The amount includes the Tip amount, if submitted in the request.
[Tip Processing]Returned only if Tip parameters are sent in the request.
ssl_base_amountBase Amount
Original transaction amount sent in the request. Returned based on the terminal setup.
ssl_tip_amountTip Amount
Added or updated tip or gratuity amount. Returned based on the terminal setup.
ssl_serverServer ID
Server identifier sent in the request. Returned based on the terminal setup.
Shift information sent in the request. Returned based on the terminal setup.
[Error]Returned only if an error occurs. Refer to the Error Codes section for more information.
errorCodeError Code
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.
errorMessageError Message
Detailed explanation of the error. This field may be changed based on merchant configuration in the user interface.
errorNameError Name
Error name or reason for the error.



  • In these examples, 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.


    <ssl_first_name>Test First</ssl_first_name>
    <ssl_last_name>Test Last</ssl_last_name>
    <ssl_avs_address>test road</ssl_avs_address>
    <ssl_address2>suite 1</ssl_address2>
    <ssl_company>Test Inc</ssl_company>


    <ssl_txn_time>04/26/2022 10:22:38 PM</ssl_txn_time>