Skip to main content
Access to bank APIs under open banking regulation is restricted to licensed Third Party Providers (TPPs). This regulatory framework ensures secure, authorised access to financial data and payment initiation. There are two types: AISP (Account Information Service Provider) for accessing account data, and PISP (Payment Initiation Service Provider) for initiating payments. Once licensed, you must also register with each bank you want to connect to. This is a regulatory requirement, not a Yapily limitation. Yapily offers two licensing paths: use Yapily Connect (where Yapily holds the licence and manages registrations on your behalf) or bring your own TPP licence and manage registrations yourself. Both paths use the same underlying API infrastructure, so your integration approach does not need to change. This also applies regardless of whether you use Hosted Pages or the Direct API. Licensing and registration are prerequisites for all open banking access.

Your licensing options

Yapily Connect (Recommended for most)Own TPP Licence
Who holds the licenceYapilyYou
Regulatory responsibilityYapily manages complianceYou manage compliance
Time to go liveDays (use Yapily’s existing registrations)Months (apply for licence, register with banks)
Bank registrationsYapily manages registrations across 2000+ institutionsYou manage registrations yourself, or use Yapily’s registration management add-on
Best forCompanies wanting to launch quickly without regulatory overheadRegulated entities (banks, e-money institutions) who already hold or are obtaining a licence
Consent brandingYapily appears as the TPP on bank consent screensYour company appears as the TPP
Works withHosted Pages and Direct APIHosted Pages and Direct API
Most Yapily customers use Yapily Connect. It removes the regulatory overhead so you can start integrating faster. You can always transition to your own licence later if your needs change.
For full details on the managed licensing service, see Yapily Connect documentation.

Bank registration

Even with a TPP licence (your own or via Yapily Connect), you must be registered with each specific bank before you can access it through Yapily. Without it, the bank will reject API requests.

If you are using Yapily Connect

Yapily maintains registrations across its network of 2000+ institutions. For most institutions, registration is already in place. For institutions that need additional registration, request it through the Console, where you can also check status for any institution.

If you are using your own licence

You must register with each institution individually. This can take days to weeks depending on the bank and country. Yapily also offers a registration management add-on. Contact our team to enable this service. You can also manage registrations yourself. See the Registrations documentation for detailed guidance.
You can check registration status for any institution in the Yapily Console. Attempting to access an unregistered institution will return an error.

Before you start building

1

Choose your licensing path

Yapily Connect for speed and simplicity, or your own licence if you are already regulated or need your branding on consent screens. See the comparison above.
2

Check your registrations

Log into the Console and verify you are registered with the institutions you need. For Yapily Connect customers, most institutions are pre-registered.
3

Understand your institution coverage

Not all institutions support all features or payment types. Use the Console or GET /institutions to check capabilities for the banks you plan to support.
4

Choose your integration approach

Once licensing and registration are in place, decide between Hosted Pages and the Direct API.
Registration is a prerequisite, not a one-time task. When expanding to new countries or institutions, check registration status first. API calls to unregistered institutions will fail.

Next steps