Knowledge Base / API
עברית

Ask AI

✦ AI answer

Thinking…

Sources

    Get Recurring Payment History

    Use this function to retrieve information about all charges recorded in the recurring payment history within a specific date range.

    When should you use this function?

    This function is very similar to Get recurring payment info. The main difference is that it retrieves information about all charges recorded in the recurring payment history within a specific date range.

    What does this function return?

    The response includes the charge amount, transaction and document numbers, and additional recurring payment details. This is an excellent solution for updating interfaces and CRM systems according to the business's needs.

    Required models:

    The Recurring Payment model and existing recurring payment models are available in the Cardcom interface.

    JSON function link:

    Request method: GET

    Get recurring payment history

    https://secure.cardcom.solutions/api/v11/RecuringPayments/GetRecurringPaymentHistory

    Parameters to send to the Get recurring payment history function

    Legend:

    Red parameter – required

    Bold parameter – recommended

    Parameter that is neither red nor bold – optional

    No.ParameterExample valuesDescription
    1apiUserName"test2025"API username
    2apiPassword"test5000$"API user password
    3RowId"13463"Recurring payment charge row in the payment history
    4AccountId13463Internal customer card number
    5FromDateDDMMYYYY – "01012025"Start date
    6ToDateDDMMYYYY – "17042025"End date

    Get recurring payment history response

    No.ParameterExample valueDescription
    1ResponseCode0Response code. If the value is 0, the function was executed successfully. Any other value indicates that the operation was unsuccessful.
    2Description"OK"Response description. “OK” indicates success.

    RecurringPaymentHistory values

    An array of objects.

    No.ParameterExample valueDescription
    1RowId"13463"Recurring payment charge row in the payment history
    2RecurringId37930Recurring payment number associated with the customer card
    3TerminalNumber1000Terminal used to charge the recurring payment
    4AccountID13744Customer card number
    5DocumentDescription"item (Payment 1 of 99999) for January"Item description on the document
    6LastDate"2025-02-03T12:18:00"Last charge date
    7OriginalNextDate"2025-01-27T00:00:00"Original charge date
    8FinalDebitCoinID1Currency number: 1 – ILS; 2 – USD. For additional currency codes, see the currency code list.
    9SumToBill100.00Amount to charge through the recurring payment
    10SumToBillNoVat84.75Amount to charge through the recurring payment before VAT
    11DepartmentID1Department number associated with the recurring payment
    12IsDocumentCreateboolean – true / falseWhether a document was configured to be issued for the recurring payment charge
    13AgentID1User number who created the recurring payment
    14PaymentNum1Payment number
    15IsReNewOrderboolean – true / falseWhether the recurring payment is new
    16ProductID(string)Internal product code
    17TranzactionId202406493Cardcom internal transaction number
    18ResposeCode0Response code. A value of 0 indicates successful execution.
    19ProcessID4467Process number
    20DocumentType1, 2, 3, 4, 50, 100, 101, 102, 200, 210, 300, 301, 302, 303, 304, 305, 330, 400, 405, 406, 410Document type to issue. 1 – tax invoice/receipt; 2 – credit invoice/refund; 3 – non-profit receipt / receipt without VAT; 4 – non-profit credit receipt; 50 – quotation; 100 – order without payment; 101 – order confirmation; 102 – order credit; 200 – delivery note; 210 – return note; 300 – transaction account; 301 – payment demand; 302 – payment demand cancellation; 303 – receipt account; 304 – receipt account credit; 305 – tax invoice; 330 – credit invoice; 400 – receipt for an invoice; 405 – donation receipt; 406 – donation receipt credit; 410 – customer refund
    21DocumentNumber18039Document number
    22Quantity1Item quantity
    23UnitPrice100Item price
    24UnitPriceNoVAT84.75Item price excluding VAT
    25IsIncludesVATboolean – true / falseWhether the price includes VAT
    26VAT15.25VAT amount
    27BillingAttempts1Number of charge attempts for this charge
    28CreateDate"2025-02-27T00:00:00"Creation date
    29ActualBillingType0 – Bank; 1 – Credit CardRecurring payment type: credit card or bank
    30NumOfCreditPaymentsINTIf the recurring payment was configured as a single charge paid in installments, this parameter contains the number of installments.
    31Status"SUCCESSFUL" / "DEBTAUTOBILLING"Normally, no other response is returned. If the charge could not be processed, an empty history array is returned.

    System messages in the URLResp field – server response

    The URLResp field displays the result of an attempt to send a Webhook notification:

    • OK : empty – The notification was sent successfully, but the receiving server returned an empty response. If the server returns content, it will be displayed in this field.
    • ERROR : No url in config – The notification was not sent because no URL was configured in the Webhook notification settings.
    • ERROR : Max Retry – The system reached the maximum number of notification attempts and will not try again. An email is also sent to the business at the address configured in the company notification settings.

    Note: If a notification attempt was made, the URLResp field will not be empty.

    Example request and response

    GET request for recurring payment history

    {
      "apiUserName": "test2025",
      "apiPassword": "test5000$",
      "RowId": "341344",
      "AccountId": "13463",
      "FromDate": "01012025",
      "ToDate": "17042025"
    }

    Response

    {
      "ResponseCode": 0,
      "Description": "ok",
      "RecurringPaymentHistory": [
        {
          "RowID": 341344,
          "RecurringId": 37551,
          "TerminalNumber": 1001,
          "AccountID": 13463,
          "DocumentDescription": "item (Payment 2 of 99999) for February",
          "LastDate": "2025-02-27T12:18:00",
          "OriginalNextDate": "2025-02-27T00:00:00",
          "FinalDebitCoinID": 1,
          "SumToBill": 100.00,
          "SumToBillNoVat": 100.00,
          "DepartmentID": 0,
          "IsDocumentCreate": true,
          "AgentID": 0,
          "PaymentNum": 2,
          "IsReNewOrder": false,
          "ProductID": null,
          "TranzactionId": 202406493,
          "ResposeCode": 0,
          "ProcessID": 4467,
          "DocumentType": 3,
          "DocumentNumber": 18039,
          "Quantity": 1.00,
          "UnitPrice": 100.00,
          "UnitPriceNoVAT": 100.00,
          "IsIncludesVAT": false,
          "VAT": 0.0000,
          "BillingAttempts": 1,
          "CreateDate": "2025-02-27T00:00:00",
          "ActualBillingType": 1,
          "NumOfCreditPayments": null,
          "Status": "SUCCESSFUL"
        }
      ]
    }

    Was this article helpful?