Queued transactions batch

The main difference between a queued transaction and an immediate transaction is that you specify the RequestedValueDate column as shown below. You can also optionally specify a value for the DateSearchMode, which can be either Forward or Backward (the default).

When this line is processed, we'll verify that the requested value date can be achieved, and if so when the batch is approved we'll queue the transaction for later processing, such that the recipient will receive their funds on the desired date.

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,RequestedValueDate
GBP,100,Jules Verne,FR,EUR,Book Payment,FR1420041010050500013M02606,CCBPFRPPINS,2020-06-04

📘

Note

As in the immediate TX example, this shows a terse set of fields - it's common to include additional data in a request, this has the absolute minimum fields necessary to make a payment. Also note that fields with defaults, such as the DateSearchMode are excluded from the file example as they are optional.

Please also be aware that the example file won't run as-is, as it includes a date parameter of 2020-06-04 for the requested value date, and this is now well in the past, so if you wish to try out this example please alter the date accordingly.

To read more about how queued transactions work, please read the full details here.