Skip to main content
POST
/
v1
/
ach
Create an ACH
curl --request POST \
  --url https://api.sandbox.lead.bank/v1/ach \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'Idempotency-Key: <idempotency-key>' \
  --data '
{
  "amount": 5000,
  "currency_code": "USD",
  "transaction_type": "credit",
  "account_number_id": "account_number_xyz123",
  "counterparty": {
    "name": "Lara Smikle",
    "account_number": "1032345678",
    "routing_number": "021000021",
    "account_type": "checking"
  },
  "delivery_type": "same_business_day",
  "sec_code": "WEB",
  "statement_descriptor": "P2P Credit",
  "individual_id": "<string>",
  "descriptive_date": "220627",
  "additional_information": "<string>",
  "metadata": {}
}
'
{
  "id": "ach_xyz001",
  "created_at": "2022-06-27T11:22:33Z",
  "updated_at": "2022-06-27T11:22:33Z",
  "status": "submitted",
  "amount": 5000,
  "account_id": "account_xyz123",
  "account_number_id": "account_number_xyz123",
  "direction": "outgoing",
  "delivery_type": "same_business_day",
  "transaction_type": "credit",
  "sec_code": "WEB",
  "currency_code": "USD",
  "statement_descriptor": "P2P Credit",
  "record_details": {
    "company_name": "Acme Inc.",
    "company_id": "1234",
    "company_discretionary_data": "Acme Inc.",
    "effective_date": "2022-06-27",
    "settlement_date": "2022-06-27",
    "individual_id": "<string>",
    "receiver_name": "<string>",
    "descriptive_date": "220627",
    "additional_information": "<string>",
    "trace_number": "123456789012345"
  },
  "counterparty": {
    "name": "Lara Smikle",
    "account_number": "1032345678",
    "routing_number": "021000021",
    "account_type": "checking"
  },
  "returns": [
    {
      "type": "return",
      "status": "submitted",
      "return_code": "R02",
      "return_reason": "<string>",
      "trace_number": "123456789012345",
      "additional_information": "<string>"
    }
  ],
  "reversal": {
    "reversal_reason": "duplicate",
    "linked_ach_id": "<string>"
  },
  "rejection": {
    "reason": "account_number_status",
    "details": "Account number account_123 is inactive."
  },
  "correction": {
    "account_number": "1032345678",
    "routing_number": "021000021",
    "account_type": "checking"
  },
  "metadata": {}
}

Authorizations

​
Authorization
string
header
required

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

Headers

​
Idempotency-Key
string
required

Idempotency key

Maximum string length: 255

Body

application/json
​
amount
integer<int64>
required

The amount of the transaction in cents.

Required range: 0 <= x <= 9900000000
Example:

5000

​
currency_code
enum<string>
required

A three-letter currency code as defined in ISO 4217.

Available options:
USD
Example:

"USD"

​
transaction_type
enum<string>
required

ACH transaction type:

  • credit: An ACH credit pushes funds from your account to the counterparty.
  • debit: An ACH debit will pull funds into your account from the counterparty.
Available options:
credit,
debit
Example:

"credit"

​
account_number_id
string
required

The ID of the Lead Bank Account Number object.

Pattern: ^account_number_\w+$
Example:

"account_number_xyz123"

​
counterparty
object
required

The details of the counterparty you are sending/receiving money from.

​
delivery_type
enum<string>
required

How fast you want the counterparty to receive the ACH.

  • same_business_day: if the ACH request is submitted before the cutoff window with the same business day option, funds will settle on the same day. 
  • next_business_day: standard ACH processing, for funds to settle on the next business day.
Available options:
same_business_day,
next_business_day
Example:

"same_business_day"

​
sec_code
enum<string>
required

The Standard Entry Class, SEC, to code the outgoing ACH. Lead currently supports:

  • CCD: Corporate payment
  • PPD: Written authorization to initiate payment
  • TEL: Telephone initiated payment
  • WEB: Web initiated payment
  • CIE: Customer initiated entry
