Skip to main content
POST
Make a payment

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

Idempotency-Key
string

An idempotency key is an arbitrary unique value generated by client to detect subsequent retries of the same request. It is recommended that a UUID or a similar random identifier be used as an idempotency key. A different key must be used for each request, unless it is a retry.

Example:

"7d943c51-e4ff-4e57-9558-08cab6b963c7"

Body

application/json

Payment to make

Request to make a one-time payment against a lending account (e.g. a card paydown). Exactly one of person_id or business_id must be provided to identify the customer initiating the payment; exactly one of payment_configs.ach or payment_configs.internal_transfer must be provided to identify the funding source.

amount
integer<int64>
required

Amount to pay, in cents. Paid in full as requested, even if it exceeds the account's current balance -- an intentional overpayment is honored, not truncated to the balance.

Required range: x >= 1
Example:

5000

lending_account_id
string<uuid>
required

The lending account (card/account) to pay down

Example:

"7d943c51-e4ff-4e57-9558-08cab6b963c7"

payment_configs
object
required

Payment method-specific configurations

business_id
string<uuid>

The business ID initiating this payment. Mutually exclusive with person_id -- exactly one must be provided.

Example:

"b2c3d4e5-f6a7-8901-bcde-f12345678901"

description
string

Optional description for the payment. Defaults to "Payment".

Example:

"Card paydown"

effective_date
string<date>

Date the payment should be made. Defaults to today. If today or in the past, the payment is executed immediately and the response reflects its final status; if in the future, the payment is scheduled and executes on that date.

Example:

"2024-01-25"

person_id
string<uuid>

The person ID initiating this payment. Mutually exclusive with business_id -- exactly one must be provided.

Example:

"a1b2c3d4-e5f6-7890-abcd-ef1234567890"

tenant
string

The id of the tenant containing the resource.

Example:

"abcdef_ghijkl"

Response

Payment created (and, if effective immediately, executed)

A one-time payment made against a lending account.

creation_time
string<date-time>
required

Timestamp when the payment was created

Example:

"2024-01-15T10:30:00Z"

description
string
required

Description for the payment

Example:

"Payment"

effective_date
string<date>
required

Date the payment was (or will be) made

Example:

"2024-01-25"

id
string<uuid>
required

Unique identifier for the payment

Example:

"2d0f7601-ecc6-48b4-b82f-5d64fa84628b"

last_updated_time
string<date-time>
required

Timestamp when the payment was last updated

Example:

"2024-01-15T10:30:00Z"

lending_account_id
string<uuid>
required

The lending account this payment was made against

Example:

"7d943c51-e4ff-4e57-9558-08cab6b963c7"

payment_configs
object
required

Payment method-specific configurations

status
enum<string>
required

Status of the autopay:

  • PENDING: Autopay is scheduled and waiting to be executed
  • EXECUTED: Autopay was successfully executed
  • SKIPPED: Autopay was skipped (e.g., no balance due)
  • FAILED: Autopay failed to execute
Available options:
PENDING,
EXECUTED,
SKIPPED,
FAILED
attempt_history
object

History of execution attempts for an autopay

current_amount
integer<int64>

The amount in cents associated with this payment. For PENDING payments this is the originally requested amount (payments are not capped at the current balance -- an intentional overpayment is honored). For EXECUTED payments this mirrors executed_amount.

Example:

5000

executed_amount
integer<int64>

The amount in cents actually paid, once executed.

Example:

5000

payment_attributes
object

Identifiers for the payment created by an autopay execution. Only one field will be populated depending on the payment method used.

tenant
Tenant · object