Update Recurring - ecsupdaterecurring

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

The ecsupdaterecurring transaction updates an existing ACH ECheck recurring payment in the Converge recurring batch.

In this section:

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

Request

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. Important: 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 Value:`ecsupdaterecurring`	Required	20	alphanumeric
`ssl_recurring_id`	Recurring ID Unique identifier of the recurring payment record to be updated.	Required	50	alphanumeric
`ssl_agree`	Agreement Indicator Valid values: `0` - Does not agree `1` - Agrees	Required	1	numeric
`ssl_amount`	Transaction Amount The recurring payment amount. Format: Number with 2 decimal places	Optional	11	numeric
`ssl_aba_number`	Routing or Transit Number Unique code assigned to the bank to be able to send and receive funds from other financial institutions.	Optional	9	alphanumeric
`ssl_bank_account_number`	Bank Account Number Unique identifier of the checking account.	Optional	16	numeric
`ssl_bank_account_type`	Bank Account Type Indicates the type of checking account. Valid values: `0` - Personal `1` - Business	Optional	1	numeric
`ssl_first_name`	First Name First name on the cardholder’s / customer’s account or billing address. Important: Required if `ssl_bank_account_type` = 0.	Conditional	20	alphanumeric
`ssl_last_name`	Last Name Last name on the cardholder’s / customer’s account or billing address. Important: Required if `ssl_bank_account_type` = 0.	Conditional	30	alphanumeric
`ssl_company`	Company Name Company name on the cardholder’s / customer’s account or billing address. Important: Required if `ssl_bank_account_type` = 1.	Conditional	50	alphanumeric
`ssl_next_payment_date`	Next Payment Date The date of the next scheduled payment for the recurring record. Format: MM/DD/YYYY	Optional	10	alphanumeric
`ssl_billing_cycle`	Billing Cycle Valid values:`DAILY`, `WEEKLY`, `BIWEEKLY`, `SEMIMONTHLY`, `MONTHLY`, `BIMONTHLY`, `QUARTERLY`, `SEMESTER`, `SEMIANNUALLY`, `ANNUALLY`, `SUSPENDED`	Optional	12	alphanumeric
`ssl_bill_on_half`	Half of the Month or Semimonthly Indicator Indicates when to process recurring payment transactions if `ssl_billing_cycle` = SEMIMONTHLY. Valid values: `1` - 1st and 15th of the month `2` - 15th and last day of the month	Conditional	1	numeric
`ssl_end_of_month`	End of Month Indicator Indicates whether to process the recurring transaction on the last day of the month. Valid values: `Y` - Yes `N` - No Select Y to process the recurring transaction: If `ssl_billing_cycle` = MONTHLY, BIMONTHLY, QUARTERLY, SEMESTER or SEMIANNUALLY and the Start Payment Date is April 30, June 30, September 30, November 30, February 28 (non-Leap year) or February 29 (Leap year). If `ssl_billing_cycle` = ANNUALLY and the Start Payment Date is February 28 (non-Leap year) or February 29 (Leap year).	Conditional	1	alphanumeric
`ssl_skip_payment`	Skip Payment Indicator Valid values: `Y` - Skip payment `N` - Do not skip payment (Default)	Optional	1	alphanumeric
`ssl_description`	Merchant-defined Transaction Description Short and custom text to describe the transaction.	Optional	255	alphanumeric

Response

Field name	Description
`ssl_result`	Transaction Outcome An `ssl_result` = 0 indicates an approved transaction. An `ssl_result` not equal to 0 indicates a declined and unauthorized transaction.
`ssl_result_message`	Transaction Result Message A result of SUCCESS indicates that the recurring record was added. A result of ERROR indicates that the recurring record was not added.
`ssl_recurring_id`	Recurring ID Unique identifier of the added recurring record. Important: Returned only if `ssl_result_message` = SUCCESS.
`ssl_amount`	Recurring Amount
`ssl_billing_cycle`	Billing Cycle
`ssl_next_payment_date`	Next Payment Due Date
`ssl_start_payment_date`	Payment 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_count`	Recurring Batch Count The current number of transactions sitting in the recurring batch after the recurring transaction has been updated.
`ssl_aba_number`	Routing or Transit Number
`ssl_bank_account_number`	Masked Bank Account Number
`ssl_bank_account_type`	Bank Account Type
`ssl_first_name`	First Name Returned based on merchant setup.
`ssl_last_name`	Last Name Returned based on merchant setup.
`ssl_company`	Company Name Returned based on merchant setup.
`ssl_description`	Merchant-defined Transaction Description Returned based on merchant setup.
[Error]	Returned only if an error occurs. Refer to the Error Codes section for more information.
`errorCode`	Error 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.
`errorMessage`	Error Message Detailed explanation of the error. This field may be changed based on merchant configuration in the user interface.
`errorName`	Error Name Error name or reason for the error.

Example

important

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 update a recurring transaction and set the billing payment to Suspended.

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>ecsupdaterecurring</ssl_transaction_type>
    <ssl_recurring_id>190115A15-E123C27A-CC10-44E6-811E-185097739FD2</ssl_recurring_id>
    <ssl_billing_cycle>SUSPENDED</ssl_billing_cycle>
</txn>