Create an RTP or FedNow transfer

Creates a new rtp or fednow transfer

Log in to see full request history
Body Params

Smart transfer body

int64
required
≥ 0

The transfer amount.

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.

network_deny_list
array of strings

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

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. Values can be rtp and fednow

network_priority_list
new_party
object

New party details

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.

string
length ≤ 35

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

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
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

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