We've added more intelligence to our ABA Routing Support and RTP RfP APIs to increase certaintly that an RfP can be delivered to a specific customer segment (i.e. consumer, small business, or wholesale) at that receiving bank. Some banks only enable RfP for businesses, others only enable RfP for consumers. Knowing this information sooner improves your customer experience by setting the right expectations.

Note: this feature applies to RTP by The Clearing House only.

ABA Routing Support now includes RfP Supported Segements (new)

ABA Routing Support response now includes receive_rfp_detail to indicate which segments can receive an RfP.

{
  "rtp": {
    "receive_rfp": true,
    "receive_rfp_detail": {
      "consumer_accounts": true,
      "small_business_accounts": true,
      "wholesale_accounts": true
      ...
    }
	...
  }
}

Send RfP now checks for supported segment (new)

When sending an RfP, Trice compares the party's bank account type to the routing number's supported segments. If there is a known mismatch, the RfP cannot be sent and the API will respond with a 400 response (below).

The party's segment is determined by theparty.bank_details.account_holder_type field, which can be set to individual, business, or undefined (null). When the party's segment is not defined, RfP delivery is attempted but may result in a later reject/decline response.

{
  "errors": [
    {
      "message": "Routing number in bank details does not support receiving RTP RfPs for consumer accounts",
      "path": "system"
    }
  ]
}

Trice party API does not differentiate between small business and wholesale account types. The API makes best effort to determine if delivery should be attempted.