Signature - ccsignature

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

The ccsignature transaction adds signature data to a previously approved Credit Card Sale (ccsale), Auth Only (ccauthonly), or Force (ccforce) transaction.


  • Signature is not allowed for the eCommerce  market segment.
  • Signature can only be added to a transaction that has no signature.

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:  ccsignature
ssl_txn_idTransaction ID
Unique identifier of the previously approved Sale (ccsale), Auth Only (ccauthonly), or Force (ccforce) transaction.
ssl_signature_imageSignature Image
Digital version of the cardholder’s signature.
RequiredBLOBBase64 Encoded
ssl_image_typeSignature Image Format
File format of the signature image.
Valid values:  GIF, TIF, JPG, PNG


Field nameDescription
ssl_resultSignature Request Result Code
ssl_result = 0 indicates that the signature was uploaded and added.
An ssl_result = 1 indicates that the signature was not uploaded and added.
ssl_result_messageSignature Upload Result Message
A result of SUCCESS indicates that the signature image was uploaded or added.
A result of ERROR indicates that the signature image was not uploaded or added.
ssl_user_idConverge User ID
[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 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.

Approved Sale Transaction


    <ssl_track_data>%B0000000000000000^NOVA CORPORATION^2212101543213961456?;0000000000000000=2212101543213961456?</ssl_track_data>


    <ssl_cvv2_response />
    <ssl_departure_date />
    <ssl_invoice_number />
    <ssl_completion_date />
    <ssl_txn_time>01/28/2022 10:21:31 PM</ssl_txn_time>
    <ssl_avs_response />

Add Signature to Approved Sale Transaction


    <ssl_description>Keyed Sale API</ssl_description>