API reference
  1. Anchorage Digital API Reference
  2. Transactions

Create an ACH debit in request

post
https://api.anchorage-staging.com/v2/transactions/ach-debit-in

Permissions required: Initiate ACH Debit In

Idempotency

A request that repeats an idempotentId returns the existing operation with a 201. Anchorage Digital does not compare the repeated request body with the first one.

Permissions

A 403 with the message "Forbidden" means the API key lacks the Initiate ACH Debit In permission for the destination wallet's vault. A 403 with the message "ACH Debit In is not enabled for this organization" means your organization is not enabled for ACH Debit In.

Result

The result of the debit arrives by ach-debit-in webhooks.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
required
^(0|[1-9][0-9]*)(\.[0-9]{1,2})?$

The amount to debit, without units, with up to two decimal places.

string
enum
required
Defaults to USD

The asset to deposit. Only USD is accepted.

Allowed:
destination
required

The wallet that receives the funds, with an optional virtual account under it.

string
required
length between 1 and 128

A client-provided unique ID for idempotent requests

string
length between 1 and 80
^[\x20-\x7E]*$

Free text carried on the entry's addenda record. Printable ASCII only.

boolean
Defaults to false

Request same-day ACH processing. Best effort: an entry submitted after the last same-day window goes out in the next available window. Standard processing when omitted.

string
enum
required

The NACHA Standard Entry Class code for the source account. WEB for a consumer account, CCD for a business account.

Allowed:
source
required

The bank account to debit. Use the type field to choose the source kind.

string
length between 1 and 10
^[\x20-\x7E]*$

Text shown on the end user's bank statement (the NACHA Company Entry Description). Printable ASCII only.

Headers
string
required
^[0-9A-Fa-f]{128,160}$

A hex-encoded Ed25519 signature of timestamp_epoch_seconds + uppercase(http_method) + request_path + request_body.

Construction example:

toHex(
  ed25519Sign(
    signing_key,
    '{}{}{}{}'.format(timestamp_epoch_seconds, toUpper(httpMethod), httpRequestPath, httpBody)
  )
)
int64
required

Current timestamp, represented as unix epoch seconds

Responses

Updated 8 days ago

Did this page help you?
Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 8 days ago

Did this page help you?