We are legally obliged to collect the actual sender and beneficiary details. Please do not send us intermediate organisation details such as exchanges, banks, gateways, etc.
If sending from yourself, there's an option to use your company's Flash account details as sender by default. Please consider the examples below.
Sender - senderId or subClientId , or neither
To use subClientId as the sender for your payments, please execute the createPayment mutation as below.
If your company is the ultimate sender for an FX payment, you can skip both the senderId and subClientId. In this situation, we will use your company’s Flash account as the sender for the payment. Please note that a new sender record will not be created in this case.
Please execute the following createPayment mutation to use your company's Flash account details as sender.
Please always send us the ultimate sender and recipient. If sending to yourself, please provide your own details. See the schema in for other recipient details options.
In the above createPayment example, you had to and use senderId as an input. Alternatively, if your account is configured to make FX payments on behalf of your , you may provide us with the sub-client ID, and the FX payment created will be linked to that sub-client. In this case, the subClientId will be used as the sender and will be reported to the government.
Callback (aka ) URI
The optional callbackUri will be invoked several times during the processing of a payment. These callbacks will usually occur soon (within several seconds) after the initial create payment call - but may be delayed in some cases. The example JSON payloads can be found on the .
The callback (aka ) endpoint URI can be invoked by anyone in the internet. Thus opening up a potential attack vector. See page to secure your data properly.
