API Reference

Create an RTP, FedNow, or ACH verification transfer

post
https://api-sandbox.trice.co/hub/v1/smart_verify

Creates a new rtp or fednow verification transfer

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Smart verify body

int64
required
≥ 0

The verificaiton amount, must be less than or equal to 200.

boolean

If true then Trice will attempt to repossessed the credit(s)) asyncronously if the repo field is true, otherwise the credit(s)) will be repossessed syncronously if the repo field is truetrue.

string
length ≤ 8

Up to 8 alpha-numberic digits that will be added to the statement description.

uuid
required

The unique ID (RFC-4122 UUID) of the bank account enrollment to use in conjunction with this tranfer.

string
length ≤ 250

Up to 250 chars of additional information about the transaction only visible to you.

string
length ≤ 140

Up to 140 chars of additional information about the transaction shared with the receiver (FedNOW and RTP only).

network_deny_list
array of strings

If supplied the the array of values represents networks to omit from smart routing. Values can be rtp, fednow, ach_same_day and ach

network_deny_list
network_priority_list
array of strings

If supplied the the array of values represents network order of priority for smart routing. If not supplied the RTP network will be prioritized first, fednow second, ach_same_day thrird, and ach forth. Values can be rtp, fednow, ach_same_day and ach

network_priority_list
new_party
object

New party details. NOTE when bank_details name_match is used, the name match is only performed after a transfer is successfully leaves Trice and then run in parallel to the transaction as it is processing through it's subsequent states, Therefore webhooks may not contain resulting name_match_data. name_match_data will always be returned as a result of any successful transfer from the smart_verify and smart_transfer endpoint.

new_ultimate_receiving_party
object

New ultimate receiving party details

uuid

The unique ID (RFC-4122 UUID) of the party that the funds are being transfered to.

boolean

If true then the code field will be prepended to the statement description followed by a hyphen (-), otherwise the code field will be appended to the statement description after a hyphen (-). This field is only used if the FedNOW network is used.

string
length ≤ 35

Up to 35 chars of reference data about the transaction. If this is left undefined, the network will populate this field.

boolean

If true then Trice will attempt to repossessed the credit(s).

int64
≥ 0

The verificaiton amount of a second transfer, must be less than or equal to 200. Optional field that should only be used if intending 2 transfers.

uuid

The unique ID (RFC-4122 UUID) of the account whos data will be used to send the transfer.. This is only usable if the account ID is a descendant the account that is creating this transfer.

uuid

The unique ID (RFC-4122 UUID) of the party that the funds are ultimately being transfered to. This field is informational and used by the receiver to account for the final destination of the funds.

uuid

The unique ID (RFC-4122 UUID) of the party that the funds are ultimately being transfered from. This party must be associated with the account that the enrollment is associated with. This is only usable if the account has the intermediary_rtp_v_2_9 or intermediary_rtp_v_3_0 capability activated.

Headers
uuid

A key used to manage the response in the case of a duplicate request. If a response with the same key already exists, then the previous response will be echoed.

integer
0 to 30000

The amount of time in milliseconds to wait on a final status response. If this header is provided, the system will block until either the status is updated to a final response or the time value is exceeded. If the time value is exceeded, then the X-TRICE-WAIT-FOR header will be included in the response with the time in milliseconds that elapsed on the system. Note that this time may be longer than the initial header value because the system will always execute until the message is send to the network. If the time value submitted in the header is 0, then the system will block until there is a final response or the maximum system timeout of 30 seconds is reached.

uuid

A parent account can include this header as reference to the descendent account being operated on.

Responses

Updated 5 months ago

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 5 months ago