Route Check

Swagger UI

You can view the full API documentation in our Swagger UI. This collection provides detailed information about all available endpoints, including request and response schemas, parameters, and examples.

Check if Instant RTP Supports a Specific Route (by routing number)

Before sending an Instant RTP, a route check must be done using a Route Inquiry API to determine if the recipient is reachable via RTP.

The route check will confirm:

• If the receiving bank or account supports RTP
• What type of payments are allowed (max amount, currency, etc.)
• Whether the destination is reachable instantly

To check if Instant RTP supports a specific route, use the following endpoint:

GET /api/v3/InstantRtpRoutes/{routingNumber}

Note

routingNumber is required.

routingNumber is the routing number you want to check, essentially a nine-digit number that functions as the bank’s address. It can be obtained from the transaction details or user profile.

The response contains:

• isServiceHealthy: Whether the InstantRTP service is operating normally. A value of false indicates a detected service disruption.
• isAvailable: Whether the routing number supports instant credits through RTP or FedNow.
• isSignedOn: Whether the financial institution is currently signed on to an instant payment network.
• routingNumber: Routing number supplied in the request.
• statusCode: Route check result: ROUTE_AVAILABLE, ROUTE_NOT_AVAILABLE, ROUTE_BLOCKED, or ROUTE_NOT_FOUND.
• statusMessage: Text description of the route check result.