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

Orchestration

One connection for seamless payment orchestration

PXP brings providers together through a single orchestration layer. Complexity is absorbed by the platform, not your teams. Scale across acquirers, channels, and markets without lock-in.

View smart routing

Built for routing at scale

Initial routing logic validates merchant configuration and determines whether a transaction can proceed. This includes confirming supported card types for the merchant and site, restricting on funding source (credit, debit, prepaid) and product type (consumer, corporate), and applying card-type restrictions. Every transaction is aligned with your configured acceptance rules before it moves forward.

Risk screening and fraud control

Not every transaction carries the same risk, value, or context, and your payment flow should reflect that. PXP gives you the tools to design, automate, and adapt transaction flows in real time.

Self-service flow control

Configure screening logic visually and adjust rules without redeploying code

Built-in and external screening

Velocity checks, whitelists, blacklists, and pattern-based risk signals, with external screening powered by Kount

Verification and step-up

Account name verification, AVS and CVV checks, and the ability to step up to 3DS when required

Outcome-based actions

Approve, decline, reroute, or send to manual review, with auto-revert as new signals arrive

Smart routing

PXP dynamically routes transactions based on real-time conditions, historical performance, and business rules. Performance-based routing evaluates historical approval data to select the strongest acquirer, with continuous re-evaluation every few seconds using a rolling time window. Retry logic and cascades automatically retry transactions across alternate acquirers. Downtime detection removes acquirers experiencing outages and reintroduces them once stability returns.

Authorisation processing

Authentication alone does not guarantee approval. PXP processes authorisation using the context built earlier in the payment journey. Transactions are routed to the most appropriate acquirer, with consistent handling across providers and channels. Authorisation follows screening and authentication decisions, with support for retries or alternate paths where appropriate.

Recovery and retries

Not every decline is final. Issuers return soft declines for many reasons, and without recovery logic, transactions stop too early. PXP supports recovery and retries as part of the orchestration flow, identifying when a decline is recoverable, retrying using updated context or alternate paths, triggering step-up actions when required, and avoiding unnecessary retries that increase cost or risk.

01

Issuer soft decline

Trigger 3DS step-up (if permitted) or submit new authorisation attempt

02

Acquirer decline

Route to next-best acquirer and resend authorisation

03

Non-recoverable decline

Stop the transaction (lost/stolen, NSF, etc.)

Built for resilience

Single-path tokenisation creates hidden risk. Token availability is often tied to one provider, and acquirer outages can break stored payments. PXP solves this with redundant tokenisation across acquirers, handled in parallel. Cards are tokenised across multiple acquirers simultaneously, token IDs are returned asynchronously as they become available, and tokens are centrally managed within Token Vault.

Ready to orchestrate your payments?

Get in touch to see how one integration can replace the complexity of managing multiple payment providers.

Get in Touch