ACH Network is the national automated clearing house (ACH) for electronic funds transfers. It processes financial transactions for consumers, businesses, and federal, state, and local governments. ACH processes large volumes of credit and debit transactions in batches. Short for "Automated Clearing House", ACH credit transfers include direct deposit for payroll, Social Security and other benefit payments, tax refunds, and vendor payments. ACH direct debit transfers include consumer payments on insurance premiums, mortgage loans, and other kinds of bills.
The rules and regulations that govern the ACH network are established by National Automated Clearinghouse Association (NACHA). In 2018, the network processed 23 billion transactions with a total value of $51.2 trillion.
Source: ACH Network
To learn more about the full ACH process please visit our Overview of ACH.
In addition to sending ACH transactions via batch files, TabaPay Clients are now able to send individual ACH transactions via the Create Transaction API. This makes for an easier integration and adoption of ACH from a Client's perspective.
How to access the ACH API?
Please contact [email protected] to request access to the ACH API.
ACH API only supports the creation of transactions, a merchant will still need to be prepared to receive any output files to receive any rejections or returns.
ACH via the API only supports Next Day ACH transactions at this time (future updates will include Same Day ACH transactions as well).
- When a TabaPay client sends a Create Transaction request, the API will "batch" that transaction.
- Once the cut-off for Next Day transactions is met, the "batched" transactions will be processed by TabaPay.
- "Processed" means we construct a NACHA file and pass it on to the bank.
- At that point a merchant would receive a "processed" file with the status of each transaction. Some transactions may be rejected, and status codes will be provided to explain these rejections. For more information on the different files you might receive: ACH file types.
- In some cases, you may receive an Output file as well - this file is generated by some banks to let us know when the transaction was sent to the Fed. This file has the exact same format as the Processed file, and will include the Trace ID from the Fed. Might take up to 2 days to be sent.
- If there are any returns you will receive a Return file - this file contains a list of returned transactions. Can come back 6 to 7 days later.
- Any transactions that are received by the system after the cut-off time will be processed during the following "Next Day" window.
ACH API integration can be broken up into two components:
- Backend integration -> Integrating with the TabaPay Create Transaction API.
- SFTP/File based integration -> You will need to be setup to receive files from TabaPay. Here is a list of the files you would receive from TabaPay ACH response and processed files.
- You can use the Retrieve Transaction API to retrieve the status of a "batched" or "processed" transaction. In the future, we will extend this functionality to support other status types (i.e. "returned", etc.).
You will be using the Create Transaction API.
All ACH transactions are pulling or pushing funds to a bank account.
- One key field for you to include is the
achOptionsfield. You would use
Nfor Next Day ACH (RTP is also supported using the same field).
- The other key field for you to include is the
achEntryTypefield. This is a new field, 3 characters long with only three options:
- For a pull ACH transaction, you would fill in the
bankobject in the source account object.
- For a push ACH transaction, you would fill in the
bankobject in the destination account object.
- There are other additional fields common to all transactions (e.g. amount, etc.).
bank object is available for the
destinationAccount objects. It contains the following information:
ABA routing transit number
Bank Account Number
Bank Account Type.
- S Savings
- C Checking
- A Business Savings
- B Business Checking
- L Loan
N-> Next Day
- All transactions since last batch are processed.
- Cut-off times:
- Next day: 6pm PT.
- If a transaction missed the cutoff they will be moved to next window
Please review the processed file
Please check the processed file to see which transactions were successfully submitted to the bank and which transactions were rejected by TabaPay (along with the corresponding error codes)
TabaPay pushes ACH files via SFTP
Get in touch with us via [email protected] to get your setup going.
Security options can include:
- Merchant whitelists TabaPay IP
- SFTP ID and Password
- TabaPay public key for SFTP security (ID or ID+PW)
- File encryption using Merchant public PGP key
For file formats of the various ACH-related files TabaPay provides, please refer:
For reference on ACH Return Codes, go here.
TabaPay output files, processed files, return files:
- Merchant pickup return files, Processed files, and Output files in the 'Outbox'
- Processed file delivered within minutes of ACH files being processed by bank; one file for each merchant batch.
- [Optional] Output file delivered next business day; same format as Processed file - with Trace ID and processed time from bank
Supported status types
Retrieve Transaction API currently supports "BATCH" and "COMPLETE" statuses. If the API returns a "COMPLETE" status, that means that the transaction has been processed. You should check the subsequent
processed.csvfile to see if the transaction was sent off to the bank or rejected by TabaPay (e.g. "over the limit").
Currently you will need to receive the ACH response and processed files to see if a transaction was successfully processed or not.
In the future, Retrieve Transaction will support additional status types like "rejected", "returned", etc.
|"BATCH"||The transaction is stored in our database, but it has not been processed yet.|
|"COMPLETE"||If the API returns a "COMPLETE" status, that means that the transaction has been processed. You should check the subsequent |
Updated about 1 month ago