Dedicated API for TPP Developers

fire.com provide an Open Banking v3.1 dedicated API for TPPs to access fire.com personal and business accounts.

fire.com Directory Information

While fire.com are using the Open Banking specification to provide its API, it is not a member the Open Banking Directory as an ASPSP.

All the required directory information is outlined below.

We recommend the use of the Forgerock test facility.

Open Banking API Version
v3.1

Auto-Registration Supported
Yes – https://dia.fire.com/open-banking/v3.1/register

Base API DNS URI
https://dia.fire.com

Logo URI

Developer Portal URL
https://www.fire.com/developers/tpp-api

OpenID Config Endpoint
https://dia.fire.com/.well-known/openid-configuration

Payload Signing Cert Location
https://dia.fire.com/.well-known/com.fire.dia.jwks

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.com 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 as a use: "tls" certificate.

OpenID Configuration

The OpenID Configuration at https://dia.fire.com/.well-known/openid-configuration specifies the various endpoints and algorithms supported by fire.com.

TPP Application Registration

Register applications at https://dia.fire.com/open-banking/v3.1/register.

fire.com accepts SSAs signed by Open Banking or self-signed. If you are providing a self-signed SSA, create it as defined in the Open Banking spec and sign using your signing key.

Token Exchange

fire.com use 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 as a use: "tls" certificate.

Token Endpoint

The token endpoint at https://dia.fire.com/open-banking/v3.1/token is used to retrieve access tokens.

Access Token for consent request.

Use a client_credentials grant with tls_client_auth to retrieve the first access token.

Access Token for resource access.

Use an authorization_code grant with tls_client_auth to obtain an access token after redirecting the PSU. A Refresh Token will also be returned for Account Info and Funds Confirmation scoped requests.

Access Token from Refresh Token.

Use a refresh_token grant with tls_client_auth to obtain further access tokens.

Access Tokens

fire.com access tokens are in JWT format, and expire in 600 seconds.

Refresh Tokens

fire.com refresh tokens are in JWT format and have an expiry equal to the length of time specified by the consent request.

A TPP can only have one active refresh token/long-lived consent with a fire.com PSU. If a second consent is processed, it will revoke and overwrite the previous one.

Account Information 

fire.com’s Account Information APIs enable you to access accountholder details, account information, balances and transaction history for fire.com 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.

Accounts

The /accounts endpoint is paginated and will return a max of 25 accounts per page.

Balances

The /balances endpoint is paginated and will return a max of 25 accounts per page.

Transactions

The /transactions and /accounts/{accountId}/transactions endpoints are paginated and will return a max of 25 transactions per page.

Beneficiaries

The /beneficiaries endpoints are paginated and will return a max of 25 beneficiaries per page.

The /accounts/{accountId}/beneficiaries endpoint will return only beneficiaries of the same currency as the account specified. For example, if {accountId} is a sterling account, only sterling beneficiaries will be returned.

fire.com beneficiaries are not tied to an account, so every account of the same currency will return the same list of beneficiaries.

Direct Debits

The /direct-debits and /accounts/{accountId}/direct-debits endpoints are paginated and will return a max of 25 mandates per page.

Party

The /party endpoint will return the details of the user who has signed into fire.com and provided the consent.

The /accounts/{accountId}/party endpoint provides the details of the account name for the specified fire.com account.

Standing Orders, Products, Offers, Scheduled Payments and Statements

fire.com do not provide these endpoints.

Payment Initiation

fire.com’s Payment Initiation APIs enable you to initiate payments from a business or personal PSU account.

See the Open Banking Confluence page for Payment Initiation API specifications.

Payments

All fire.com payments – either in Sterling or Euro – are domestic payments. It is only possible to initiate sterling payments from fire.com sterling accounts, and euro payments from fire.com euro accounts.

Scheduled Payments and Standing Orders

fire.com do not currently support standing orders or scheduled payments.

References

fire.com treats the references and identifiers in the payment request as follows:

  • Initiation/EndToEndIdentification – at present it is not possible for the EndToEndIdentification to be passed in the payment.
  • Initiation/InstructionIdentification – ignored.
  • Initiation/RemittanceInformation/Unstructured – ignored.
  • Initiation/RemittanceInformation/Reference – this will appear on the payee’s statement.
  • Initiation/CreditorAccount/Name – will be displayed on the fire.com PSU’s statement as the payee name.

The fire.com PSU will be offered the opportunity to edit the reference to appear on their statement, however the payee name will always be displayed on the fire.com PSU’s statement.

Confirmation of Funds

fire.com’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.com currently do not provide the event notification API.

Queries

If you have any queries regarding the fire.com Dedicated API, please get in touch by email at tpp@fire.com.