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.

Orchestration

Routing that adapts

PXP dynamically routes transactions based on real-time conditions, historical performance, and business rules. Static routing leads to avoidable declines and lost revenue. Smart routing keeps your approval rates high and your operations resilient.

Speak with our sales team

Traditional routing leaves performance on the table

Sending every transaction to one acquirer is not realistic at scale. Acquirer performance varies by region, time, and card type. Outages, latency, and issuer behaviour change constantly, and partial degradation happens frequently and unpredictably. Switching providers manually is slow and reactive, and limited visibility makes it hard to know when performance is shifting.

How smart routing works

Performance-based routing

Evaluates historical approval performance to select the strongest acquirer, with continuous re-evaluation every few seconds using a rolling time window

Non-sticky decisioning

Routing decisions evolve as conditions change, with controlled volume sent to alternate acquirers to maintain accurate performance comparison

Retry logic and cascades

Automatically retry transactions across alternate acquirers, preventing repeat failures through the same route

Downtime detection

Automatically removes acquirers experiencing outages or degraded service and reintroduces them once stability returns

Self-service routing rules

Configure routing logic to support your specific business requirements. This includes on-us transaction routing, least-cost debit routing, and preferences based on cost, region, or card type. Rules are managed through a self-service interface, so your team can adapt routing strategy without waiting for development cycles.

01

On-us transaction routing

02

Least-cost debit routing

03

Region and card type preferences

Stop losing revenue to static routing.

Talk to our team about adaptive routing built for your traffic, your processors, and your performance goals.

Get in Touch