Initiate a cross-border remittance

Amount in the major currency unit of the associated wallet e.g. 50.80 for 50 GBP and 80 pence

Optional. Who the remittance is going to. Either this or destination is required

The URL Eclipse must post the WalletRemittanceResult to when the remittance is finalised (either successful or error). Optional as one can always do a GET to get the result instead of using callbacks. This will be a system-system call

This is only applicable when the driving currency is FX currency, as denoted by useFxCurrencyAsBase=True. Consequently, it is an optional field. If both destinationAmount and useFxCurrencyAsBase=True are provided, destinationAmount will retain its value while the amount will be adjusted

The destination currency - e.g. USD, ZAR, NGN, TSH

Provide a GUID for the remittance to prevent replays/duplicates

Save the profile details of the destination as a new beneficiary against the wallet owner

Amount in the major currency unit of the associated wallet e.g. 50.80 for 50 GBP and 80 pence

The currency of the wallet - e.g. USD, ZAR, NGN, TSH

Amount in the major currency unit of the associated wallet e.g. 50.80 for 50 GBP and 80 pence being used to buy the destination currency at the exchange rate

The amount to pay in the wallets currency for one major unit of the destination currency. The recipient will get exchangeAmount/exchangeRate in the destination currency

Loosely typed data resulting from the remittance payment. E.g. could be a voucher code if the payment was for a VAS. The structure depends on what was being paid for.

Fee that will be decuted from wallet in wallet currency. walletFeeAmount + walletSendingAmount = walletTotalAmount

The transaction identifier for this remittance as provided by the gateway itself

Status of a remittance

If fees are INCLUSIVE this will be same as sourceAmount,if fees are EXCLUSIVE it will be sourceAmount + fee