Freedom251 › Open Banking Payment Platforms
Fire Payments API
What Fire Payments API is
Fire Payments API connects Fire’s digital payment services to applications and back-office systems so businesses can automate payment work. It can initiate batches of internal transfers and local or cross-border payouts from a customer’s own systems. Businesses can also issue cards, block or unblock them, and manage card limits. Payment requests let customers pay by bank transfer and collect extra information for reconciliation.
The API retrieves current transaction, payee, user and balance information for reconciliation and internal operations. Customers can check balances and move funds between their Fire accounts in real time. Developers can use Fire’s OpenAPI specification to build a backend client library in their preferred programming language. Fire says customers need to contact sales to create an account before setting up an API application and choosing permissions. Its payment services use a security framework designed to meet PSD2 technical standards, with payment batches authorised and authenticated through the Fire for Business mobile app. Fire-EU is regulated by the Central Bank of Ireland as a Payment Institution; Fire-UK is authorised by the FCA as an Electronic Money Institution. Customer funds are held separately from operational funds, under safeguarding that differs from bank deposit guarantee schemes. Pricing is paid, with a listed note from €10/mo and customised corporate pricing available on request.
Who it suits
Fire Payments API suits fintechs and corporate clients that want payment processing built into their applications or back-office systems. It is aimed at teams that need to automate transfers, payouts, card controls, payment requests or reconciliation through an API.
What it does well
- Automates internal transfers and local or cross-border payouts.
- Supports card issuance, blocking and limit management.
- Payment requests support bank transfer with reconciliation data.
- Retrieves transaction, payee, user and balance information.
- Enables real-time balance checks and transfers between Fire accounts.
- OpenAPI specification supports client libraries in preferred languages.
What to know first
- Requires a Fire account created through the sales team.
- Standing orders and scheduled payments are unsupported.
- Event notification API is currently unsupported.
- Corporate pricing is customised on request.
Limits
API access requires a Fire account, and standard business fees vary by service and currency. The TPP API documentation says standing orders, scheduled payments and event notifications are not supported.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Fire Business Account (API access) | Contact Fire’s sales team for an account; customised corporate pricing is available on request. · API access requires a Fire account · standard business fees vary by service and currency | On request |
As fire.com lists them, read 28 Sept 2026. The maker's own page has the final word.
Getting started
- Contact Fire sales to create a Fire account.
- Set up an API application and select its permissions.
- Use Fire’s OpenAPI specification to build a backend client library in your preferred language.
- Use the Fire for Business mobile app to authorise and authenticate payment batches.
Verdict
Choose Fire Payments API if your fintech or corporate operation needs to integrate Fire payments, payouts, card controls and reconciliation into its own systems. Look elsewhere if standing orders, scheduled payments or event notifications are required.
Questions
How much does Fire Payments API cost?
The listed pricing note is from €10/mo. Customised corporate pricing is available on request, and standard business fees vary by service and currency.
Is there a free plan?
No. The pricing model is paid.
Which platforms does it support?
The listed platforms are Android, API, iOS and web.
How do developers integrate it?
Fire provides an OpenAPI specification for building a backend client library in a preferred programming language.
Does it support standing orders or scheduled payments?
No. The TPP API documentation says standing orders and scheduled payments are not currently supported.
How do customers get API access?
Fire says prospective customers should contact its sales team to create a Fire account, then configure an API application with selected permissions.
Facts from Fire Payments API's own pages
- Account setup
- Fire says customers should contact its sales team to create a Fire account before setting up an API application with selected permissions. · docs.fire.com, 28 Sept 2026
- Cards
- The API can issue cards and let customers block or unblock them and manage limits from their own systems. · fire.com, 28 Sept 2026
- Cash flow
- Customers can check balances and transfer funds between their Fire accounts in real time through the API. · fire.com, 28 Sept 2026
- Founded
- 2010 · fire.com, 28 Sept 2026
- Headquarters
- Dublin, Ireland · fire.com, 28 Sept 2026
- Integrations
- Fire provides an OpenAPI specification that developers can use with their preferred programming language to build a client library for backend integration. · docs.fire.com, 28 Sept 2026
- Intended customers
- Fire says it focuses on fintechs and corporate clients that need integrated payment processing as part of their business. · fire.com, 28 Sept 2026
- Notable limits
- Fire’s TPP API documentation says it does not currently support standing orders, scheduled payments or the event notification API. · fire.com, 28 Sept 2026
- Open banking
- The API can create payment requests so customers can pay by bank transfer, with additional data collected for reconciliation. · fire.com, 28 Sept 2026
- Payouts
- The API can initiate batches of internal transfers and local or cross-border payouts from a customer’s own systems. · fire.com, 28 Sept 2026
- Purpose
- The Fire Payments API integrates Fire’s digital payment services into applications and back-office systems to automate payment processes. · fire.com, 28 Sept 2026
- Reconciliation
- The API can retrieve current transaction, payee, user and balance information to support automated reconciliation and internal operations. · fire.com, 28 Sept 2026
- Regulation
- Fire-EU is regulated as a Payment Institution by the Central Bank of Ireland and Fire-UK is authorised as an Electronic Money Institution by the FCA. · fire.com, 28 Sept 2026
- Safeguarding
- Fire says customer funds are safeguarded in accounts separate from its operational funds, and this safeguarding is different from bank deposit guarantee schemes. · fire.com, 28 Sept 2026
- Security
- Fire says its payment services use a security framework designed to meet PSD2 technical standards, including authorisation and authentication of payment batches through the Fire for Business mobile app. · fire.com, 28 Sept 2026
- Support
- Fire directs prospective customers to [email protected] and existing customers to [email protected]. · fire.com, 28 Sept 2026
Where Fire Payments API stands on Freedom251
- Open Banking Payment Platforms#6 of 22