Create Expected Payment

The amount of the payment, in string representation. All amounts should be passed in full subunits, e.g. 1000 for 10.00

The asset_code of the payment. The asset must've been created in the system before it can be used in payments

Additional metadata for the payment. This can be any key-value pair that is relevant to the payment. For example, a payment can have a metadata key of "invoice_id" with a value of "1234" to map it internally to an invoice

The network of the payment, such as SEPA, or Providers such as Wise

The payment reference used by the sender to reconcile the payment

The source account ID of the expected payment

The amount of the payment, in string representation. All amounts should be passed in full subunits, e.g. 1000 for 10.00

The asset_code of the payment. The asset must've been created in the system before it can be used in payments

The destinations for a payment, such as recipients or revenue accounts

The unique ID of the payment

The source account ID of the payment

The current status of the payment

The unique ID of the payment in the external system. This ID will guarantee the idempotency of the operation

The transfer reference used by the sender to reconcile the payment. Typically, this is a reference code that is included by the the sender in bank-transfers