Yapily review: open banking API, products, coverage (2026)

Yapily is an open banking infrastructure company that gives businesses a single REST API for two things: initiating account-to-account payments and reading bank account data, across the UK and a group of European markets. Its distinctive offer is Yapily Connect, a model in which the customer relies on Yapily's own regulated entities rather than applying for third-party provider status itself.

The company describes its role as connectivity rather than money handling: it does not hold, process or settle client funds. Its customers include payment providers, platforms and fintechs that embed bank payments and data into their own products. For background on how these flows work, see our guide to open banking payments.

At a glance

How the platform works

Yapily sits between a customer's application and the banks' open banking interfaces. In the UK there is one dominant technical standard that most large banks follow closely. In Europe there are several (the company names Berlin Group and STET as examples), each with differences in required fields and authentication flows. Yapily says it normalises these into one API, though some country-specific differences still show up in requests.

The consent flow follows the usual open banking pattern, as described in the company's documentation:

1. The customer's application asks Yapily to create a consent request.
2. The end user is sent to their own bank and authenticates with strong customer authentication.
3. The bank returns the user with an authorisation code.
4. The application exchanges that code for a consent token.
5. The token is used either to read data or to execute a payment.

Payment consent is single use, so one payment is executed and then monitored. Data consent is longer lived: Yapily states up to 90 days in the UK and up to 180 days in the EEA. Because payments move directly between bank accounts, Yapily notes there is no card network involved, and so no interchange fee or chargeback mechanism of the card type. Our real-time payments guide covers the instant rails that many of these payments use.

The API is REST-based and uses HTTP Basic Authentication, according to the documentation overview page. Yapily Console is the web tool for creating applications, collecting credentials and browsing supported institutions.

Hosted Pages or Direct API

Customers choose one of two integration routes, and can combine them.

The documentation says Hosted Pages cover data as well, in the payments countries plus Sweden, Norway, Denmark and Ireland. Yapily suggests most customers begin with Hosted Pages and add Direct API calls later. Some documentation pages still label Hosted Pages as beta, while the changelog records ongoing expansion, so access terms are worth confirming with Yapily.

Products

Payments

Yapily Payments covers single, scheduled and periodic account-to-account payments across the UK and Europe. A separate bulk payments product sends one batch from a single account to many recipients, with individual payment status tracking added in May 2026 according to the changelog. The documentation overview marks bulk payments as beta.

Variable Recurring Payments

Variable Recurring Payments (VRP) let a customer authorise a mandate once and then collect varying amounts later without a fresh approval each time. The documentation distinguishes sweeping VRP from commercial VRP. The changelog says commercial VRP launched for approved UK use cases in May 2026, and that Barclays and Nationwide were added to commercial VRP coverage for UK personal current accounts in July 2026.

Data, Data Plus and Validate

The Data product retrieves accounts, balances and transactions. Data Plus adds categorisation and enrichment, and the August 2026 changelog entry records a Categorisation Feedback API. Validate confirms customer details and account ownership from basic account information, and is positioned for onboarding. In October 2025 Yapily announced a bank account verification service for Google, and a later post extends it to Google Cloud customers in 11 European markets, with Yapily stating it connects to more than 2,000 banks in 19 UK and European markets.

Yapily Connect

Yapily Connect is the licensing model. Under it, Yapily's regulated entity acts as the account information and payment initiation provider on the customer's behalf, so the customer does not need its own authorisation. The documentation says teams can go live in days this way, against months when holding their own licence. Either way, registration with each bank is still required, and most institutions are already registered under Yapily Connect.

Pay By Link and virtual accounts

Pay By Link generates a reusable payment request link for a fixed amount that can be sent by email or SMS, with Hosted Pages completing the payment. The documentation overview also lists Virtual Accounts (beta) for multi-currency collections and payouts, but we did not find a dedicated documentation section for it in the published index, so treat availability as unconfirmed.

Developer experience and integrations

The documentation covers tutorials for single payments, bulk payments, VRP and data, plus guidance on consent lifecycles, webhooks, payment status, error handling and a changelog. Webhooks are documented, including payment webhooks for Hosted Pages, and a migration guide covers moving from the older Notification API to the Webhook API.

On SDKs, the index lists "Client Libraries" as a section about generating API clients from the OpenAPI specification rather than a set of maintained packages, so the company's own wording is the safer guide here.

Sandbox access comes in several forms. Preconfigured sandboxes need no registration and use Yapily's credentials. Non-preconfigured sandboxes need certificates and bank-specific credentials. There is a Yapily Mock sandbox and a regulator-provided Modelo (Ozone) sandbox. The documentation warns that sandbox data may not behave like live banks, for example payments may complete immediately. A Yapily Demo App (beta) lets developers test with real bank credentials.

Named customers on the homepage include Adyen, Intuit QuickBooks, Revolut, Google, Allica Bank, Alipay+, Payhawk, Pleo, SumUp, Yonder, Crezco and Moneyfarm. Logos on a homepage do not describe the scope of each relationship.

Payment methods, currencies and coverage

Yapily's products described on the pages we opened are all bank-based; none cover cards or wallets. The homepage states 2,000 institutions in 19 countries, with most banks in the UK and Germany (checked 3 November 2026). A documentation overview page gives a slightly lower figure of over 1,900 institutions, so figures differ between pages. Payment types named in the documentation include domestic payments, SEPA and SEPA Instant.

Recent changelog entries show how coverage grows in small steps:

Comparable providers include Token.io, TrueLayer and Tink; see the Tink vs Yapily comparison.

Pricing model

Yapily did not publish a price list on the pages we could open on 3 November 2026. Pricing is not published on the company website as of that date, and customers should expect to agree terms directly. The documentation does describe how cost structure differs by licensing route: Yapily Connect shortens set-up time, while holding your own licence puts compliance on the customer. Yapily also lists registration management as an add-on for customers with their own licence.

Recent launches

Regulation in brief

Yapily's compliance pages state that Yapily Ltd, the parent, is not itself regulated and does not provide regulated services. Yapily Connect Ltd is stated to be regulated by the Financial Conduct Authority in the UK, and Yapily Connect UAB by the Bank of Lithuania for the EU. Both are described as fully owned subsidiaries. These statements come from company pages dated March and October 2025; check the FCA register and our guide on how to check a financial licence for current status.

Who it tends to suit

Yapily is commonly used by payment providers, fintechs and platforms that want bank payments and account data from one API across several European markets, and by teams that prefer to operate under a provider's authorisation. Businesses with a single-country need or a data-only focus may also look at Plaid or TrueLayer. The open banking hub lists related profiles.