Available options:
CCD,
PPD,
TEL,
WEB,
CIE
Example:

"WEB"

​
statement_descriptor
string
required

The description you would like to appear on your customers’ statement. Maximum number of characters is 10.

Required string length: 1 - 10
Pattern: ^(?!0+$)(?! +$)[\x20-\x7E]*$
Example:

"P2P Credit"

​
individual_id
string

The name of the individual you are sending funds to. Required for P2P payments.

Maximum string length: 15
Pattern: ^[\x20-\x7E]*$
​
descriptive_date
string

The date you would like displayed to the counterparty. Receiving financial institutions may utilize this field to display on the statement.

Maximum string length: 6
Pattern: ^[\x20-\x7E]*$
Example:

"220627"

​
additional_information
string

Additional information for the ACH recipient. Not all banks will share this message with their end customer.

Maximum string length: 80
Pattern: ^[\x20-\x7E]*$
​
metadata
object

A set of key-value pairs that can be used to store additional information related to this object.

Response

ACH object created.

​
id
string

id of the ACH object

Pattern: ^ach_\w+$
Example:

"ach_xyz001"

​
created_at
string<date-time>

The ISO-8601 timestamp at which the ACH object was created.

Example:

"2022-06-27T11:22:33Z"

​
updated_at
string<date-time>

The ISO-8601 timestamp at which the ACH object was last updated.

Example:

"2022-06-27T11:22:33Z"

​
status
enum<string>

The current status of the ACH object.

Available options:
scheduled,
processing,
submitted,
posted,
canceled,
under_review,
approved,
rejected,
pending_return,
returned
Example:

"submitted"

​
amount
integer<int64>

The amount of the transaction in cents.

Required range: 0 <= x <= 9900000000
Example:

5000

​
account_id
string

The ID of the Account object.

Pattern: ^account_\w+$
Example:

"account_xyz123"

​
account_number_id
string

The ID of the Lead Bank Account Number object.

Pattern: ^account_number_\w+$
Example:

"account_number_xyz123"

​
direction
enum<string>

Who is initiating the transaction.

outgoing: You are sending a transaction to a counterparty. incoming: You are receiving a transaction from a counterparty.

Available options:
outgoing,
incoming
Example:

"outgoing"

​
delivery_type
enum<string>

How fast you want the counterparty to receive the ACH.

  • same_business_day: if the ACH request is submitted before the cutoff window with the same business day option, funds will settle on the same day. 
  • next_business_day: standard ACH processing, for funds to settle on the next business day.
Available options:
same_business_day,
next_business_day
Example:

"same_business_day"

​
transaction_type
enum<string>

ACH transaction type.

Available options:
credit,
debit
Example:

"credit"

​
sec_code
enum<string>

Standard Entry Class (SEC) code to use for this ACH object.

Lead currently only supports CCD, PPD, WEB, and TEL for outgoing ACHes.

Available options:
PPD,
CCD,
ARC,
BOC,
CIE,
CTX,
IAT,
POP,
POS,
RCK,
TEL,
WEB,
ADV,
DNE,
ENR,
MTE,
SHR,
TRC,
TRX,
COR
Example:

"WEB"

​
currency_code
enum<string>

A three-letter currency code as defined in ISO 4217.

Available options:
USD
Example:

"USD"

​
statement_descriptor
string

The description you would like to appear on your customers’ statement. Maximum number of characters is 10.

Required string length: 1 - 10
Pattern: ^(?!0+$)(?! +$)[\x20-\x7E]*$
Example:

"P2P Credit"

​
record_details
object
​
counterparty
object

The details of the counterparty you are sending/receiving money from.

​
returns
object[]

Associated returns.

​
reversal
object

A reversal associated with this object.

​
rejection
object
​
correction
object

The corrected counterparty details.

​
metadata
object

A set of key-value pairs that can be used to store additional information related to this object.