Build a NACHA ACH file API
Generate a 94-character NACHA ACH file (PPD/CCD/WEB/TEL) with batch hashes, totals and blocking-factor padding from JSON entries.
The Build a NACHA ACH file operation is part of the UK Modulus NACHA IBAN UETR camt053 API API on BRAINIAC.software. Generate a 94-character NACHA ACH file (PPD/CCD/WEB/TEL) with batch hashes, totals and blocking-factor padding from JSON entries. It is exposed as POST /api/v1/bank-payments/nacha-file-build and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Vocalink UK modulus checking v9.20 (vendored valacdos.txt and scsubtab.txt) EPC262-08 Creditor Identifier Overview (algorithm only) SWIFT IBAN Registry lengths + ISO 13616 ISO 20022 UUIDv4Identifier / RFC 9562 Swift CBPR+ postal address rules Nacha ACH Guide for Developers ISO 20022 camt.052/053/054 message definitions Limitations: No live bank, Vocalink, Nacha or ISO registry HTTP call is made at request time. UK modulus and IBAN/CI checks do not prove an account exists or is open. NACHA generation follows the public ACH Guide for Developers; ODFI-specific header rules may differ. Outputs are lookups or prechecks for human review. They are not legal, customs, tax, medical, or identity determinations. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include UK sort code + account modulus check, Validate a SEPA Creditor Identifier, Build an IBAN from a BBAN, Validate or generate a UETR. Open the group documentation for the full request schema, field notes, and response examples before integrating.
/api/v1/bank-payments/nacha-file-buildExample request
curl -i -X POST "https://www.brainiac.software/api/v1/bank-payments/nacha-file-build" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"immediateDestination": "021000021",
"immediateOrigin": "1234567890",
"destinationName": "JPMORGAN CHASE",
"originName": "ACME CORP",
"fileCreationDate": "2026-11-16",
"fileCreationTime": "09:00",
"fileIdModifier": "A",
"batches": [
{
"companyName": "ACME CORP",
"companyId": "1234567890",
"secCode": "PPD",
"entryDescription": "PAYROLL",
"effectiveEntryDate": "2026-11-17",
"odfiRouting": "02100002",
"entries": [
{
"transactionCode": "22",
"rdfiRouting": "021000021",
"accountNumber": "123456789",
"amount": 150000,
"individualId": "EMP001",
"name": "JANE DOE"
},
{
"transactionCode": "27",
"rdfiRouting": "011000015",
"accountNumber": "987654321",
"amount": 2500,
"individualId": "INV42",
"name": "JOHN ROE"
}
]
}
]
}
JSONAn unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.
FAQ
- Do I need an API key? No. Pay the listed USDC amount with x402.
- What network? Base (eip155:8453), USDC.
- Is this an official determination? No. Results are for human review against the cited sources.
Related operations
- UK sort code + account modulus check — $0.02 USDC
- Validate a SEPA Creditor Identifier — $0.01 USDC
- Build an IBAN from a BBAN — $0.01 USDC
- Validate or generate a UETR — $0.01 USDC
Related APIs
UK Modulus NACHA IBAN UETR camt053 API APIFull docsHow it works