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.

1. Send RfP on behalf of a child. A parent account can send an RfP on behalf of a child account by presenting an RfP presentment that belongs to its child account. This is useful when the parent account owns the parties but the child account is the actual RfP sender.
2. Internal description increased to 250 on smart_transfers, smart_verify, rtp_transfers, and fednow_transfers
3. Improve RTP / FedNow error handling. When sending a credit transfer to RTP or FedNow, if the message cannot be delivered to the network for any reason (network is down, Trice is down, etc), we will fail the transaction quickly and return a 400 quickly instead of returned a pending credit transfer that is manually updated to failed status once investigated.
4. Delete new_party after smart_verify transfer completes. If new_party is provided when creating a smart_verify transfer, the party is deleted when the transfer completes since it is not longer needed.

🆕 Added Smart Verify API for instantly verifying that an account is open and can receive transactions. Can also use this API to verify account ownership. Read about it here

Fix: Trice APIs now enforce that text provided to our APIs is valid with respects to both RTP and FedNow. The allowed character set is UTF-8 Basic Latin and and Latin-1 Supplement (excluding control characters), which is 0x20-0x7F and 0xA0-0xFF.

Search for Transfers

Smart Transfers API: Let Trice route your payment instruction to the correct rail (RTP or FedNow) based on what rails the account supports, the bank's status (signed on or off), and the preferences that you indicate.

Reduce processing time for outbound RTP credit transfers. Customers sending RTP credit transfers should expect to see credit transfers transition to their final status (completed, rejected, failed, etc.) about 1 second faster.

Fixed issue where updating a verified party (see https://triceapi.readme.io/reference/update_party) did not set the verified data correctly, which causes 404 when using that party as an ultimate sending party when creating a credit transfer.

Internal fixes for RTP credit transfers and RfPs. No impact to API. Fixed the following:

1. Early access to our FedNow APIs with simulator are available. Please contact us to request access. We continue developing and testing our FedNow capability and expect to launch in the coming weeks.
2. Multi-bank improvements:
   1. Add Bank Capabilities API: this new API manages what capabilities your Trice account has with one of our sponsor banks. Customers with the undewriter capability can use this API to manage capabilities for their child accounts.
   2. Add Enrollments API (GET): this new API will enable easier management of your Trice accounts that are enrolled with instant payment rails. Customers with the aggergator capability can use this API to view / manage enrolments for their child accounts.
3. Expired RfP improvement: when an RfP expires before it is paid, we send an RfP cancelation just in case the other bank is still displaying an expired RfP.