Skip to main content

Dedicated API for TPP developers

Fire provides an open banking v3.1 dedicated API for TPPs to access Fire Business and Fire Personal accounts.

Fire ASPSP information

We recommend the use of the Forgerock test facility.

Open banking API version  

v3.1

Auto-registration supported 

Yes – https://dia-api.fire.com/tpp/register

Base API DNS URL

https://dia-api.fire.com

x-fapi-financial-id 
CPAY

Logo URL


https://siteapi.fire.com/wp-content/uploads/2024/07/Fire-logo-white-with-TM_large.png

https://siteapi.fire.com/wp-content/uploads/2024/07/Fire-logo-dark-violet-with-TM_large.png

OpenID config endpoint

Generic – https://dia.fire.com/.well-known/openid-configuration
Personal accounts – https://dia.fire.com/personal/.well-known/openid-configuration
Business accounts – https://dia.fire.com/business/.well-known/openid-configuration

Payload signing cert location

https://dia.fire.com/.well-known/jwks.json

Discovery and application registration

The open banking specification for registering with Account Servicing Payment Service Providers (ASPSPs) is available on the open banking confluence.

Fire supports dynamic client registration (DCR), and uses tls_client_auth for registration endpoint authentication. The certificate used must match the certificate specified in your registration request (specified in the tls_client_auth_dn field), and must be present in your JWKS file.

Please use RFC1779 format when specifying Distinguished Names (DNs) of your certificates. e.g. CN=dia-api.fire.com, O=Fire Financial Services Limited, OID.2.5.4.97=PSDIE-CBI-C58301, L=Dublin, ST=Dublin, C=IE, OID.2.5.4.5=464819, OID.2.5.4.15=Private Organization, OID.1.3.6.1.4.1.311.60.2.1.3=IE. This is generally available as an option in most programming languages – e.g. for Java:

transportCert.getSubjectX500Principal().getName(X500Principal.RFC1779);

Token exchange

Fire uses tls_client_auth for token endpoint authentication. The certificate used must match the certificate specified in your Application registration request (specified in the tls_client_auth_dn field), and must be present in your JWKS file.

Account information

Fire’s account information APIs enable you to access accountholder details, account information, balances and transaction history for Fire business and personal PSUs.

The list of the PSU’s payees/beneficiaries and direct debit mandates is also available.

See the Open Banking Confluence page for Account Information API specifications.

Payment initiation

Confirmation of funds

Fire’s confirmation of funds API enables you to obtain a Yes/No response indicating whether or not funds are available for a particular payment.

See the open banking confluence page for confirmation of funds API specifications.

Event notification

Fire currently does not provide the event notification API.

Have queries about the Fire dedicated API? Get in touch by email.