Batch examples
The following examples show a terse set of fields. It is common to include additional data in a request, but the examples show the absolute minimum fields necessary to make a payment.
Transactions with a recipient
Here we'll send £100 to a recipient in France. To do so, we'll create a CSV file that contains the following data:
| Field | Value |
| SendCurrency | GBP |
| SendValue | 100 |
| RecipientName | Jules Verne |
| RecipientCountry | FR |
| RecipientCurrency | EUR |
| RecipientReference | Book Payment |
| AccountIban | FR1420041010050500013M02606 |
| AccountSwift | CCBPFRPPINS |
The corresponding CSV data is shown below, if you hover over the text you can copy the example to the clipboard.
SendCurrency,SendValue,RecipientName,RecipientCountry,RecipientCurrency,RecipientReference,AccountIban,AccountSwift
GBP,100,Jules Verne,FR,EUR,Book Payment,FR1420041010050500013M02606,CCBPFRPPINSTransactions with a Stored recipient
If you wish to upload a batch that targets stored recipients, there's a minimal set of fields you need to fill in. In this example, we'll assume you have a stored recipient already defined within the system of AAA-BBB-CCC.
| Field | Value |
|---|---|
| SendCurrency | GBP |
| SendValue | 100 |
| StoredRecipientId | AAA-BBB-CCC |
| RecipientReference | Book Payment |
The corresponding CSV data is shown below, if you hover over the text you can copy the example to the clipboard.
SendCurrency,SendValue,StoredRecipientId,RecipientReference
GBP,100,AAA-BBB-CCC,Book PaymentAs you can see, this provides an extremely terse way to create a transaction in the system. You can use stored recipient details with all transaction types, just replace the standard recipient fields with the StoredRecipientId and RecipientReference.
Updated about 2 months ago