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

3D Secure

Authentication that adapts to risk.

3D Secure transforms payment security from a regulatory necessity into a competitive advantage. PXP gives you flexible ways to connect, with the scale and compliance built in, so authentication doesn’t slow you down.

Speak with our sales team

The 3DS challenge

Online payments require layers of protection, but security often comes at a cost to conversion.

For merchants

Murky liability rules and exemption management

Technical complexity of integration

False declines and poor authentication UX

For customers

Disrupted checkout flows and inconsistent experiences

Limited accessibility and app-switching confusion

Unnecessary friction that drives abandonment

Where 3DS creates friction, PXP removes it

PXP applies 3DS as part of a flexible authentication framework. Pre-authentication evaluates a card before authorisation, determines whether PSD2 applies, identifies available exemptions, and applies business rules to decide the best response. Options include authenticate with or without challenge, data-share only, apply exemption, or skip authentication entirely.

Security fit for your workflows

PXP offers two integration modes to fit different architectures.

Integrated

PXP handles both authentication and authorisation. Best for merchants who want to minimise and outsource risk, or who use PXP acquiring.

Both modes support full 3DS flows, challenge handling, SCA compliance, and fallback logic for declines.

Standalone

PXP authenticates, and authorisation follows your established payment route. Best for merchants who want full control over their payment routing and setup.

Both modes support full 3DS flows, challenge handling, SCA compliance, and fallback logic for declines.

Configurability

Customisable authentication flows that adapt to your needs. PXP supports 3DS 2.x protocols, reducing reliance on static passwords. Mobile-optimised and biometric-capable authentication flows are built in. Intelligent step-up triggers only when necessary to reduce unnecessary friction, and the authentication iframe is fully customisable including window size and placement.

3DS 2.3

3DS 2.3 builds on the existing 3DS framework to improve usability, consistency, and future readiness. Expanded authentication options support additional methods based on issuer preferences. Richer data exchange improves issuer confidence without increasing customer effort, and reduced consumer friction comes from better assessment of when authentication is truly needed.

Built for compliance and scale

Compliance

Fully compliant with PSD2 Strong Customer Authentication (SCA)
Automatically updated for evolving global 3DS regulations
Reduces merchant liability for fraud disputes through strong authentication
Helps ensure exemption support for TRA and low-risk transactions

Scalability

Built for high-volume environments and optimised for latency-sensitive authorisations
High authentication success rates from smart retry and fallback strategies
Developer-friendly APIs and SDKs support seamless integration