Built to be extended, not just used
The same operating layer that runs merchant lifecycle, orchestration, and portfolio operations is open to the technology partners, ISVs, and POS providers building around it — through APIs, not a parallel system. What they build becomes something you can offer, not something you have to build.
Every role in the ecosystem gets its own door in
The platform isn't built for merchants alone, and it isn't built for ISOs alone. Different participants need different access — structured so each one gets exactly the capability their role calls for.
ISOs & FSPs
Revenue operations and portfolio tools built against the same ledger that already powers residuals and reporting — extending what your own team, or a technology partner working with you, can put in front of agents and sub-ISOs.
Merchants
Commerce and front-office tools — POS overlays, accounting sync, loyalty, invoicing — sold and supported by you. Merchants get the capability; you keep the account.
Sponsor Banks & Acquirers
Compliance and governance visibility into the programs you sponsor, without asking every ISO for a different report in a different format.
Technology Partners & Developers
Build once against the platform's APIs, and reach every ISO running on it — the entry point for ISVs, POS providers, and software partners.
The same APIs already running orchestration, commerce, and enterprise infrastructure
REST APIs and SDKs aren't a separate product bolted onto the platform — they're the same interface every solution here is built on, opened up for technology partners to build against.
- REST APIs and SDKs across onboarding, orchestration, commerce, and reporting
- Webhooks for real-time event delivery
- Tokenized data access — partners integrate against payment references, never raw card data
- App marketplace distribution — connect an integration once, make it available across the ISOs running the platform
For your organization, that means the software your merchants already expect — invoicing, loyalty, vertical POS, accounting sync — can arrive from a technology partner already connected to the same ledger, instead of a build request on your own roadmap. For a technology partner, it means API and data access to real merchant activity — underwriting signals, transaction history, portfolio structure — to build a richer product without becoming a payments company to do it.
Merchant Commerce & Embedded PaymentsA sandbox before a sales call
Technology partners can start building immediately — a self-service sandbox, full documentation, and a defined path from first integration to a live listing.
- Self-service developer sandbox — start building without a sales cycle
- Full API and webhook documentation, alongside SDKs for common platforms
- A structured review path — security, data handling, API conduct — before anything reaches a live merchant
- Once approved, available to every ISO running the platform
The apps and integrations that come out of this become part of what you can offer — not one more thing your team has to build, secure, and maintain.
Building something, or want something built?
If you're a technology partner, ISV, or POS provider building on the platform, request sandbox access directly. An ISO who wants a specific integration in front of merchants can talk with our team directly.
Connected across the acquiring, processing, and software ecosystem
