https://www.brainiac.software/api/v1/bank-payments/uk-modulus-check$0.02 USDCUK sort code + account modulus check
Check whether a UK sort code and account number pair can be valid using Vocalink modulus weights (valacdos/scsubtab) and exceptions 1–14.
Body
| Field | Required | Notes |
|---|---|---|
sortCode | Yes | string |
accountNumber | Yes | string |
Request exampleJSON
{
"sortCode": "089999",
"accountNumber": "66374958"
}Response exampleJSON
{
"sortCode": "089999",
"accountNumber": "66374958",
"standardisedAccountNumber": "66374958",
"standardisedSortCode": "089999",
"checksAvailable": true,
"checks": [
{
"algorithm": "MOD10",
"weights": [
0,
0,
"…"
],
"exception": null,
"total": 180,
"passed": true
}
],
"valid": true,
"result": "valid",
"specVersion": "9.20",
"sources": [
{
"source": "Vocalink UK modulus checking v9.20 (valacdos.txt, scsubtab.txt)",
"url": "https://www.vocalink.com/tools/modulus-checking/",
"retrievedAt": "2026-11-14",
"status": "ok"
}
],
"limitations": [
"A pass means the pair can be valid. It does not prove the account exists or is open.",
"Sort codes not in the weight table cannot be checked and are presumed valid (spec 2.2.1 step 1).",
"…"
]
}cURL
curl -i -X POST "https://www.brainiac.software/api/v1/bank-payments/uk-modulus-check" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"sortCode": "089999",
"accountNumber": "66374958"
}
JSONhttps://www.brainiac.software/api/v1/bank-payments/sepa-creditor-id-validate$0.01 USDCValidate a SEPA Creditor Identifier
Parse a SEPA Direct Debit Creditor Identifier and recompute ISO 7064 Mod 97-10 check digits (business code excluded).
Body
| Field | Required | Notes |
|---|---|---|
creditorId | Yes | string |
Request exampleJSON
{
"creditorId": "DE98ZZZ09999999999"
}Response exampleJSON
{
"creditorId": "DE98ZZZ09999999999",
"country": "DE",
"checkDigits": "98",
"expectedCheckDigits": "98",
"businessCode": "ZZZ",
"nationalIdentifier": "09999999999",
"valid": true,
"sources": [
{
"source": "EPC262-08 Creditor Identifier Overview v12.0 (algorithm only)",
"url": "https://www.europeanpaymentscouncil.eu/document-library/guidance-documents/creditor-identifier-overview",
"retrievedAt": "2025-10-05",
"status": "ok"
}
],
"limitations": [
"Format and check digits only; does not confirm the CI was issued.",
"Outputs are lookups or prechecks for human review. They are not legal, customs, tax, medical, or identity determination…"
]
}cURL
curl -i -X POST "https://www.brainiac.software/api/v1/bank-payments/sepa-creditor-id-validate" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"creditorId": "DE98ZZZ09999999999"
}
JSONhttps://www.brainiac.software/api/v1/bank-payments/iban-from-bban$0.01 USDCBuild an IBAN from a BBAN
Compute ISO 13616 check digits for a country code and domestic BBAN, then validate the resulting IBAN structure.
Body
| Field | Required | Notes |
|---|---|---|
country | Yes | string |
bban | Yes | string |
Request exampleJSON
{
"country": "GB",
"bban": "NWBK60161331926819"
}Response exampleJSON
{
"iban": "GB29NWBK60161331926819",
"ibanPrint": "GB29 NWBK 6016 1331 9268 19",
"checkDigits": "29",
"valid": true,
"expectedBbanLength": 18,
"sources": [
{
"source": "SWIFT IBAN Registry lengths + ISO 13616 mod-97",
"url": "https://www.swift.com/standards/data-standards/iban",
"retrievedAt": "2026-11-14",
"status": "ok"
}
],
"limitations": [
"Builds check digits only. Does not validate national account check digits or confirm the account exists.",
"Outputs are lookups or prechecks for human review. They are not legal, customs, tax, medical, or identity determination…"
]
}cURL
curl -i -X POST "https://www.brainiac.software/api/v1/bank-payments/iban-from-bban" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"country": "GB",
"bban": "NWBK60161331926819"
}
JSONhttps://www.brainiac.software/api/v1/bank-payments/uetr-validate$0.01 USDCValidate or generate a UETR
Validate an ISO 20022 UETR as a UUID version 4, or generate one or more UETRs with crypto.randomUUID().
Body
| Field | Required | Notes |
|---|---|---|
uetr | No | string |
generate | No | boolean |
count | No | integer |
Request exampleJSON
{
"uetr": "eb6305c9-1f7f-49de-aed0-16487c27b42d"
}Response exampleJSON
{
"uetr": "eb6305c9-1f7f-49de-aed0-16487c27b42d",
"valid": true,
"version": 4,
"variant": "RFC4122",
"normalised": "eb6305c9-1f7f-49de-aed0-16487c27b42d",
"reason": null,
"sources": [
{
"source": "ISO 20022 UUIDv4Identifier / RFC 9562 UUID version 4",
"url": "https://www.rfc-editor.org/rfc/rfc9562",
"retrievedAt": "2026-11-14",
"status": "ok"
}
],
"limitations": [
"ISO 20022 UETR values are UUID version 4; other UUID versions are rejected.",
"Pattern matching is case-insensitive; normalised output is lower-case for ISO 20022 pattern compatibility.",
"…"
]
}cURL
curl -i -X POST "https://www.brainiac.software/api/v1/bank-payments/uetr-validate" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"uetr": "eb6305c9-1f7f-49de-aed0-16487c27b42d"
}
JSONhttps://www.brainiac.software/api/v1/bank-payments/postal-address-check$0.02 USDCCBPR+ postal address format check
Classify an ISO 20022 PostalAddress as structured, hybrid or unstructured and check Swift CBPR+ town/country/AdrLine rules.
Body
| Field | Required | Notes |
|---|---|---|
address | Yes | object; Object |
role | No | string; One of: party, agent; Default: "party" |
agentHasBic | No | boolean |
messageType | No | string |
Request exampleJSON
{
"address": {
"StrtNm": "MARK LANE",
"BldgNb": "55",
"BldgNm": "THE CORN EXCHANGE",
"Flr": "6",
"PstCd": "EC3R 7NE",
"TwnNm": "LONDON",
"Ctry": "GB",
"AdrLine": []
},
"role": "party",
"messageType": "pacs.008"
}Response exampleJSON
{
"format": "structured",
"cbprCompliant": true,
"issues": [],
"exempt": false,
"cbprRetirementDate": null,
"sources": [
{
"source": "Swift ISO 20022 unstructured address removal / CBPR+ postal address rules",
"url": "https://www.swift.com/standards/iso-20022/removal-unstructured-address",
"retrievedAt": "2026-11-14",
"status": "ok"
}
],
"limitations": [
"cbprRetirementDate is null because Swift deferred the original 14 Nov 2026 retirement; the revised timeline is pending.",
"Free-text AdrLine values are not parsed into structured fields.",
"…"
]
}cURL
curl -i -X POST "https://www.brainiac.software/api/v1/bank-payments/postal-address-check" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"address": {
"StrtNm": "MARK LANE",
"BldgNb": "55",
"BldgNm": "THE CORN EXCHANGE",
"Flr": "6",
"PstCd": "EC3R 7NE",
"TwnNm": "LONDON",
"Ctry": "GB",
"AdrLine": []
},
"role": "party",
"messageType": "pacs.008"
}
JSONhttps://www.brainiac.software/api/v1/bank-payments/nacha-file-build$0.04 USDCBuild a NACHA ACH file
Generate a 94-character NACHA ACH file (PPD/CCD/WEB/TEL) with batch hashes, totals and blocking-factor padding from JSON entries.
Body
| Field | Required | Notes |
|---|---|---|
immediateDestination | Yes | string |
immediateOrigin | Yes | string |
destinationName | Yes | string |
originName | Yes | string |
fileCreationDate | Yes | string |
fileCreationTime | Yes | string |
fileIdModifier | No | string; Default: "A" |
batches | Yes | array; Array |
Request exampleJSON
{
"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"
}
]
}
]
}Response exampleJSON
{
"file": "101 02100002112345678902611160900A094101JPMORGAN CHASE ACME CORP \n5200ACME CORP …",
"lineCount": 10,
"batchCount": 1,
"entryAddendaCount": 2,
"entryHash": "0003200003",
"totalDebit": 2500,
"totalCredit": 150000,
"serviceClassCodes": [
"200"
],
"warnings": [],
"sources": [
{
"source": "Nacha ACH Guide for Developers",
"url": "https://achdevguide.nacha.org/ach-file-overview",
"retrievedAt": "2026-11-14",
"status": "ok"
}
],
"limitations": [
"Generated from the Nacha ACH Guide for Developers; your ODFI may require different File Header values.",
"Outputs are lookups or prechecks for human review. They are not legal, customs, tax, medical, or identity determination…"
]
}cURL
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"
}
]
}
]
}
JSONhttps://www.brainiac.software/api/v1/bank-payments/nacha-file-validate$0.03 USDCValidate a NACHA ACH file
Validate NACHA record order, lengths, ABA checksums, batch/file hashes and totals, reporting every structural error by line.
Body
| Field | Required | Notes |
|---|---|---|
file | Yes | string |
maxErrors | No | integer; Default: 200 |
Request exampleJSON
{
"file": "101 02100002112345678902611160900A094101JPMORGAN CHASE ACME CORP \n5200ACME CORP 1234567890PPDPAYROLL 261117 1021000020000001"
}Response exampleJSON
{
"valid": true,
"summary": {
"lines": 10,
"batches": 1,
"entries": 2,
"totalDebit": 2500,
"totalCredit": 150000
},
"errors": [],
"warnings": [],
"sources": [
{
"source": "Nacha ACH Guide for Developers",
"url": "https://achdevguide.nacha.org/ach-file-overview",
"retrievedAt": "2026-11-14",
"status": "ok"
}
],
"limitations": [
"Structural and checksum validation only; ODFI acceptance rules are not applied.",
"Outputs are lookups or prechecks for human review. They are not legal, customs, tax, medical, or identity determination…"
]
}cURL
curl -i -X POST "https://www.brainiac.software/api/v1/bank-payments/nacha-file-validate" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"file": "101 02100002112345678902611160900A094101JPMORGAN CHASE ACME CORP \n5200ACME CORP 1234567890PPDPAYROLL 261117 1021000020000001"
}
JSONhttps://www.brainiac.software/api/v1/bank-payments/camt053-parse$0.03 USDCParse camt.052/053/054 statements
Parse an ISO 20022 bank-to-customer statement or report into normalised JSON with balance reconciliation checks.
Body
| Field | Required | Notes |
|---|---|---|
xml | Yes | string |
includeRaw | No | boolean; Default: false |
Request exampleJSON
{
"xml": "<Document xmlns=\"urn:iso:std:iso:20022:tech:xsd:camt.053.001.08\">...</Document>",
"includeRaw": false
}Response exampleJSON
{
"messageType": "camt.053.001.08",
"statements": [
{
"id": "STMT-1",
"createdAt": "2026-11-13T18:00:00Z",
"account": {
"iban": "DE89370400440532013000",
"currency": "EUR"
},
"balances": [
{
"type": "OPBD",
"amount": "1000.00",
"currency": "EUR",
"creditDebit": "CRDT",
"date": "2026-11-13"
},
{
"type": "CLBD",
"amount": "1100.00",
"currency": "EUR",
"creditDebit": "CRDT",
"date": "2026-11-13"
}
],
"entries": [
{
"amount": "100.00",
"currency": "EUR",
"creditDebit": "CRDT",
"status": "BOOK",
"bookingDate": "2026-11-13",
"valueDate": "2026-11-13",
"accountServicerRef": "REF1",
"bankTxCode": {
"domain": "PMNT",
"family": "RCDT",
"subFamily": "ESCT"
},
"endToEndId": "E2E-1",
"remittance": [
"INV 123"
],
"counterparty": {
"name": "ACME GMBH",
"iban": "DE44500105175407324931"
}
}
],
"balanceReconciles": true
}
],
"checks": {
"balanceReconciles": true
},
"sources": [
{
"source": "ISO 20022 camt.052/053/054 message definitions",
"url": "https://www.iso20022.org/iso-20022-message-definitions",
"retrievedAt": "2026-11-14",
"status": "ok"
}
],
"limitations": [
"Parses common element paths only; no XSD validation is performed in this endpoint.",
"Amounts remain decimal strings; they are never converted to floating-point numbers.",
"…"
]
}cURL
curl -i -X POST "https://www.brainiac.software/api/v1/bank-payments/camt053-parse" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"xml": "<Document xmlns=\"urn:iso:std:iso:20022:tech:xsd:camt.053.001.08\">...</Document>",
"includeRaw": false
}
JSON