Managing originators

Use these endpoints to create originators, update them, and change their status:

Endpoint	Description
`POST /v2/originators`	Create an originator. Requires `core_balance_id`, `entity_id`, `company_name`, and `ach`. Requires an `Idempotency-Key` header. Starts in `pending`.
`GET /v2/originators`	List originators. The `core_balance_id` filter is required.
`GET /v2/originators/{originator_id}`	Retrieve an originator.
`PATCH /v2/originators/{originator_id}`	Update `company_name`, the `ach` block, or `metadata`.
`POST /v2/originators/{originator_id}/activate`	Return an `inactive` originator to `active`.
`POST /v2/originators/{originator_id}/deactivate`	Move an `active` originator to `inactive`.
`POST /v2/originators/{originator_id}/cancel`	Permanently cancel an originator. You can’t undo this.

The activate, deactivate, and cancel endpoints take no request body but require an Idempotency-Key. Calling one on an originator already in the target status returns the current object. See Idempotency. An originator can originate ACH only while it is active. A new originator waits in pending until Lead reviews it. See Originator Statuses for the full lifecycle.

Send ACH under an originator

After it is active, set ach_controls.originator_id on each account number you want to send under it. See The Account Number Object.

Products

Banking Infrastructure

Customers & Accounts

Balances and Transactions

Lending & Receivables

Payment Rails

Send ACH under an originator

​Send ACH under an originator

​Related

Send ACH under an originator

Related