ACH Return Reason CodesR01/R07 Table Lookup
Bounded offline reference: Two bounded ACH return-code descriptions support exact normalized codes. Source: NACHA return-code documentation. Timing, eligibility and application depend on the applicable network rule edition. Supported topic keys: R01, R07. No complete external corpus or live policy implied.
Description
ACH return codes identify reasons within entry and authorization rules.
ACH return codes identify reasons within entry and authorization rules.1
A short code explanation does not validate a return's timing, eligibility or transaction context. Use ACH Return Reason CodesR01/R07 Table Lookup to read a supported reference-card topic.
When to use ACH Return Reason CodesR01/R07 Table Lookup
Use ACH Return Reason CodesR01/R07 Table Lookup to read a supported reference-card topic. Choose an exact supported token from the table, preserving punctuation and capitalization.
How to use ACH Return Reason CodesR01/R07 Table Lookup and understand its results
- Choose an exact supported token from the table, preserving punctuation and capitalization.
- Enter Topic using the field table and validation rules below, then run the tool.
- Read Text in the Result object; interpret the units, signs, ordering and unknown-value placeholders described below.
- Read the chosen stored entry in the context below; consult the stated limits and correct unsupported tokens before rerunning.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| topic | Topic | string | Required; constraints below |
Enter one of the exact supported topic tokens listed below. The implementation performs a case-sensitive own-key lookup and returns the stored text unchanged. It does not fetch the cited books, search a corpus or inspect current policy. Unsupported tokens and added whitespace are input errors. The entries are stored explanations rather than retrieved source passages; read the stated scope and assumptions alongside the selected token. This bounded card is not a complete reference database.
returned text = storedTable[exactSupportedToken] Use the field order, units and branch conditions described above.
| Exact supported token | Stored reference text |
|---|---|
| R01 | Insufficient funds:the available balance is inadequate under the applicable return context. |
| R07 | Authorization revoked by customer:applies under the applicable entry and authorization rules. |
| Output field | Meaning | Value type |
|---|---|---|
| result | Object containing the named result fields below. | object |
| result.text | Stored text for the exact supported token; read summary, reference and limitations together. | string |
{
"input": {
"topic": "R01"
},
"output": {
"result": {
"text": "Insufficient funds:the available balance is inadequate under the applicable return context."
}
}
}Limitations and assumptions
A short code explanation does not validate a return's timing, eligibility or transaction context. Apply the exact scope and assumptions explained above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.
Alternative or Complementary methods
Use Decline Code Do Not Honor Meaning Lookup for a related task: A generic issuer decline does not disclose a unique underlying cause.
Use Card Expiry CVV Length Checker for a related task: A card's expiration month convention is distinct from its CVV format policy.
References
Similar or alternative tools
- Decline Code Do Not Honor Meaning Lookup
A generic issuer decline does not disclose a unique underlying cause.
- Card Expiry CVV Length Checker
A card's expiration month convention is distinct from its CVV format policy.