Payer: Identifies the original source of funds. If both the account guid and an outside instrument guid are provided, funds will be pulled from outside instrument to the payer's account guid before being sent to the payee. However, the outside instrument guid must belong to the payer.

Payee: Identifies the ultimate recipient of funds. If both the account guid and an outside instrument guid are provided, funds will be deposited to the outside instrument from the payee's account guid after it is received from the payer. However, the outside instrument guid must belong to the payee.
This is not required for payment_request_code PT_CR_REPAYMENT; API will error out if provided.

Payment amount. Skip for payment types PT_CLEARING and PT_CR_REPAYMENT as it defaults to 0; the value will be ignored if sent.

Three letter currency code

Payment description

PT_TOPUP: For adding balance to an account if it reaches a certain balance.
PT_COLLECTION: For collecting funds from (multiple) external sources and collecting in a client collection account.
PT_ACCOUNTDISB: For disbursing funds from a client funding account to beneficiaries' account (or external account).
PT_CR_REPAYMENT: For repaying a funding account from external account.
PT_CLEARING: For sweeping the balance from a Clearing Account.
PT_SCH_TRANSFER: For scheduling a future-dated payment for Maker-Checker requests.
PT_RECURRING: For fixed (exact-amount) recurring payment schedules. The transfer amount is taken from payment_amount. Supports ACCOUNT2ACCOUNT, ACCOUNT2BANK, and BANK2ACCOUNT directions across all channels.

Payment balance - Minimum Balance in destination account to trigger Payment

Unique payment identifier. To be skipped in the request.

For future use. Required to chain multiple payments.

Response code for the payment. To be skipped in the request.

Reason code for the payment.

Requestor wallet guid

Scheduled date for the payment based on the business day adjustment rule. Required for scheduling a one time payment request.

Requested Scheduled date for the payment.

Unique client identifier for the payment.

Payment Schedule Class

Fields for error handling in case of maker-checker rejections or other processing errors. These will be populated in the response when applicable but are not expected to be sent in the request.