Get started with batches

Transfer funds into your Fire account for automatic distribution to employees or contractors.

Why use Fire to make batch payments?

Apply your own logic to manage and split funds. Initiate payouts via the Fire Payments API.
Manage unlimited account reconciliations, get instant payment notifications, set custom user access, and transfer money instantly between Fire accounts.

Find more use cases and examples on Fire's website.


How can you use Fire to submit batch payments?

πŸ“˜

See the Batches reference section for more detailed information.


Use our API to create, manage and send batch payments (processing multiple payment transactions as a single group or batch), eliminating manual fund distribution. You can also split payments using batches, and process refunds. Individual batches are identified by the batchUuid attribute, which you can find by calling 'List all Batches' first. Individual payments within batches are identified by the itemUuid.

Bank Transfer Batch Payment Sequence Diagram

Bank Transfer Batch Payment Sequence Diagram

If you want to practice using the batch payments API endpoints listed below, Fire has recipes created in Javascript to see how to use the API to do things like call a list of your accounts. To use these, you'll need our OpenAPI definition document, which you can download from our Github here.. You can use these endpoints to start creating batches, and to generate reports on them.

Fire allows the creation of 3 main batch types:

  • Bank Transfer batches - contain payments to other financial institutions in the UK and Ireland, or external Fire accounts
  • Internal Transfer batches - contain payments to your other Fire accounts
  • International Transfer batches - contain payments to be distributed outside of the UK and Ireland. These batches must be paid to existing payees

If you are adding payments to a batch, they must be the correct type for the batch they are being added to. All payments in a batch must be the same currency. New payee batches are created for you once you submit the batch, and are specifically to approve any new payees in an existing batch for users with approvals enabled. You can find more on payees below.


The first step for any batch type is to create a batch and save the batchUuid returned. If you have already created the batch, you can find this by listing all your batches.


Next, you should add all the payments to your batch using the batchUuid. The type of payment you can add depends on the type. Save the itemUuid for these payments. If you want to view any of these payments, you can find this by calling the details of this batch. If you would like to remove a payment after adding it, you can. Please note, any new payees will need to be approved, and you can view who these payees are using the 'List Items for a New Payee Batch' endpoint.


Bank Transfer batches:


Internal Transfer batches:


International Transfer batches:


Batch Details


Finally, once you have added your payments and are happy with it, you can submit your batch. Once it is submitted, you will need to approve any new payees if you have payee approval enabled. If you decide not to use this batch, you can cancel it. You cannot cancel a batch once it is submitted and approved.


Payees

Verification of Payee (VoP) is a mandatory service for SEPA payments aimed at preventing misdirected and fraudulent payments by confirming that the payee's name matches the provided bank account details (IBAN). For Euro payment batches, from October 2025, any new payee will have to be approved, irrespective of if approvals are enabled or not.

See how to write a script to use these endpoints here




Fire customers use our API to submit large batch payments, which ensures swift reconciliation to identify payees and automate payouts, thus avoiding manual errors. For example, JustTip has automated large volume batch payments to all employees across partner facilities, handling over 2000 payments in a short time.