One contract for the whole payments problem.
Every method your customers want to use, one place the money lands, and one way to send it back out. Instead of a PSP for cards, somebody else for the market where nobody uses cards, and a spreadsheet to make the two agree.
Three things move when the pieces become one platform.
Not a migration — Banky can sit alongside whatever you take today. These are the differences on the payments that come through it.
What you sign
A contract per provider: one for cards, another for the local method in the market where cards are not what people use, a bank for the payouts.
One contract, covering every method you enable and the account the money lands in.
What you build
An integration per provider, each with its own quirks, and a layer of your own on top to decide which one gets each payment.
One REST API. Which methods a customer sees is configuration, set per country, not code you maintain.
What happens at month end
Each provider settles into its own account, on its own schedule, in whatever currency it chose. Reconciliation is a job somebody does on Mondays.
Every method settles into the same multi-currency account. One balance, one history, one export.
Two ways to take the money.
Does the payment go straight to your bank account, or does Banky hold it and settle to you? Both are live, and the choice changes what refunds, payouts and settlement each mean for you.
Straight to your bank account
- Purchase
- Merchant
Banky initiates a payment from the payer's bank account to your bank account. The money goes where it was always going and Banky never holds it.
Pick this if: You want the shortest path between your customer and your account, you already have a way to issue refunds, and you would rather not have a third party sitting on your balance.
Held by Banky, settled to you
- Purchase
- Banky
- Merchant
Banky initiates payments from the payer's account, then securely holds the funds before settling them to your account. Payouts, settlements and refunds are fully supported.
Pick this if: You need refunds and payouts to go out through the same channel the money came in, you want settlement on a schedule you agreed rather than transfer by transfer, or you want one place to see the balance.
| Straight to your bank account | Held by Banky, settled to you | |
|---|---|---|
| Where funds land | Your own bank account | A Banky merchant account |
| Who holds the money | Nobody but you | Banky, until settlement |
| Settlement | Bank to bank, as each payment clears | On a schedule, as requested and agreed |
| Refunds and payouts | Yours to make, from your own account | Through the API or the merchant portal |
| Merchant portal | — | Balance, payment history, account management |
| Changing the recipient account | Ask us to set it, or send it on the API request | In the merchant portal |
On that last row: There is a setting that allows or disallows overwriting the saved recipient account. If overwrite is disallowed and a payment request still includes a recipient account, the request errors.
What you need before the first payment.
- An officially registered company, onboarded and verified by our team
- A finalised agreement with us
- An integration to our API
- An active bank account
How onboarding works
You can become a merchant, eligible to use Banky, if you are an officially registered company, which gets successfully onboarded and verified by our team. We would require documents related to your business and the company's ownership through the onboarding process, to approve your application and eligibility to use our services.
What it costs
Pricing is set per merchant — by volume, by sector and by the markets you sell into. There is no public rate card, and we would rather tell you a real number for your business than a headline one that turns out not to apply to it.