Who Yapily is
Yapily is an open banking infrastructure company founded in London in 2017. One API connects to banks across the UK and Europe for payments, from single and scheduled payments to bulk and variable recurring ones, and for account data, account validation and Verification of Payee.
Yapily Connect Ltd is regulated by the UK's Financial Conduct Authority and Yapily Connect UAB by the Bank of Lithuania, so a business without its own licence can work under Yapily's. Payment companies, banks and e-money institutions, lenders and accounting platforms use it, which is why it is one of the open banking providers our modules connect to.
What it does in your platform
Accounts & IBANs
Connects accounts your customers hold at other banks. With their consent, Yapily shares balances and transactions, confirms the account is theirs, and starts the payment that tops up their account in your app.
Checkout
Adds bank payments to the checkout. Yapily's API leaves the bank list and consent screens to the checkout, so they look like the rest of it, and the order follows the payment's status.
How the connection works
One connector talks to Yapily's API. Yapily handles the bank connections; the module draws the screens, keeps the consents and listens for Yapily's webhooks.
The buyer picks a bank
The checkout lists the banks Yapily supports in the buyer's country, and the buyer picks theirs.
An authorisation is requested
The module asks Yapily for a payment authorisation with the amount and the merchant's account, and gets back a link to the bank.
Consent at the bank
The buyer approves the payment at their bank and is sent back to the checkout, which receives a consent token.
The payment is created
With the consent token, the module creates the payment, which goes over the local rail, such as Faster Payments or SEPA.
The status comes back
Yapily's webhooks, signed with a secret the platform holds, report the status. The order is marked paid, and the payment shows in the backoffice.
Next to other providers
Yapily can run next to Tink, TrueLayer or local methods such as iDEAL, with the checkout routing bank payments between them, for example by country, while merchants keep the same integration.
Because the screens and consents belong to the module, adding a provider next to Yapily, or moving away from it later, changes a connector, not your app.
When Yapily fits best
A strong fit when
- You want the bank payment screens to look like the rest of your product.
- You need payments and account data across the UK and Europe from one API.
- You need bulk or variable recurring payments as well as single ones.
Also worth a look
- A provider with a ready-made payment page, if you would rather not own those screens.
- A provider you already have a contract with: it becomes a connector too.
How we get you live
The contract
We help you get your Yapily account and contract in place, under your own licence or through Yapily Connect.
The banks
We set up the banks and countries you need with you, and the registration each bank asks for.
The keys
The application credentials and the webhook secret go into your platform's secrets and nowhere else, so every event is proven to come from Yapily.
A full test run
The whole flow runs in Yapily's sandbox with its test banks, from bank choice to webhook, before your first real customer.
