Skip to main content
POST
/
service
/
checks
/
verify
Verify Check
curl --request POST \
  --url https://api.example.com/service/checks/verify \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "routingNumber": "<string>",
  "accountNumber": "<string>",
  "amount": 123,
  "checkNumber": "<string>",
  "currency": "USD",
  "payerName": "<string>",
  "frontImage": "<string>",
  "backImage": "<string>"
}
'
{
  "data": {
    "verificationId": "<string>",
    "riskScore": 123,
    "routingNumberValid": true,
    "createdAt": "<string>",
    "reasons": [
      "<string>"
    ]
  },
  "message": "<string>"
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Check verification request body

​
routingNumber
string
required

ABA routing number extracted from the MICR line

Required string length: 9
​
accountNumber
string
required

Bank account number the check is drawn on

​
amount
number
required

Check amount in the smallest currency unit (e.g. cents)

​
checkType
enum<string>
required

Type of check being verified

Available options:
personal,
business
​
checkNumber
string

Sequential number printed on the check

​
currency
string
default:USD

ISO 4217 currency code

​
payerName
string

Name of the account holder issuing the check

​
frontImage
string

Base64-encoded image of the front of the check captured from a scanner or mobile app

​
backImage
string

Base64-encoded image of the back of the check

Response

Check verification completed successfully

​
data
object
required
​
code
enum<string>
Available options:
health_status_ok,
health_status_error,
validation_error,
bad_request,
unauthorized,
forbidden,
not_found,
method_not_allowed,
internal_server_error,
organization_not_found,
cannot_access_organization,
api_key_not_found,
resource_already_exists
​
message
string