Submit Recurring Payment - ecsrecurringsale

This section describes the message parameters for Electronic Check Submit Recurring Payment transaction processing, which you can submit using the XML API integration method. Refer to the Integration Methods section for more information.

The ecsrecurringsale transaction allows you to run an ACH ECheck recurring payment outside of its billing cycle and increase the total number of payments.

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.
Important: The ssl_user_id sending the transaction request must be associated with the terminal that will process the request.
ssl_transaction_typeTransaction Type
Value:  ecsrecurringsale
ssl_recurring_idRecurring ID
Unique identifier of the recurring payment record to be submitted for payment.


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
A result of SUCCESS indicates that the recurring record was submitted for payment.
A result of ERROR indicates that the recurring record was not submitted for payment.
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_approval_codeTransaction Approval Code
Unique code returned that indicates the approval status of the transaction.
ssl_recurring_idRecurring ID
Unique identifier of the recurring record sent for payment.
ssl_amountAuthorized/Approved Transaction Amount
Returned based on merchant setup.
ssl_billing_cycleBilling Cycle
ssl_next_payment_dateNext Payment Due Date
ssl_start_payment_datePayment Start Date
The date when the first payment started. If recently added, the start date is the same as the next payment due date.
Format: MM/DD/YYYY
ssl_recurring_batch_countThe current number of transactions sitting in the recurring batch after the recurring transaction has been sent for payment.
ssl_aba_numberRouting or Transit Number
ssl_bank_account_numberMasked Bank Account Number
ssl_bank_account_typeBank Account Type
ssl_first_nameFirst Name
Returned based on merchant setup.
ssl_last_nameLast Name
Returned based on merchant setup.
ssl_companyCompany Name
Returned based on merchant setup.
ssl_descriptionMerchant-defined Transaction Description
Returned based on merchant 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 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.

This example demonstrates the minimum required data to send a recurring sale outside of the billing cycle.