Validating Bank Information with Routable

Hello, friends! Our changelog has been a little quiet lately, but don't worry - we've been hard at work adding a wide variety of small improvements across the API, from providing better information about international PaymentMethods to supporting pre-created Companies in your accounting software, searching Companiesby external_id, returning information about vendor risk checks in the Retrieve a Company call, and lots more.

However, today we're excited to announce a huge new feature that's been requested for some time: bank account validation! If you're collecting bank information directly in your app, you want to check that the information is correct to minimize failed Payables and help prevent fraud. In the past, Routable recommended that you verify bank account information via Plaid, but now, you can do it directly through the Routable API! It's super easy to add to an existing Routable integration; just POST to the new Validate a Payment Method endpoint the identical payload you're already sending to Create a Payment Method!

The result of this call is an object containing an array of checks. Currently, we check two things:

• The verification check confirms that the bank account exists and is open.
• The ownership check confirms that the bank account's owner matches the information provided in the Company identified in the company_id query parameter of the request.

{
  "id": "b4ae2dc9-f9ec-410f-a18c-ce612cdb4d84",
  "checks": [
    {
      "id": "268f4942-cf01-4b6e-84c8-3d3fcfbf0222",
      "type": "ownership",
      "created_at": "2025-06-02T17:57:05.350000+00:00",
      "result": "mismatch",
      "updated_at": "2025-06-02T17:57:05.350000+00:00"
    },
    {
      "id": "56b8cb0c-9b09-496c-beed-cf687eedd70f",
      "type": "verification",
      "created_at": "2025-06-02T17:57:05.350000+00:00",
      "result": "match",
      "updated_at": "2025-06-02T17:57:05.350000+00:00"
    }
  ]
}

For each check, one of four results are possible:

• match: We were able to confirm that the information is correct and valid.
• mismatch: We were able to confirm that the information is not correct and valid.
• no_data: No data was found to assess validity or ownership.
• unable_to_verify: The system was unable to verify (due to timeout, upstream failure, etc.)

Your app can then make the decision about whether or not to Create a Payment Method with the supplied information based on the result of the checks. Just pass the same payload to that endpoint as you do normally, and begin creating Payables with confidence!

💫

This is a new, optional feature!

To use Routable Bank Account Validation, we will need to enable it in your Workspace. Additional fees may apply. Contact your Routable Success Manager to start using it!

If you have not activated the feature in your Workspace, this endpoint will return a 402 Payment Required error.