Skip to main content
An ACH debit, also called an originated debit, is when you pull USD from your source bank account to fund your Anchorage Digital account. Unlike an ACH credit, where the sender pushes funds from their bank, Anchorage Digital originates the debit on your behalf. For the shared model, see Deposit.
ACH is in development. Reach out to your relationship manager for beta access—see USD rails.
How you pull funds depends on whether you’re a client funding your own account or a platform serving end clients.

Clients

Clients pull funds with an ACH debit from the web dashboard only—there’s no API for client ACH pulls. Connect your source bank account using Plaid, then pull USD from it to fund your Anchorage Digital account.

Platforms (B2B2X)

Platforms serving their own end clients—see B2B2X accounts—need ACH debit access enabled before they can originate debits. Reach out to your relationship manager to request access. Once enabled, you create an ACH debit transaction through a dedicated endpoint, currently in development. The endpoint identifies the source bank account in one of two ways:
  • Plaid—a source bank account connected through Plaid
  • Account and routing number—the source bank account’s account number and routing number
Depending on your platform’s business model, a Reserve Loss Account and an Instant Funding account may be required. Your relationship manager can confirm what your setup needs.

Connect a source bank account with Plaid

To identify the source bank account with Plaid, Anchorage Digital acts as your Plaid processor. Your end client connects their bank in Plaid Link, your server exchanges the resulting tokens with Plaid, and you pass a processor token to Anchorage Digital. Your access token stays on your server—Anchorage Digital only ever receives the processor token.
This flow assumes your platform already has its own relationship with Plaid, including the API credentials your server uses to call Plaid. Anchorage Digital doesn’t provide Plaid access or credentials.
Select a step in the diagram, or use Previous and Next, to see what happens at each stage.

Track a debit with webhooks

Subscribe to the ach-debit-in webhook events to follow each debit: initiated, submitted, completed, failed, and returned. A failed event carries a reason that says why the debit didn’t go through. For the payload fields and the list of reasons, see ACH debit deposit lifecycle.

Returns from the source bank

After a debit settles, the account holder can still dispute it with their source bank, such as Chase or Bank of America, by filing an ACH return. If they file within the return deadline, the source bank honors the return. We deduct the returned amount from your Anchorage Digital account, and you receive an ach-debit-in.returned webhook for the deduction. The event carries the original transactionId, the returnOperationId of the return transaction, and the Nacha returnCode. See ACH debit returns.