Update Installment - ccupdateinstall

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

The ccupdateinstall transaction updates a credit card installment record in Converge.

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.
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:  ccupdateinstall
ssl_installment_idInstallment ID
Unique identifier of the installment record to be updated.
[Card data]
ssl_card_numberCard number
Card number as it appears on the credit card.
Required when adding an installment record using a card number.
ssl_exp_dateCard’s Expiry Date
Date when the card becomes invalid.
Format: MMYY
Required if ssl_card_number is not null.
[Payment Schedule]
ssl_amountTransaction Amount
The Installment amount that includes the Net and Sales Tax amounts.
Format: Number with 2 decimal places
ssl_total_installmentsNumber of Payments
Total number of installment payments for a transaction.
ssl_next_payment_dateNext Payment Date
The date of the next scheduled payment for the installment record.
Format: MM/DD/YYYY
ssl_billing_cycleBilling Cycle
ssl_bill_on_halfHalf of the Month or Semimonthly Indicator
Indicates when to process installment payment transactions if ssl_billing_cycle = SEMIMONTHLY.
Valid values:
  • 1 - 1st and 15th of the month
  • 2 - 15th and last day of the month
ssl_end_of_monthEnd of Month Indicator
Indicates whether to process the installment transaction on the last day of the month.
Valid values:
  • Y - Yes
  • N - No

Select Y to process the installment 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).
ssl_skip_paymentSkip Payment Indicator
Valid values:
  • Y - Skip payment
  • N - Do not skip payment (Default)
[Optional Fields]
ssl_avs_addressAddress Line 1
Commonly the house number and street name on the cardholder’s / customer’s account or billing address.
Address Verification Service (AVS) data compared with the address on the card issuer’s file.
ssl_avs_zipPostal or ZIP Code
ZIP code on the cardholder’s account or billing address.
Address Verification Service (AVS) data compared with the postal or ZIP code on the card issuer’s file.
ssl_first_nameFirst Name
First name on the cardholder’s / customer’s account or billing address.
ssl_last_nameLast Name
Last name on the cardholder’s / customer’s account or billing address.
[Purchasing Cards]Use only on terminals that are set up with the Purchasing Card 2 credit card payment option.
ssl_customer_codeCustomer Code or Purchase Order Number
Customer ID or PO number specified in the billing statement of the cardholder.
ssl_salestaxSales Tax
Tax amount to add to the purchase or sales amount. For a tax exempt transaction, enter 0.00.
Format: Amount with 2 decimal places.
[Invoice Number]Returned only if Invoice Number parameters are sent in the request.
ssl_invoice_numberInvoice Number
The invoice number or ticket number sent in the original request.
[Doing Business As]Use only on terminals that are set up with the DBA Name terminal option.
ssl_dynamic_dbaDoing Business As Name
Merchant-defined descriptors that replace the merchant’s business name on credit card statements.
Format: Prefix*Descriptor
Length: Prefix = 3, 7, or 12, Asterisk = 1, Descriptor = 21 - (Prefix + Asterisk)


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 installment record was added.
A result of ERROR indicates that the installment record was not added.
ssl_card_numberMasked 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).
ssl_installment_idInstallment ID
Unique identifier of the added installment record.
Important: Returned only if ssl_result_message = SUCCESS.
ssl_amountInstallment Amount
ssl_total_installmentsTotal Number of Payments
ssl_number_of_paymentsNumber of Payments
The current number of payments run on the system. Returned by Converge.
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_countRecurring Batch Count
The current number of transactions sitting in the recurring batch after the installment transaction has been updated.
[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.




    <ssl_avs_address>first street</ssl_avs_address>