ACH Account Validation- iStream

Overview

When using runner.js to tokenize ACH payment information, you may validate the Routing Number (ABA) and Demand Deposit Account (DDA) number before processing an ACH transaction. This validation helps reduce the risk of failed transactions due to invalid or fraudulent banking information. Please inquire with integrations@runpayments.io to have this enabled for your merchant account.

Validation Process

Request Account Validation

When submitting an ACH tokenization request with validation enabled, the system performs real-time verification of the provided banking details against multiple risk factors including:

  • Routing number validity
  • Account number format
  • Known fraud patterns
  • Historical transaction data

Response Format

The validation response includes a Risk Information object containing two critical fields:

},
"risk_info": {
"decision": " ",
"reason": " "
},

Decision Codes

The decision field will return one of three possible values:

CodeMeaningDescriptionRecommended Action
AAcceptThe account information passed all validation checks and is considered low riskProceed with tokenization and transaction processing
WWarningThe account information passed basic validation but has some risk indicatorsReview additional risk factors before proceeding; consider additional verification steps
DDeclineThe account information failed validation or is considered high riskDo not proceed with tokenization; reject the transaction and request alternative payment method

Example Response

Successful Validation Response:

1{
2 "token_info": {
3 "token": "22455816"
4 },
5 "risk_info": {
6 "decision": "Accepted",
7 "reason": ""
8 },
9 "bank_info": {
10 "routingNumber": "074912319",
11 "paymentType": "ach",
12 "name": "Creek City Bank",
13 "addressFull": "113 W Market St, Warsaw, IN 46580",
14 "street": "113 W Market St",
15 "city": "Warsaw",
16 "state": "IN",
17 "zip": "46580",
18 "phone": "574-267-7855",
19 "active": "Active",
20 "lastUpdated": "Mar 25, 2024"
21 }
22}