Fire Payments API vs TrueLayer Data API

Fire Payments API connects Fire’s digital payment services to applications and back-office systems, letting fintechs and corporate clients automate payment processes. It can initiate batches of internal transfers and local or cross-border payouts, issue cards, and manage card blocks and limits. Businesses can create bank-transfer payment requests with added information for reconciliation, retrieve transaction, payee, user and balance data, and move funds between Fire accounts in real time. Developers can use Fire’s OpenAPI specification to build backend integrations in their preferred programming language. Customers need to contact sales to open a Fire account before configuring an API application and its permissions. Fire says payment batches are authorised and authenticated through the Fire for Business mobile app, within a framework designed to meet PSD2 technical standards. Fire-EU is regulated by the Central Bank of Ireland, while Fire-UK is authorised by the FCA. Customer funds are held separately from operational funds; this is not a bank deposit guarantee. Pricing is paid, from €10/mo, with corporate pricing available on request.

TrueLayer Data API gives applications access to identity, account, transaction and balance data for integrated banks through a single interface. Account details may include the holder’s name, account number and IBAN; card data may include the network, last four digits and name on card, with balances and transactions available at card level. Listed uses include account verification and aggregation, affordability checks, rewards and insights, and money management. TrueLayer offers a customizable user journey or a custom authentication flow for regulated customers. Non-regulated customers and agents of TrueLayer customers must use the customizable flow. Documentation lists client libraries for Node.js, Python, Java and .NET, as well as web and mobile SDKs and hosted payment-page options. The free Sandbox plan uses mock data and has no production access. Production pricing is based on volume and use case; access requires a registered business or commercial entity, a signed commercial agreement and KYB/KYC. TrueLayer requires HTTPS and says data is encrypted at rest and in transit. Identical API requests are cached for one hour, and persistently unreasonable request volumes may be throttled or blocked. The company is headquartered in London and was founded in 2016.