Skip to main content
POST
Create an ACH debit in request

Authorizations

Api-Access-Key
string
header
required

An API key associated with a security role

Headers

Api-Signature
string
required

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

Construction example:

Pattern: ^[0-9A-Fa-f]{128,160}$
Api-Timestamp
integer<int64>
required

Current timestamp, represented as unix epoch seconds

Body

application/json
amount
string
required

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

Pattern: ^(0|[1-9][0-9]*)(\.[0-9]{1,2})?$
Example:

"250.00"

assetType
enum<string>
default:USD
required

The asset to deposit. Only USD is accepted.

Available options:
USD
Example:

"USD"

destination
ACHDebitInDestination · object
required

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

idempotentId
string
required

A client-provided unique ID for idempotent requests

Required string length: 1 - 128
Example:

"12838927347"

secCode
enum<string>
required

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

Available options:
WEB,
CCD
source
PlaidProcessorTokenSource · object
required

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

remittanceInformation
string

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

Required string length: 1 - 80
Pattern: ^[\x20-\x7E]*$
sameDayAch
boolean
default: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.

statementDescriptor
string

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

Required string length: 1 - 10
Pattern: ^[\x20-\x7E]*$

Response

Successfully initiated an ACH debit in

data
CreateACHDebitInDetails · object
required
Example: