Global currencies is a Wise product that allows sending to currencies in countries other than the one the currencies are domestic to. For example, sending US dollars to a person or business in Hong Kong, rather than the USA.
It is quite common, especially for businesses, to operate in USD, GBP, or EUR while based outside of the respective country of these currencies. In some countries, bank accounts for these currencies do not use the standard account details that a domestic account would, like account number and sort code in UK. Instead, these accounts are more likely to use an IBAN.
Global currencies are sent via the Swift network and therefore have some limitations, though Wise has worked hard to reduce these as much as possible.
The primary limitation to be aware of that Wise cannot guarantee the full amount of the transfer will reach the recipient, regardless of the type of instruction (OUR or SHA). There is always a chance that one or more correspondent bank involved in the transfer of funds will incur a fee.
While the charging mechanism (OUR/SHA/BEN) is included and states the intention of the sending bank, two issues remain:
- Intermediary and recipient banks can and may ignore or not support the specified type.
- The instruction can get lost if the transfer ends up moving through a local scheme that doesn't support it.
This is fundamentally a Swift issue and a big part of why Wise exists as a company.
Wise has continuously worked to provide the best experience around global currencies so you can properly inform your customers as much as possible. The details included in this guide highlight how to best create transfers for global currencies, when and how we smart-select OUR vs SHA, and how you can override that logic if required.
When offering global currencies, you must communicate to your customers that there are potentially additional fees for this type of transfer.
For example:
To send this transfer, we must use the Swift network, which is more expensive and slower than normal transfers. Intermediary banks may also take extra fees from the amount you send. We cannot guarantee the exact amount that will be received by your recipient for transfers sent via the Swift network.
There are three scenarios where we use the Swift network to send a global currency transfer. These are delineated by the type of recipient and currency of the transfer.
- A USD recipient of type
swift_code - A GBP recipient of type
ibanwhere the IBAN does not start withGB - A EUR recipient of type
swift_codewhere the IBAN does not start with one of the SEPA country codes (the transfer is to a non-SEPA country).
To create a global currency transfer:
- Create a quote for the currencies you wish to send between (like GBP to USD). If using Swift, ensure to set
payOuttoSWIFT, which will give the best estimate on the fees charged for the transfer. - Create a recipient and ensure it includes the recipient account requirements.
- Update the quote with the ID of the recipient.
The payOut field of the quote updates to be of type SWIFT or SWIFT_OUR. The paymentOptions array updates to also have a payOut of type SWIFT or SWIFT_OUR with updated fees.
At this point, you have a full quote in a supported global currency with the correct recipient type. Ensure that the updated information in the quote is communicated to your user. You should also take note of whether SWIFT or SWIFT_OUR will be used.
Wise automatically selects SHA or OUR based on aggregated data, previous transfer experience, and machine learning. This ensures that we accurately deliver the full amount of global currency transfers 93%+ of the time, with only 37% of those being sent through OUR. It also ensures that this consistently improves over time.
Following the steps above ensures most transfers are received in full without sacrificing fees.
In certain cases, you may want to force the use of OUR with Swift. This is possible, but it must be configured for your integration internally. Contact your Wise implementation team if you would like this option enabled.
Once configured, you can supply payOut of type SWIFT_OUR when creating quotes. This forces the quote to be generated with fees and be processed as OUR.
When a refund occurs for global currency transfers, the refunded amount might be less than the original sent amount due to intermediary bank fees. Additionally, failing to read the actual refunded amount may result in reconciliation errors. The method to determine the exact refunded amount varies depending on the settlement and refund model used.
With bulk settlement, we offer two refund models:
- Transfer-by-transfer: If you are using bulk settlement with the transfer-by-transfer refund model, you must subscribe to the
transfers#refundwebhook. When a transfer is refunded, you will receive a webhook notification with the updated status, followed by the actual refund credited back to your account. To determine the final refunded amount, check your account balance. Note that the settlement journal does not need to include refunded transfers. - Net settlement: For those using the net settlement refund model, subscribe to the
payout#createwebhook. The refund amount is specified in theamountfield. In the settlement journal, only include the transfer reference in the refunds section, rather than the refund amount itself.
You must subscribe to the balances#update webhook to receive the actual refund amount in your balance. Use the transfer_reference field to trace back to the transfer ID of the refunded transaction.
If you are using the transfer-by-transfer settlement model, subscribe to the transfers#refund webhook to receive the refund amount.