ACH Endpoints

ach/validate-nacha

This endpoint is used to trigger a NACHA validation on the provided bank account. In the endpoint below, either Token or ABARoutingNumber/AccountNumber are required. Either a CompanyName OR FirstName and LastName must be provided.

post/ach/validate-nacha

Request

  • Base URL
    https://earthnode-dev.vopay.com/api/v2
  • URL
    https://earthnode-dev.vopay.com/api/v2/ach/validate-nacha
  • Auth
    none declared

Request body multipart/form-data

AccountIDstring required

Your account ID

Keystring required

API key for the account

Signaturestring required

Hashed signature for the request

Tokenstring required

Your iQ11 Token that has been generated using Custom Iframe. This can be provided in lieu of a routing number and account number.

ABARoutingNumberinteger required

ABA routing number for customer's US bank account. This can be provided in lieu of a token.

AccountNumberinteger required

Customer's bank account number for transaction code. This can be provided in lieu of a token.

CompanyNamestring required

Company's name. This can be provided in lieu of first name and last name.

FirstNamestring required

Customer's first name. This can be provided in lieu of a company name.

LastNamestring required

Customer's last name. This can be provided in lieu of a company name.

PhoneNumberstring required

Customer's phone number. Digits only - no parentheses or dashes allowed.

Addressstring required

Customer's civic number and street name (eg. 123 Main Street)

Citystring required

Customer's city

Statestring required

Customer's state specified using two character abbreviations (eg. CA, AZ)

ZipCodestring required

Response

Response indicating the result of the NACHA validation.

Successboolean required

True if the request was successful, false if it failed

ErrorMessagestring required
ValidationResultstring required

The result of the NACHA validation. Possible values are: verified or failed.

Example response

{
  "Success": true,
  "ValidationResult": "verified"
}

Changes

No recorded changes to this operation across all 1 revision of this API.