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

Online

PXP Components

Custom checkout builds for better buying experiences. Flexible, modular card-entry widgets that give you complete control over the checkout experience while keeping sensitive data out of scope.

Speak with our sales team Try online demo

Make checkout seamless

Rigid hosted checkouts, missing payment methods, and clunky multi-step flows don't just frustrate customers, they cost you conversions. PXP Components enable modular, customisable payment elements that embed directly into your checkout.

Reduce friction, support local payment methods, and deliver a consistent experience across every device, without the development overhead.

Card components, built for secure acceptance

Each component is fully customisable for different styles, texts, translations, and more. Embed individual fields or grouped card-entry forms directly into your page, and control exactly how they look and behave.

PXP Components capture card data securely and can be used for tokenisation, 3DS, and transaction processing. Secure card data fields use iframe isolation and client-side encryption, and are designed to reduce PCI scope and standardise the experience across your checkout.

Components can be used for:

Tokenisation only
3DS authentication only
Full transaction processing

Security without fragmentation

Accepting cards without PCI burden often means giving up control. Segmenting sensitive PAN data often redirects to an unbranded page, checkout experiences stop matching the site, customers question the legitimacy of a new web page, and businesses end up choosing between strong security and a consistent experience.

PXP Components solve this by keeping the secure fields embedded natively in your checkout. The experience stays branded and consistent, while card data never touches your servers.