v5
latestOpenAPI 3.1.02026-07-262421791.5 MBCreate a transfer
Create a transfer to a recipient account based on a quote.
Some fields are conditionally required depending on the currency route and transfer amount. Always call the transfer requirements endpoint to determine which fields are needed, and submit values accordingly. These requirements may change over time.
Avoiding duplicate transfers
The customerTransactionId field is used to avoid duplicate transfer requests. If your initial call to create a transfer fails (error or timeout), retry the call using the same customerTransactionId value. Subsequent retry messages are treated as repeat messages and will not create duplicate transfers. Use a sensible retry limit, ideally with a back-off approach.
Payment Approvals
{% admonition type="warning" %} Business Payment Approvals created on your wise.com settings page are not compatible with creating transfers over the API. {% /admonition %}
If you use personal tokens and do not use client credentials, and if your business account has payment approvals, your application will receive this error when attempting to create a transfer: Quote cannot be accepted with this request due to missing approval.
Consider removing the payment rule if you are going to use the API to create transfers.
Headers
Optional UUID for correlating requests across systems. If provided, Wise echoes it back in the response. Maximum 36 characters. Learn more.
Request body
Response
Transfer successfully created.
Example response
{
"id": 16521632,
"user": 4342275,
"targetAccount": 8692237,
"quoteUuid": "8fa9be20-ba43-4b15-abbb-9424e1481050",
"status": "incoming_payment_waiting",
"reference": "reference text",
"rate": 0.89,
"created": "2017-11-24 10:47:49",
"details": {
"reference": "Testing"
},
"sourceCurrency": "EUR",
"targetCurrency": "GBP",
"targetValue": 150,
"customerTransactionId": "54a6bc09-cef9-49a8-9041-f1f0c654cd88",
"payinSessionId": "23330542-8e9e-419f-95eb-312b880f92ad"
}