List payments

Authorizations

Authorization

string

header

required

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

Query Parameters

business_entity_id

string

required

payroll_id

string

remittance_account_id

string

status

enum<string>

Filter by payment status. Supports multiple comma-separated values.

Available options:

canceled,

failed,

overdue,

paid,

pending,

processing

destination

enum<string>

Filter by payment destination. Supports multiple comma-separated values.

Available options:

bill_pay,

cra,

employee,

internal,

no_op,

payroll_float,

rq

method

enum<string>

Filter by payment method. Supports multiple comma-separated values.

Available options:

direct_deposit,

manual,

pad,

wire

is_held

boolean

Filter by hold status. true returns only held payments, false returns only non-held payments.

expected_at

object

Date filters support two formats: Exact Date Match: Provide a well-formatted date in YYYY-MM-DD format for an exact match. Example: expected_at=2024-01-01 Use an array-like syntax to specify a range with one or more comparison operators:

gt (greater than)
gte (greater than or equal to)
lte (less than or equal to)
lt (less than) Example: expected_at[gte]=2024-01-01&expected_at[lt]=2024-12-31

process_at

object

Date filters support two formats: Exact Date Match: Provide a well-formatted date in YYYY-MM-DD format for an exact match. Example: process_at=2024-01-01 Use an array-like syntax to specify a range with one or more comparison operators:

gt (greater than)
gte (greater than or equal to)
lte (less than or equal to)
lt (less than) Example: process_at[gte]=2024-01-01&process_at[lt]=2024-12-31

sort

enum<string>

Sort order is specified using the format sort=field[:direction][,field[:direction],...] where field is the name of the field to sort by and direction is the optional sort direction (asc or desc).

Available options:

amount,

destination,

expected_at,

process_at,

status

expand

enum<string>[]

Available options:

payroll,

remittance_account

Response

200 - application/json

object

string

read-only

The type of the object in Nmbr ("list").

data

object[]

Hide child attributes

data.id

string

read-only

The unique identifier of the object in Nmbr.

data.object

string

read-only

The type of the object in Nmbr ("payment").

data.data

Default · object

Default
With payroll expanded
With remittance_account expanded

Hide child attributes

data.data.payroll

object

Hide child attributes

data.data.payroll.id

string

read-only

The unique identifier of the object in Nmbr.

data.data.payroll.object

string

read-only

The type of the object in Nmbr ("payroll").

data.data.remittance_account

any

data.data.destination

enum<string>

Where the payment is destined. payroll_float is the funding debit from the employer's bank account. employee is a credit to an employee or contractor. cra and rq are remittances to the Canada Revenue Agency (CRA) and Revenu Québec (RQ), respectively.

Where the payment is destined. For example, employee for payments to employees, cra for remittances to CRA, payroll_float for business funding.

Available options:

bill_pay,

cra,

employee,

internal,

no_op,

payroll_float,

rq

data.data.method

enum<string>

How the payment will be processed. pad (Pre-Authorized Debit) is used for employer funding. direct_deposit is used for employee credits. manual indicates the payment is handled outside of Nmbr.

How the payment will be processed. For example, direct_deposit or pad.

Available options:

direct_deposit,

manual,

pad,

wire

data.data.amount

number<decimal>

The dollar amount of the payment.

data.data.status

enum<string>

The current processing status of the payment. Payments begin as pending, move to processing when submitted to the banking network, and settle as paid or failed. Held payments that pass their processing date become overdue.

Available options:

canceled,

failed,

overdue,

paid,

pending,

processing

data.data.process_at

string<date> | null

The date on which Nmbr will submit the payment to the banking network for processing.

data.data.expected_at

string<date>

The date on which the payment is expected to arrive at its destination.

data.data.is_impacted_by_weekend_or_holiday

boolean

Whether the payment dates have been adjusted due to a weekend or bank holiday.

data.data.is_held

boolean

Whether the payment is currently held. A held payment will not be submitted for processing until it is released.

data.data.held_at

string<dateTime> | null

read-only

The timestamp when the payment was placed on hold. null if the payment is not held.

data.data.created_at

string<dateTime>

read-only

The date and time the object was created in Nmbr.

data.data.updated_at

string<dateTime>

read-only

The date and time the object was last updated in Nmbr.