Secure Payments API – Lookup/Verify Routing Number


You can lookup and verify bank information from a routing number. Authentication can be through either a combination of authorization and secret or a single OBO token.

How To

There are two methods to get a routing number. Both methods will require sending a GET request to this endpoint:


Replace {number} with the routing number you want to test.

Method 1: Uses the authorization and secret.

This request works like most GET requests in Secure Payments: Include your typical authorization and secret, but leave the body empty. Here's a cURL request:

curl -X GET --header 'Accept: application/json' --header 'authorization: YOUR AUTH' --header 'secret: YOUR SECRET' 

Method 2: Uses an OBO token as the identifier.

Users can do this as well, but this method exists for the benefit of the iFrame that creates payment profiles. The iFrame isn't aware of your token or secret, but it does know the OBO token and can use it. Leave your header empty and expand your endpoint with the OBO token:

curl -X GET ''


Whatever method you used, the response should look the same. If the routing number is legitimate, you'll get a 200 message with the name of the bank and some other information:

"code": 200,
"rn": "324377516",
"message": "OK"

A phony routing number will also yield a 200 response, but this one will say "Unspecified" instead of listing the bank:

"name": "Unspecified",
"code": 200,
"rn": "1555524002971",
"message": "OK"

How did we do?

Powered by HelpDocs (opens in a new tab)