Secure Payments API – Create NACHA Processor


NACHA transactions are gathered throughout the day and are then consolidated in a single file for each 24 hour period at a specified time. The NACHA file will consist of any transactions that have been created in the period since the previous transaction was exported. An example of creating the processor is as follows:

How To

To create a NACHA processor, send a POST request to the following endpoint:


Sample payload:

"nacha": {
"name": "Wells Fargo Tertiary 447WCs",
"cutoff_time": "23:15",
"bank_routing": "026012881",
"tax_id": "123456789",
"bank_name": "WELLS FARGO BANK",
"company_name": "Prime Lending",
"discretionary_data": "Nothing",
"export_type": "none"

Sample cURL payload:

curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'authorization: YOUR AUTHORIZATION' --header 'secret: YOUR SECRET' -d '{ \
"nacha": { \
"name": "Test Processor", \
"cutoff_time": "22:15", \
"bank_routing": "123123123", \
"tax_id": "12-3456789", \
"bank_name": "Test Bank", \
"company_name": "My Company", \
"discretionary_data": "Data", \
"export_type": "none" \
} \
}' ''

The response will be the ID of your newly created NACHA processor. Notice that in the above example “22:15” is given as the cutoff_time. This value is the time when the NACHA file for this processor will be generated every day with “00:00” being midnight. Note that you can enter any time string with an "HH:MM" format, but the batch process only runs every 15 minutes. So, if you enter "10:08" as the time, the process will actually run at "10:15". All NACHA export times are in UTC standard time.

When NACHA files are generated, any special character names will be scrubbed out. Accepted character are 0-9 a-z A-Z - & , .

How did we do?

Powered by HelpDocs (opens in a new tab)