The platform is the same for everyone. What changes is which modules matter first — and in what order. Nothing below is exclusive to one kind of partner.
Merchant acquisition is slow and expensive, and profitability per MID is invisible.
ISO or White-label — you own the whole merchant lifecycle, optionally under your own brand. See the responsibility split →
You manage someone else's portfolio in spreadsheets, under someone else's brand.
ISO — you sell, onboard and service — with your own pricing and your own team. See the responsibility split →
You know the businesses on your patch, but you have no system, no contract and no way to track what you are owed.
Referral or Affiliate — you own the lead, or the lead and the onboarding. We handle the contract and the installation. See the responsibility split →
You install and repair terminals, but you find out what is wrong only when the merchant phones you.
Affiliate or ISO — you take over service, and with it the part of the revenue that pays for it. See the responsibility split →
You want payments and fiscalisation inside your own product without becoming a payments company.
API — you keep your product and your customers; we run the infrastructure underneath. See the responsibility split →
You sell devices but have no software or fleet management to put on them.
ISO or API — you ship the hardware; the software and the fleet tooling come from us. See the responsibility split →
Six kinds of partner. One platform underneath.
Pick the card that matches your business — the modules and the model follow.Your merchants are not one thing either. These are the three shapes we see most often — the platform handles all of them from the same record.
Every branch runs different hardware and nobody knows what is where.
One place for every branch, device and document — and it fits in your pocket.They need a till that works, prints legally and does not stop when the internet does.
A cash register that keeps selling offline and fiscalises everything when it reconnects.They want to sell without staff at the point of sale.
An unattended checkout you can deploy and monitor remotely.Everything a merchant actually touches — the register, the terminal, the mobile app — lives on the merchant site. See the merchant stack →
Tell us how you sell or build and we will map the right model — including the commercial terms. Become a partner →
We only look at where you are visiting from — curious souls — and which of our modules you open most. We run an internal contest: the module that wins earns its product manager a cappuccino. Privacy notice
Nothing gets baked, but your choice is in our Slack. If we ever open a bakery, you will be first to know.
If you like what you find here, or find it useful, let us know. You will make our day.
It just landed in our Slack. Somewhere a product manager is now closer to a cappuccino.
Tell us who you are and a person comes back within two working days. No autoresponder, no drip campaign.
Fill in the form. A person answers, not an autoresponder.
Book a demo Tell us a bit about you and pick a time. Thirty minutes, no slide deck. Got it — now pick a time. Your details are with us and we will have read them before we meet. Choose whatever suits you. We will come back with times that suit you, within two working days.Commercial model, markets, onboarding. Ready to apply? Become a partner.
API, sandbox keys, webhooks. Integration Hub.
Cash register, terminals and the merchant app live on veslo.io.
We will come back to you within two working days.
Calendar not loading? Open it in a new tab.
You will see only free slots, in your own time zone. The invite lands in your inbox the moment you confirm — we are looking forward to it.