CBI Globe Gateway

The CBI Globe Gateway allows Italian institutions and other entities to expose their APIs in conformance with the PSD2 directive. Yapily has integrated with the CBI Globe Gateway to allow third parties to connect with Italian institutions.


Yapily is connected to following Italian institutions through CBI Globe:

  • Banca Nazionale del Lavoro S.p.A. (BNL)
  • Banca Popolare dell Alto Adige Personal
  • Banca Popolare dell Alto Adige Corporate
  • Banco BPM S.p.A
  • Banco di Sardegna S.p.A.
  • Banca Monte dei Paschi Business
  • Banca Monte dei Paschi Personal
  • Hello Bank!
  • Intesa Sanpaolo S.p.A
  • Posta Italiane (BancoPosta)
  • Unione di Banche Italiane S.p.A. (UBI Banca)
  • Widiba

New CBI Globe flow

We deprecated our old CBI Globe flows on 10th May 2022.

Our new CBI Globe flows have simplified both the AIS and PIS flows.

Financial data

Our old CBI Globe AIS flow required a consent for getting account details and a separate consent for getting balances and transactions, using those account details.

With the new AIS flow, you can obtain account details, balances and transactions consent via a single consent. This is more like the single redirect flow as used by Commerzbank, Unicredit, Fineco etc.

There is a limitation that customers can only call GET /accounts once per consent. Customers should store the account id to be able to GET /balances and GET /transactions.

AIS authorisation flow

Financial data can be accessed by following our standard single redirect flow, although keep in mind that you can call GET /accounts only once per consent so consider storing account details.



Our old CBI Globe PIS flow used a double redirect method, which could be unreliable when used with the CBI Globe API.

The new PIS flow involves obtaining a one-time pre-authorisation consent for a PSU. This consent can be used multiple times (with no expiry) for that PSU to initiate payments. The pre-authorisation also involves initiating a payment - for security purposes - that will never be completed (therefore never charged to the payer).

Customers should use a static IBAN and a small amount (€0.01) for this pre-authorisation payment. Once pre-authorisation is obtained, customers can initiate a real payment through to completion.

PIS pre-authorisation flow (once per user)

Initiate pre-authorisation flow illustrated below once per user to receive a permanent consentToken. The consent will stay under PRE_AUTHORIZED status and can be used multiple times to initiate payments, therefore, consider saving consentToken for future payments.


PIS authorisation flow (initiating payment for existing user)

If you already have a consentToken from the pre-authorisation step, you can initiate a payment by following the diagram below.


PIS authorisation flow (full payment intiation)

The diagram illustrates full payment authorisation flow if you don't have PRE_AUTHORIZED consent from the user.