Smart Verify API
Instantly verify that a bank account is open and can receive payments using Trice's new Smart Verify API.
Instantly verify that a bank account is open and can receive payments using Trice's new Smart Verify API. Use this API to send a microdeposit ($2.00 or less) to any bank account that can receive via RTP or FedNow. The API intelligently routes to the right network based on availability (i.e. which rail(s) supported), its connectivity status (i.e. active or offline), and your preferences.
The receiving bank will display the sender's name for the transaction. Sender name is the sender's DBA or entity name of the account that is sending the credit transfer. If you want to display a verification code, keep reading!
Display a verification code (FedNow only)
The API can send a credit transfer with a verification code that you provide. Trice will append code and/or memo fields (if they are provided) to the sender name using "-" as the delimiter to ensure important data is displayed to the end user. Use prepend_code=true to prepend the verification code before the sender name.
The verification code is displayed to the end user in their banking app. Your application can request the user to log into their bank app, view the transaction with verification code, and return that verification code back to your application to verify control of the account.
Verification Code Examples:
| code field | memo field | Displayed to end user* |
|---|---|---|
| null (or not defined) | "1234" | sender_name-1234 |
| "ab1234" | null (or not defined) | sender_name-ab1234 |
| "ab1234" with prepend_code=false (or omitted) | "account verify" | sender_name-ab1234-account verify |
| "ab1234" with prepend_code=true | "account verify" | ab1234-sender_name-account verify |
| "ab1234" with prepend_code=true | null (or not defined) | ab1234-sender_name |
*Receiving banks may truncate the display name to as few as 15 characters
Note: RTP network operating rules do not allow appending/prepending any data to the sender name.
Note: the verification code is not stored / returned in the API. If you need Trice to store it, add this data to the internal_descriptionfield or persist it within your application.
Verify account control using microdeposits
Call the Smart Verify API twice using 2 different amounts ($2.00 or less). Your application can request the user to log into their bank app, view the 2 transactions, and return the transaction amounts back to your application to prove ownership of the account.
Updated 3 days ago