Create a payment draft

Create a payment draft.

When you create a payment draft, it stays a draft until you send it for processing as payment in the Revolut Business app.

Until then, you can delete the draft if you no longer wish to proceed with it.

Note

If you or the payment you're making is subject to an approval process, when you send the draft for processing, the payment goes into the Pending review state. Before it can be processed, the business owner, administrator, or another team member designated as an approver must approve it in the Revolut Business app.

For more information on use cases and other details, see the guides: Payment drafts.

Request​

The payment draft information

Request body

Body object

The title of the payment draft.

The scheduled date of the payment draft in ISO 8601 format.

The details of the payment(s) to be made.

The ID of the account to pay from.

Note

You can specify only one account ID for multiple payments in the same payment draft.

The details of the transfer recipient.

If the counterparty has multiple payment methods available (e.g. 2 accounts, or 1 account and 1 card), you must specify the account (account_id) or card (card_id) to which you want to transfer the money.

The ID of the receiving counterparty.

The ID of the receiving counterparty's account. Used for bank transfers.

If the counterparty has multiple payment methods available, use it to specify the account to which you want to send the money.

The ID of the receiving counterparty's card. Used for card transfers.

If the counterparty has multiple payment methods available, use it to specify the card to which you want to send the money.

The amount of the payment.

Pattern: Value must match regular expression ^[A-Z]{3}$

ISO 4217 currency code in upper case.

The reference for the payment. A piece of text or number you provide to help identify what the payment relates to. It can be used, for example, for reconciliation or tracking purposes.

You might include an invoice number, account or transaction ID, or any other reference meaningful to you.

Possible values: [shared, debtor]

The party that should bear the transaction fees related to the selected transaction route if applied. Possible options are:

• shared: Also known as SHA. The transaction route fees are split between the sender and the recipient. The sender pays the fees charged by their bank, while the recipient pays the fees charged by the receiving and any intermediary banks.
• debtor: Also known as OUR. The sender pays all explicit transaction fees.

Note

• This field is not supported for bulk payments.
• Some transactions with fees might not support charge bearer selection. If this is the case, the request will return error 3287. To proceed with the default fee handling, remove this field from your request and try again.

Response​

The ID of the payment draft that was created

Response body

Body object

The ID of the payment draft created.