Credit Accounts

Use the Accounts API endpoint to submit a payment for processing through the customer's primary payment profile.

📘
Early Access
Credit API endpoints are currently being finalised as part of ongoing product development. While we do not anticipate significant changes, some interfaces, behaviours, and documentation may be refined before general availability.

The Log Payment endpoint enables you to record a payment directly against a customer's line of credit account in the system. Use this endpoint to log payments that have already been collected through an external channel, such as a cash payment made in person or a check received by mail. Unlike Create Autopay, this endpoint is not tied to a specific linked bank account. To schedule an automated bank transfer instead, use the Create Autopay endpoint.

📘
More Information
For more information about the Accounts endpoints, see: Credit Accounts.

Prerequisites

To integrate calls to the Log Payment endpoint, you need:

The account_id of the line of credit account to log the payment against. This is the Thredd Account ID, returned when a credit application is approved.
The payment amount. The description and apply date are optional.

Example Request

Log a payment by making a POST request to the Log Payment endpoint.

POST {{baseUrl}}/api/v1/credit/accounts/{account_id}/payment/log

Path Parameters

Parameter	Description
`account_id`	string. Required. The unique identifier of the line of credit account.

Example Payload

{
  "amount": 0,
  "description": "string",
  "apply_date": "YYYY-MM-DD"
}

{
  "amount": 250.00,
  "description": "Cash payment received in branch",
  "apply_date": "2025-02-15"
}

Request Fields

Attribute	Description
`amount`	number or string. Required. The payment amount, as a positive number with up to two decimal places.
`description`	string. Optional. A description of the payment. Maximum length is 255 characters. Defaults to `"payment"` if omitted.
`apply_date`	string. Optional. The date on which the payment applies to the account, in `YYYY-MM-DD` format.

Example Response

A successful request returns a 200 HTTP status code confirming the payment has been logged.

📘
Note
If the request contains invalid data or is incomplete, the system returns a 422 HTTP error and details of the validation failure.

{
  "is_success": true
}

{
  "detail": "Account mapping not found."
}

{
  "detail": [
    {
      "loc": ["body", "amount"],
      "msg": "Field required",
      "type": "missing"
    }
  ]
}

Response Fields

Attribute	Description
`is_success`	boolean. Indicates whether the operation was successful.

Error Messages

If there is a problem with the request, the response returns one of the following errors:

404 — The account_id provided does not match an existing account.
422 — A required field or its value is missing or invalid. The response includes details of the validation failure.

Accounts Endpoints

Accounts Endpoints. The Accounts endpoints enable clients to log payments and schedule automatic payments against a line of credit account. Use these endpoints to record a payment made outside the system, or to set up a scheduled automatic payment (autopay) using a linked bank account.

Endpoint	Documentation	Method
Log Payment	Log Payment	POST
Create Autopay	Create Autopay	POST

For more information about the Accounts endpoints, see Credit Accounts. The Accounts endpoints can also be viewed in the API Explorer.

Updated 4 days ago

Did this page help you?