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.

Automatic name verification before you take payment.

Account Name Verification confirms whether the cardholder's name matches the issuer record before processing. A simple identity check that strengthens trust and safety for your business and customers.

Speak with our sales team

How account name verification works

Account Name Verification supports Visa and Mastercard, works with both PAN and token inputs, and returns clear results on matches, partial matches, no matches, or unable to validate. It adds an identity check without impacting the customer and helps flag transactions that do not align with issuer records.

01

Customer enters card details

02

Merchant sends name verification request (no dollar amount required)

03

Issuer checks name against records

04

Match result returned

05

Merchant decides next step

More confidence in transactions accepted

Detect mismatched names early

Spot issues before processing payments and reduce bad transactions tied to impersonation or misuse

Cleaner customer data

Ensure stored details align with issuer records for more accurate customer profiles

Reduce losses

Lower losses tied to impersonation or misuse of card credentials

Strengthen trust

A simple safeguard that strengthens trust across your payment operations

Works with your existing stack

Supports Visa and Mastercard
Works with both PAN and token inputs
Returns match, partial match, no match, or unable to validate
No customer-facing disruption – check runs silently before payment

Add a name check to every payment.

Our team will show you how a single check can lift confidence in every payment you accept.

Get in Touch