Skip to main content
Yapily offers two integration approaches built on the same underlying API infrastructure: Hosted Pages, a pre-built web flow, and the Direct API, where you build your own UI with full control over the experience. For most customers, especially those getting started, Hosted Pages is the fastest and lowest-friction way to integrate. It handles the most complex parts of open banking (bank selection, user authorisation, Strong Customer Authentication) so you can focus on your product.
Both integration approaches require licensing and bank registration. See Licensing & Registration if you have not set this up yet.

​
Quick comparison

​
When to choose Hosted Pages

Choose Hosted Pages when:
  • You want to accept payments or obtain data consent and need to go live quickly
  • You do not have frontend engineering resource to build authorisation flows
  • You are building an MVP or testing open banking for the first time
  • Your use case is single payments, VRP, or data access in supported Hosted Pages countries
  • You want Yapily to handle the complexity of bank selection, redirects, SCA, and consent management

​
How Hosted works for each use case

For payments: Hosted manages the entire flow. You create a payment request, receive a URL, redirect your user, and the payment is executed once the user authorises. You receive webhooks on payment status changes. For data access: Hosted manages the consent and authorisation flow. Once the user authorises, you receive a consent token. You then use this token with the Yapily API to call data endpoints: accounts, balances, transactions, and Data+ enrichment.
Hosted Pages is also the safer option for teams new to open banking. It handles SCA edge cases, bank-specific error responses, and auth flow differences across institutions, so you avoid building and maintaining that logic yourself.
Learn more:

​
When to choose the Direct API

Choose the Direct API when:
  • You need payment types not yet supported by Hosted Pages (bulk, scheduled, periodic, international)
  • You are operating in countries not yet covered by Hosted Pages
  • You need full control over the user experience and want to build a custom UI
  • You are building a native mobile app (Hosted Pages is a web redirect experience)
  • You have complex requirements such as multi-bank consent management or custom retry logic
Both approaches can be combined within the same product. For example, use Hosted Pages for standard payment collection and data consent, then use the Direct API for specialised payment types or additional data processing.
Learn more:

​
Feature availability

Hosted Pages coverage is expanding. Check the Hosted Pages documentation for the latest supported countries and features.

​
Which approach fits your situation?

​
Next steps

Get started: