Skip to content
SPECIFICTION
Get listed

Fire Payments API vs Tarabut Gateway Account Information

Fire Payments API

fire.com

Tarabut Gateway Account Information

tarabut.com

Side by side

FigureFire Payments APITarabut Gateway Account Information
Price from——
Free plan——
Free trial——
Open source——
WebYesYes
iOSYes—
AndroidYes—
APIYesYes
Plans published11
Spec score · Open Banking Payment Platforms7.7 (#5)7.1 (#14)
Founded20102018
HeadquartersDublin, IrelandRiyadh, Saudi Arabia

Plans

Fire Payments API

  • Fire Business Account (API access)Priced on request

Fire Payments API pricing →

Tarabut Gateway Account Information

  • Production accessPriced on request

Tarabut Gateway Account Information pricing →

In their own words

Fire Payments 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.

Visit fire.com

Tarabut Gateway Account Information

Tarabut Gateway Account Information connects customer bank accounts through an Open Banking consent journey and provides account data after permission is granted. Its Connect service supplies an embeddable URL that guides customers through bank selection, permissions, bank authentication, and consent. Available information can include accounts, transactions, direct debits, and beneficiaries. Transaction responses may include category and merchant details through Insights. Documentation says one year of transaction history is fetched by default, although available history varies by bank. Consent can be one-time or long-term; long-term consent lasts up to 12 months and is required for categorisation. Refresh frequency depends on the bank, while APIs can request updated balances and transactions. Connect supports English and Arabic. Customers can withdraw access at any time, and Tarabut says credentials remain with the bank. A free Portal account provides an isolated development sandbox. Tarabut presents Connect for personal finance, spend management, and lending flows, with API and web access.

Visit tarabut.com