Most gateways rent you a revenue stream. SurePay sells you one — with the source code, the merchants and the data in your hands.
We sell you one. Same merchants, same processors — a fundamentally different position on your balance sheet.
The usual deal
The SurePay deal
The gateway is an asset purchase, not a subscription. The financing plan is what makes that reachable for an ISO or ISV.
Your portfolio, processor mix and pricing programs. We come back with the shape of a deployment.
Purchase terms and the financing structure, sized against your book rather than a list price.
API docs, sandbox credentials and a first group of pilot merchants on your own branding.
Terminals and merchants move in waves, with the old gateway live until each wave is settled.
Terms are set against the size and mix of your portfolio rather than a list price, so they are covered on the scoping call. Nothing is signed before you have run your own merchants through the sandbox.
Pricing programs are how your merchants compete. All three run card-present and card-not-present.
A fee added to credit transactions, with BIN validation so it never lands on a debit card.
A lower posted price for cash. Runs on terminals, hosted pages and invoices.
Card price and cash price shown side by side, so the choice sits with the cardholder.
Whichever program runs, the fee and any tip are itemized on screen before the cardholder confirms.
Merchant counts, processing volume and customer references are available under NDA on a scoping call.
If yours is not here, ask it on the scoping call — or email it and we will answer in writing.
A license to the SurePay gateway with the source code, deployed on infrastructure you control. Not a reseller agreement and not an API key against someone else's platform — the merchants, the data and the recurring revenue sit with you.
The gateway is purchased outright, with terms sized for an ISO or ISV balance sheet rather than an enterprise one. Exact structure depends on portfolio size, so it is covered on the scoping call rather than published here.
No. SurePay is certified on TransIT, Omaha/North and Paya/Nuvei, and the choice is made per merchant. Most portfolios keep their existing processing relationships and change only the gateway underneath.
You do, on the Azure reference architecture we ship — multi-region, geo-replicated, WAF at the edge. If you would rather not staff for it, monitoring and maintenance is available as an optional service.
The platform is PCI Level 1 compliant. Hosted payment pages, payment buttons and browser-side tokenization keep card data off your merchants' systems, which is what keeps their scope small.
Yes, end to end — the portal, hosted pages, payment buttons, invoices and both mobile apps, including the support details a merchant sees inside the app.
It depends on portfolio size and how many terminals are in the field. The scoping call produces a real sequence: sandbox, pilot merchants, then estate migration in waves.
The TSYS Sierra processing platform, targeted Q4 2026. Beyond that, the roadmap becomes yours — you own the source.
A scoping call covers your portfolio, processor mix and pricing programs. You leave knowing what ownership would cost you.