Skip to main content

​
Overview

The Account Intelligence v3 endpoint is part of GrailPay’s real-time bank account validation system. It allows you to determine whether a user’s bank account is valid, active, and safe to use - helping you reduce fraud, prevent returns, and accelerate decision-making. With a single API call, the endpoint returns a confidence_score along with detailed decisioning_insights based on the identity and bank account data you provide. These insights can be used to drive onboarding, funding, and payout workflows with higher accuracy and lower risk. When constructing your request, you’ll pass an identity object that contains either an individual or an organization. These two are mutually exclusive: the request will fail if both are included. Use organization for validating business entities and individual for people. While the only required fields are account and routing numbers, we strongly recommend providing as much identity data as possible. More complete input data results in more meaningful confidence scores and more actionable insights.
This API is only available for U.S. bank accounts.
For complete request and response definitions, visit the Account Intelligence OpenAPI Documentation.

​
Actions

By default, every call to this endpoint performs core validation checks on the routing and account numbers. To enrich the results further, you can optionally include an actions object in your request to enable additional validation layers. Currently, the following action is supported:
  • name_match: Compares the provided name in the identity object with the account holder’s name on file.
To enable name matching, include the following in your request payload: 
{
  "actions": {
    "account_intelligence": {
      "version": "v3",
      "name_match": true
    }
  }
}
This triggers GrailPay’s proprietary name-matching engine, which contributes directly to the confidence score and provides additional clarity on identity matching. For full request and response examples, see the Account Intelligence API reference.

​
Usage Recommendations

  • Always pass complete and accurate identity data to maximize result quality.
  • Use the confidence_score and decisioning_insights to guide onboarding and risk workflows.
  • Review fields such as name_match, valid_routing_number, and negative_transactions_seen closely when the score is low.
  • Display insights to users (where appropriate) or use them in your internal logic to block or flag high-risk activity.

​
Questions?

If you’re encountering any issues, please reach out to [email protected].
⌘I