Skip to main content
Logo
API Documentation Status page Submit a request
Sign in
  1. Bank Account Data
  2. Bank Account Data Portal
  3. Account Management

Bank Account Data API Usage - how is your usage number calculated

Calculating Requisitions and Usage

What is a Requisition?

A requisition, more simply referred to as a connection, is a live link between an end user’s bank account(s) at a specific bank and your company. This connection remains active for a maximum of 90 or 180 days.

For example:

End User has the following bank accounts: 

  • Main Street Bank (user accesses both accounts through the same login credentials)
    • Current Account 
    • Savings Account 
  • Capital Bank 
    • Current Account 

This is two requisitions for three bank accounts. 

In other words, one end user authorisation (via bank's biometric/manual login) is equal to one requisition — regardless of the number of bank accounts at that bank (e.g.: current account and savings account that both have the same login credentials for the user).

Determining "Active Requisitions per Month" for Billing:

When calculating API usage for billing purposes, we consider a requisition as active if it meets the following criteria at any time during a given calendar month (in the UTC time zone):

- Status is Linked (status: LN)

- Has an active End-User Agreement (accepted and not expired)

- Not a Sandbox requisition (institution_id: SANDBOXFINANCE_SFIN000*)

- Not deleted before 00:00:00 UTC on the first day of the month

 

Multiple Requisitions for the Same Account:

If you connect the same account(s) twice through different requisitions, each connection will be counted as a separate active requisition for that month.

 

Optimising Monthly Usage Fees:

To manage your monthly usage fees effectively, we recommend evaluating the required validity period for each requisition (depending on your use case) and deleting any unnecessary requisitions before the start of the upcoming calendar month. You can use the following endpoint to delete requisitions:

DELETE​ /api​/v2​/requisitions​/{id}​/

 

For example, if you delete a requisition during April that would have been valid in May, it will still be counted towards your April usage but not for May.

Was this article helpful?
  • Promoted articles

    • Bank Account Data API Usage - how is your usage number calculated
    • EEA 180-day access
    • Bank Account Data API Rate Limits
    • How to recognise and handle end user authentication errors
    • Account Endpoint Errors and Suspended Accounts
  • Recently Added Articles

  • Top Articles

Bank Account Data Quickstart Guide

Simple and streamlined guide to start using our Bank Accoun Data API

Quickstart Guide

Demo page of our Bank Account Data API

See the product in action with few easy clicks

Bank Account Data Demo

Need Support?

Contact us

We're available Monday to Friday, 9am-5pm GMT

Quick links

Knowledge base
Gocardless Bank Account Data

About GoCardless

Legal
Privacy
Security
Blog

Support

Contact support
Complaints
Contact sales

API Documentation

Developer documents

GoCardless Ltd, Sutton Yard, 65 Goswell Road, London, EC1V 7EN, United Kingdom


GoCardless Ltd (company registration number 07495895) is authorised by the Financial Conduct Authority under the Payment Services Regulations 2017, registration number 597190, for the provision of payment services.





https://docs.google.com/spreadsheets/d/1EZ5n7QDGaRIot5M86dwqd5UFSGEDTeTRzEq3D9uEDkM/edit?gid=976380583#gid=976380583
/hc/theming_assets/01JVYEMDH4NW2KMNM8HG9Y2GXA
Detailed bank coverage
A detailed list of the available institutions and specifications.
custom
https://gocardless.com/stories/bondora/
/hc/theming_assets/01JKWXK6T8QZWQQSYYJAD0X703
Our latest customer story
Learn about how companies are using our technology.
custom
https://developer.gocardless.com/bank-account-data/overview
/hc/theming_assets/01JVYEMQ0208DBSNG2GPZRZ36T
Developer Docs
All the documentation you need to integrate with our API.
Rate Limits, Access expired, Requisition