Select type from the list at Payment Orders

The payment type used to create the payment order if the original type is not valid for the receiving account. Currently, this only supports falling back from RTP to ACH (type=rtp and fallback_type=ach)

An additional layer of classification for the type of payment order you are doing. This field is only used for ach and cross_border payment orders currently. Select subtype from the list at Payment Orders

Describes the direction money is flowing in the transaction. A credit moves money from your account to someone else's. A debit pulls money from someone else's account to your own.

The ID of one of your organization's internal accounts

Either receiving_account or receiving_account_id must be present. When using receiving_account_id, you may pass the id of an external account or an internal account.

Specifies the ID of a ledger transaction that will be linked to the payment order. If the payment order status and ledger transaction status do not match, the payment order creation will fail. The resulting ledger transaction will mirror the status of the payment order. See Linking to other Modern Treasury objects.

Must conform to ISO 4217. Defaults to the currency of the originating account. For currency conversions, this must be the target currency.

Either normal or high. high priority is only available for ach, eft, and check payment types. For ACH and EFT payments, high represents a same-day transfer. For check payments, high can mean an overnight check rather than standard mail. For all other payment types, high priority payments are treated the same as normal priority payments.

An optional description for internal use.

An optional descriptor which will appear in the receiver's statement. For check payments this field will be used as the memo line. For ach the maximum length is 10 characters. Note that for ACH payments, the name on your bank account will be included automatically by the bank, so you can use the characters for other useful information. For eft the maximum length is 15 characters.

For ach, this field will be passed through on an addenda record. For wire payments, this field will be passed through as the "Originator to Beneficiary Information", also known as OBI or Fedwire tag 6000. For rtp payments, this field will be included on the recipient's transaction.

For wire, this is usually the purpose which is transmitted via the "InstrForDbtrAgt" field in the ISO20022 file. If you are using Currencycloud, this is the payment.purpose_code field. For eft, this field is required and is the 3 digit CPA Code that will be attached to the payment.

The party that will pay the fees for the payment order. Read Charge Bearer to learn more about possible values and how they get serialized

Indicates the type of FX transfer to initiate, can be either variable_to_fixed, fixed_to_variable, or null if the payment order currency matches the originating account currency.

If present, indicates a specific foreign exchange contract number that has been generated by your financial institution.

If present, this will replace your default company name on receiver's bank statement. Banks may institute maximum character lengths for different payment types. Characters above this limit may be truncated.

The id of the account to which the origination of this payment should be attributed to. You may pass the id of a virtual account or an internal account.

Name of the ultimate originator of the payment order.

Identifier of the ultimate originator of the payment order.

Name of the ultimate funds recipient.

Identifier of the ultimate funds recipient.

An optional user-defined 180 character unique identifier