What integration options are available?

Technology partners can integrate through PXP's REST API, native Kotlin SDK, local HTTP REST calls, or webhook-based event flows. The integration path depends on your platform architecture and whether you're building for in-store, online, or both.

Do my merchants need separate contracts with the different acquirers?

No. PXP manages acquiring relationships. Your merchants sign with PXP, and smart routing handles which acquirer processes their transactions based on performance, geography, and card type. Merchants don't need to manage acquirer relationships directly.

How long does integration typically take?

It varies depending on complexity and which products you're integrating. PXP's technical team supports the process from scoping through testing and certification. Sandbox access is available immediately.

What are the hardware options for in-store integration?

PXP uses Castles Android-based Saturn terminals. They're acquirer-agnostic, meaning the hardware doesn't need to change if routing changes. Contract terms run from 12 to 48 months, and asset finance options are available.

How is commission structured?

Revenue share is calculated on the transaction volume your merchants process. It's tracked automatically through Launchpad and paid for the lifetime of each customer relationship. PXP does not re-paper merchants or end commission after a set period.

Time for a Level Playing Field for Regulated UK Gambling Payments

Download Whitepaper

Smarter tokenisation for secure payments.

Replace sensitive card data with secure tokens and unlock stronger performance. PXP Token Vault stores and manages tokens centrally, powering network tokenisation and enabling seamless recurring payments.

Speak with our sales team

Storing cards is necessary. Storing PAN data is not.

Customers expect to keep their cards on file, but stored card data creates long-term security risk. Keeping credentials updated is difficult and adds operational burden, and without tokenisation, risk persists beyond the initial transaction.

Tokenisation, built into the platform

PXP Token Vault exchanges PANs for gateway or network tokens, so sensitive data is never stored in your environment. It works across channels, supports safer recurring and stored credential payments, and integrates with existing PXP services or as a standalone solution.

PCI scope reduction

Sensitive card data never touches your environment

Built for recurring payments

Power one-click checkout, subscriptions, and customer profiles

Automatic lifecycle management

Keep tokens fresh with scheme updates and credential-on-file refreshes

Works across channels

Online, in-app, and in-store where supported

Gateway vs network tokens

Gateway tokens

Generated by the payment gateway and replace PANs with provider-issued tokens. Device-agnostic and useful for PCI scope reduction, but they work only within the gateway's ecosystem and have limited portability if you change providers.

Network tokens

Issued by card networks and live at the scheme level. Automatically refreshed when the card changes or credentials are reissued, work across gateways, processors, and channels, and carry higher trust from issuers with built-in risk scoring and lifecycle data. Currently supported for Visa and Mastercard.

Why network tokens deliver better performance

Issuers trust network tokens more than raw PANs, which translates to higher approval rates. Lifecycle updates reduce expired card failures. A scheme cryptogram adds another layer of security, and fewer failed payments mean fewer moments where revenue and customers slip through the cracks. Network tokens are also portable across providers, helping you avoid lock-in as you scale.

Build a token strategy that fits your business

A blended approach works well because gateway tokens provide immediate availability while network tokens provision asynchronously. Keeping both types gives you redundancy and failover, and you can use the optimal token by channel or use case. Many businesses start with gateway tokens and add network tokens over time as a natural migration path.