ACH
ACH payments as unique as your business
Originate ACH credits and debits, track and initiate returns, and store frequently accessed details.
Unlimited account numbers
Stay organized and protect your account details with unique account numbers for every counterparty.Same-day by default
We default to same-day ACH processing and hit every window.Sensible return correlation
We pass unique trace identifiers with every transaction to identify returns effectively.Stable company identifiers
We expose company identifiers: no more complicated matching rules for statement descriptors.Transparent funds availability
Know precisely when your transfers are submitted to the Federal Reserve and when your funds will be available.Passthrough codes
We pass return codes and standard entry class codes directly: no new ontologies or mappings.Approval flows and limits
Approval flows let you review payments before sending. Programmable limits can prevent unwanted debits.Addenda
Non-financial messages like child-support payments or tax authority identifiers are visible alongside transfers in the API.Same-day ACH is
open
open
Next window in 06:18:53
A window of opportunity
Payroll needs to go out on time. We default to same-day ACH and hit every window. Our direct integration to the Federal Reserve means that you can submit transfers right down to the wire.
Same-day ACH is
open
open
Mon, 12:00pm
4:00
5:30
10:00
11:30
6:00
Tue, 12:00pm
4:00
5:30
10:00
11:30
6:00
Wed, 12:00pm
4:00
5:30
10:00
11:30
6:00
Thu, 12:00pm
4:00
5:30
10:00
11:30
6:00
Fri, 12:00pm
4:00
5:30
10:00
11:30
6:00
Increase
Future Day
Same Day
Full control of FedACH
Programmatically create ACH debits and credits. Pro tip: use unique account numbers for every counterparty to simplify reconciliation.
- We default to same-day ACH and hit every window.
- Returns are correlated automatically.
- Webhooks keep you up-to-date on the transfer lifecycle.
1
2
3
4
5
6
7
8
9
10
11
curl -X "POST" \
--url "${INCREASE_URL}/ach_transfers" \
-H "Authorization: Bearer ${INCREASE_API_KEY}" \
-d $'{
"account_id": "account_in71c4amph0vgo2qllky",
"account_number": "987654321",
"amount": 100,
"routing_number": "101050001",
"statement_descriptor": "New ACH transfer"
}'
Increase correlates ACH transfer returns automatically using a unique trace identifier for each request.
- No more manual reconciliation.
- Webhooks keep you up-to-date on the transfer lifecycle.
1
2
3
4
5
6
7
8
9
10
11
curl \
--url "${INCREASE_URL}/ach_transfers/ach_transfer_uoxatyh3lt5evrsdvo7q" \
-H "Authorization: Bearer ${INCREASE_API_KEY}"
External Accounts represent accounts at financial institutions other than Increase. You can use this API to store their details for reuse.
- Use in place of account & routing number in API calls.
- Verify external accounts to allow debits.
- Easily link external bank accounts from 5,000 different institutions.
1
2
3
4
5
6
7
8
9
10
11
curl -X "POST" \
--url "${INCREASE_URL}/external_accounts" \
-H "Authorization: Bearer ${INCREASE_API_KEY}" \
-d $'{
"routing_number": "101050001",
"account_number": "987654321",
"description": "Landlord"
}'
Intuitive and predictable funds flows
- You initiate a ACH transfer from the API via a call to /ach/transfers.The transfer is
pending_submission. - We send you an
ach_transfer.createdwebhook. The transfer is stillpending_submission. - The Federal Reserve ACH window opens.We default to same-day ACH and hit every window.
- We send you an
ach_transfer.updatedwebhook. The transfer is nowsubmitted.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
{
"account_id": "account_in71c4amph0vgo2qllky",
"account_number": "987654321",
"amount": 100,
"currency": "USD",
"created_at": "2020-01-31T23:59:59Z",
"id": "ach_transfer_uoxatyh3lt5evrsdvo7q",
"network": "ach",
"return": null,
"routing_number": "101050001",
"statement_descriptor": "Statement descriptor",
"status": "pending_submission",
"submission": null,
"transaction_id": null,
"company_descriptive_date": null,
"company_discretionary_data": null,
"company_entry_description": null,
"company_name": "National Phonograph Company",
"funding": "checking",
"individual_id": null,
"individual_name": "Ian Crease",
"standard_entry_class_code": "corporate_credit_or_debit",
"type": "ach_transfer"
}
{
"account_id": "account_in71c4amph0vgo2qllky",
"account_number": "987654321",
"amount": 100,
"currency": "USD",
"created_at": "2020-01-31T23:59:59Z",
"id": "ach_transfer_uoxatyh3lt5evrsdvo7q",
"network": "ach",
"return": null,
"routing_number": "101050001",
"statement_descriptor": "Statement descriptor",
"status": "pending_submission",
"submission": null,
"transaction_id": null,
"company_descriptive_date": null,
"company_discretionary_data": null,
"company_entry_description": null,
"company_name": "National Phonograph Company",
"funding": "checking",
"individual_id": null,
"individual_name": "Ian Crease",
"standard_entry_class_code": "corporate_credit_or_debit",
"type": "ach_transfer"
}
- During a FedACH window, we receive an transfer file.The inbound ACH transfer is represented as a Pending Transaction.
- The funds are in your
currentbalance.The transfer issubmitted. - Two days pass.The duration of the hold is always transparent.
- The hold elapses. The transfer is now represented as a Transaction.We also send you a
transaction.createdwebhook event. - The funds are available in your account.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
{
"account_id": "account_in71c4amph0vgo2qllky",
"amount": 100,
"currency": "USD",
"created_at": "2020-01-31T23:59:59Z",
"description": "Frederick S. Holmes",
"id": "pending_transaction_k1sfetcau2qbvjbzgju4",
"route_id": "card_route_jk5pd79u6ydmbf9qzu6i",
"route_type": "transfer_instruction",
"source": {
"category": "ach_transfer_instruction",
"ach_transfer_instruction": {
"amount": 100,
"transfer_id": "ach_transfer_uoxatyh3lt5evrsdvo7q"
}
},
"status": "pending",
"type": "pending_transaction"
}
{
"account_id": "account_in71c4amph0vgo2qllky",
"amount": 100,
"currency": "USD",
"created_at": "2020-01-31T23:59:59Z",
"description": "Frederick S. Holmes",
"id": "pending_transaction_k1sfetcau2qbvjbzgju4",
"route_id": "card_route_jk5pd79u6ydmbf9qzu6i",
"route_type": "transfer_instruction",
"source": {
"category": "ach_transfer_instruction",
"ach_transfer_instruction": {
"amount": 100,
"transfer_id": "ach_transfer_uoxatyh3lt5evrsdvo7q"
}
},
"status": "pending",
"type": "pending_transaction"
}
“Increase has been an invaluable banking partner to Modern Treasury. They support innovative, fast growing customers looking for high quality banking technology, and get our mutual customers moving money quickly. They understand the importance of speed to market and provide the right tools for building financial products.”
Dimitri Dadiomov
CEO, Modern Treasury
Let's talk specifics
The ACH file format (or Nacha file) is a text file with ASCII text lines, where each line is 94 characters long and serves as a record to execute domestic ACH payments through FedACH.
nacha.txt
1
2
3
4
5
6
7
8
9
10
101•0105000110531129292303302303A094101Increase•••••••••••••••Increase•••••••••••••••••••••••5200MYCOMPANY NC.•••••••••••••••••••••1602214076CCDPAYROLL•••2302142302140441123456780000001622123456789987654321000000003502586760•••••••••••••••IAN CREASE••••••••••••0839692747659385820000000139650193952939390509231938587261821602214076•••••••••••••••••••••••••1234567800000019000001000001000000018829592817293939050923193858726182•••••••••••••••••••••••••••••••••••••••
Record Type CodeFile header
A constant. Essentially, a version number. Impressive stability!
Priority CodeFile header
The lower the number, the higher processing priority. Currently, only 01 is used.
Immediate DestinationFile header
The sending bank's 9 digit ABA Routing number, preceded with a blank space.
Immediate OriginFile header
A ten-digit company identifier. Counterparties can use this to reconcile payments.
File Creation Date File header
The date the file was created, in YYMMDD format.
File Creation Time File header
The time the file was created, in HHMM format.
File ID ModifierFile header
A single character. Uppercase A-Z and 0-9 allowed. Starts with A and incremented for each file created during the calendar day.
Record SizeFile header
The number of characters per record. Always 94.
Blocking FactorFile header
Always 10. ACH files are padded with lines of 9s, so that the number of lines in the file are a multiple of 10. If the line count is already divisible by 10, no extra padding is needed.
Format CodeFile header
Always 1.
Immediate Destination NameFile header
The name of the federal reserve office to which the file is being sent.
Immediate Origin NameFile header
The name of the sending bank, padded to 23 characters.
Reference CodeFile header
Used to identify this file for accounting purposes. Often left blank.
Record Type CodeBatch header
The start of a batch within a file. Always 5.
Service Class CodeBatch header
Represents whether the batch contains debits (225), credits (220) or both (200).
Company NameBatch header
Your company name, up to 16 characters. This is often printed in receiver's statements.
This field can be set using the company_name field in the API. Read more.
Company Discretionary DataBatch header
Optional. As the name implies, the use is up to you.
This field can be set using the company_discretionary_data field in the API. Read more.
Company IdentificationBatch header
An identifier for your company. Should be stable. Generally, set by Increase but can be configured if necessary.
Standard Entry Class CodeBatch header
A three-letter code that describes how a payment was authorized by the receiver. Codes are defined and maintained by Nacha. Most common is CCD, for Corporate Credit or Debit. In practice, it's important to get the code right: using the wrong code can result in a return.
This field can be set using the standard_entry_class_code field in the API. Read more.
Company Entry DescriptionBatch header
A description of nature of the transactions to help counterparties identify the purpose. Examples: Payroll, Payables, etc.
This field can be set using the company_entry_description field in the API. Read more.
Company Descriptive DateBatch header
Optional. Descriptive date - often in YYMMDD with the same value as the effective date. Useful in recurring transaction scenarios, such as payroll.
Effective Entry Date Batch header
Effective / transaction date. Date the other party is to be debited or credited.
Settlement DateBatch header
The calendar date of the transaction. Fascinatingly, this field uses the Julian system, where dates run from 3:00AM to 2:59AM the following day.
Originator Status CodeBatch header
Constant.
Originating Financial InstitutionBatch header
Increase's routing number.
Batch NumberBatch header
Start with 0000001 and increment by 1 for each batch.
Record Type CodeTransaction entry
The start of a transaction within a batch. Always 6.
Transaction CodeTransaction entry
A code identifying the transaction:
- 22: A credit payment to a checking account
- 23: A credit pre-note to a checking account
- 27: A debit payment from a checking account
- 28: A debit payment from a checking account
- 32: A credit payment to a savings account
- 33: A credit pre-note to a savings account
- 37: A debit payment from a sacvings account
- 38: A debit payment from a sacvings account
Receiving Financial InstitutionTransaction entry
The other party's ABA routing number.
This field can be set using the routing_number field in the API. Read more.
Receiving Account NumberTransaction entry
Other party's account number, left-justified and zero-padded.
This field can be set using the account_number field in the API. Read more.
AmountTransaction entry
The transaction amount. No decimal. For pre-notifications, ten zeroes are used.
This field can be set using the amount field in the API. Read more.
Identification NumberTransaction entry
Optional. Helps the receiver (other party) identify themselves within your system, should they need to contact you. Typically their account number.
Receiving Company NameTransaction entry
The name of the transfer recipient. This value is information and not verified by the recipient's bank.
This field can be set using the individual_name field in the API. Read more.
Discretionary DataTransaction entry
Typically blank.
Addenda Record IndicatorTransaction entry
Either 0 (No addenda following) or 1 (Addenda following).
Trace NumberTransaction entry
The first 8 digits of your Originating DFI number, followed by the entry detail sequence number.
This field can be set using the trace_number field in the API. Read more.
Record Type CodeBatch footer
The start of batch footer. Always 8.
Service Class CodeBatch footer
Represents whether the batch contains debits (225), credits (220) or both (200). Must match the entry in the batch header.
Entry/Addenda CountBatch footer
Number of detail entry (transactions) and addenda records within the batch.
Entry HashBatch footer
Sum of the receiving DFI ID (first 8 digits of the other party's ABA routing number) for each entry/transaction within the batch.
Total Debit Entry Dollar AmountBatch footer
Total debits for the batch. No decimal.
Total Credit Entry Dollar AmountBatch footer
Total credits for the batch. No decimal.
Company IdentificationBatch footer
An identifier for your company. Should be stable. Generally, set by Increase but can be configured if necessary. Must match the entry in the batch header.
Message Authentication CodeBatch footer
Blank.
ReservedBatch footer
Blank.
Originating DFI IDFile footer
A detail as to the general nature of the transactions to help the other parties identify the purpose. Examples: Payroll, Payables, etc.
This field can be set using the company_discretionary_data field in the API. Read more.
Batch NumberFile footer
Must match the entry in the batch header.
Record Type CodeFile footer
The start of file footer. Always 9.
Batch CountFile footer
Number of batches in the file.
Block CountFile footer
Number of blocks in file (10 records = 1 block).
Entry/Addenda CountFile footer
Number of detail entry (transactions) and addenda records within the file.
Entry HashFile footer
Sum of the receiving DFI ID (first 8 digits of the other party's ABA routing number) for each entry/transaction within the file.
Total Debit Entry Dollar AmountFile footer
Total debits for the file. No decimal.
Total Credit Entry Dollar AmountFile footer
Total credits for the file. No decimal.
ReservedFile footer
Reserved.
Build your bank
Everything you need and nothing you don't
Direct connections to the networks for money transmission. Bank accounts that open instantly. Unopinionated building blocks that let you build for any funds flow or use case.
ACH
Originate ACH credits and debits, validate account numbers with pre-notifications and store commonly accessed details.
Bank Accounts
Commercial or consumer, FDIC insurance, unlimited account numbers.
Cards
Issue cards with custom art to businesses or consumers. Approve authorizations in real-time, or configure limits programmatically.
Checks
Send branded checks anywhere in the world with one API call. Or deposit checks via API or the dashboard.
Real-Time Payments
Transmit money to accounts at most major banks in seconds, not days.
Wires
The original instantaneous money transfer. Send money anywhere, anytime Fedwire is open.