Submit Recurring Payment - ccrecurringsale

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

The ccrecurringsale transaction allows you to run a credit card recurring payment outside of its billing cycle. This will increase the payment number.

In this topic:


15 | numeric | required
Merchant ID
Elavon-assigned Converge account ID.
15 | alphanumeric | required
Converge User ID
The user ID with Hosted Payment API User status that can send transaction requests through the terminal.
64 | alphanumeric | required
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.
20 | alphanumeric | required
Transaction Type
Value: ccrecurringsale
50 | alphanumeric | required
Recurring ID
Unique identifier of the recurring payment record to be submitted for payment.
Use only on terminals that are set up with the Tokenization   terminal option.
1 | alphanumeric | optional
Add to Card Manager Indicator
Indicates whether to generate and store the token in Card Manager.
Valid values:
  • Y - Authorize transaction, generate and store token
  • N - Do not store token (Default)
20 | alphanumeric | conditional
First Name
First name on the cardholder's / customer's account or billing address.
Important:: Required if ssl_add_token is set to Y.
30 | alphanumeric | conditional
Last Name
Last name on the cardholder's / customer's account or billing address.
Important:: Required if ssl_add_token is set to Y.
1 | alphanumeric | optional
Generate Token Indicator
Indicates whether to generate a token when submitting the card data.
Valid values:
  • Y - Authorize transaction and generate token
  • N - Do not generate token (Default)
[Card On File]
1 | alphanumeric | optional
Merchant Initiated Unscheduled Transaction Indicator
Indicates the transaction was initiated by a merchant using a stored credential (token or stored card number) for a fixed or variable amount that does not occur on a scheduled or regularly occurring transaction date.
Valid values:
  • Y - Yes
  • N - No


Transaction Outcome
An ssl_result = 0 indicates an approved transaction.
An ssl_result not equal to 0 indicates a declined and unauthorized transaction.
Transaction Result Message
Refer to the Payment Card Response Codes section for an extensive list of possible returned messages.
Transaction ID
Unique identifier of the transaction.
Processing 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
Transaction Approval Code
Unique code returned by the credit card processor that indicates the approval status of the transaction.
Total Authorized/Approved Transaction Amount
Returned based on merchant setup.
Masked Card Number
Converge only returns the first 2 or last 4 digits of the regular PAN, or the last 4 digits of the actual card number if it is an association token (example, ApplePay).
Card's Expiry Date
Returned based on merchant setup.
Recurring ID
Unique identifier of the submitted recurring record.
Important: Returned only if ssl_result_message = SUCCESS.
Billing Cycle
Next Payment Due Date
Number of Payments
The current number of payments ran on the system. Returned by Converge.
Invoice Number
The invoice number or ticket number sent in the original request. Returned based on merchant setup.
Returned only if an error occurs. Refer to the Error Codes section for more information.
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.
Error Message
Detailed explanation of the error. This field may be changed based on merchant configuration in the user interface.
Error Name
Error name or reason for the error.


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