- payment.succeededacct_2nz1s
- customer.updatedacct_84j4s
- payment.succeededacct_19f9s
- dispute.openedacct_7px22s
- refund.createdacct_2nz41s
Problems we hear from Software ISV programs
Gateways that go around you
Vendor-led upsells, side ISO programs, or a competing platform launched into your vertical the next quarter. Every "partner" gateway has a path that quietly cuts your software out of the loop.
Bolted-on integrations
One-off gateway adapters slow every release. You need predictable patterns for tokens, webhooks, idempotency, refunds, and disputes — not a different shape on every endpoint.
Card-present as an afterthought
When your customers eventually need terminals, your gateway treats hardware as a separate product, with a separate vault and a separate report. The "embed" story breaks the day card-present matters.
Outcomes we optimize for
Built for embedding, not bolting on
REST + webhooks. Idempotency keys. Token-based vault. Component library for desktop and mobile. Sandbox you can hit in 60 seconds.
We don't go around you
Partner-only by design — we don't sign up your end users behind your back, and we don't license a competing platform to your competitor next month.
One contract covers card-present and online
When your customers eventually need terminals, we have those — same vault, same reporting, same API. You don't change vendors when card-present matters; you just turn it on.
Where teams usually start
Every product ships behind your brand. Explore details on each product page.
Tokenizer
Hosted fields and tokenization to reduce PCI scope for your application.
View productCustomer Vault
Saved methods and updater-friendly patterns for subscriptions and repeats.
View productWatchDog Fraud
Controls you can tune per merchant profile instead of one-size-fits-all scoring.
View product
Next step for Software ISV teams
Apply when you are ready for partnership review. Book a demo when you want a technical walkthrough first.