Payment Processing

Payment processing is how your merchants accept and authorize card and bank payments on Xplor Pay.

Pick the integration based on channel (in-person, web, recurring, ACH) and UX control.

Pick a Payment Integration

Cloud EMV

Card-present for POS and terminals (unified API).

Learn more

Mobile EMV SDK

In-app card-present for iOS/Android (Bluetooth reader).

Learn more

Tap to Pay on iPhone

In-app contactless payments on iPhone without a separate reader.

Learn more

JavaScript SDK

Web checkout with hosted iframe + wallets.

Learn more

Recurring Payments

Stored payment methods + scheduled billing.

Learn more

Paylink

Payment links using SMS or e-mail.

Learn more

ACH Transactions

Bank payments with tokenization.

Learn more

Payment UI

A ready-to-use interface for handling card payments.

Learn more

Rule of thumb:

• Building for terminals / POS: start with Cloud EMV.
• Building mobile in-person payments: use Mobile EMV SDK.
• Building web checkout: use JavaScript SDK.
• Charging on a schedule: use Recurring Payments (needs a stored payment method).
• Requesting payment via a payment link: use Paylink (send link by SMS or e-mail).
• Want lower-cost bank payments: use ACH Transactions.
• Manage card payments in your iOS app: use Paylink UI.

Card-present options are device-specific:

• Cloud EMV SDK supports selected terminals (PAX and Dejavoo).
• Mobile EMV SDK uses the ID TECH VP3300 card reader.

Comparison matrix

Solution	Channel	Best for	Integration type	Hardware required
Cloud EMV	In-person (card-present)	POS platforms supporting multiple terminals	REST API	Yes (supported terminals)
Mobile EMV SDK	In-person (card-present)	Mobile apps that want embedded payments	iOS/Android SDK + Mobile Payments API	Yes (VP3300 via Bluetooth)
Tap to Pay on iPhone	In-person (card-present)	iPhone apps that want contactless payments without external hardware	iOS SDK + Mobile Payments API	No
JavaScript SDK	Online (card-not-present)	Hosted checkout + wallet support with reduced PCI scope	JavaScript SDK + backend token submission	No (optional readers supported)
Recurring Payments	Scheduled billing	Subscriptions, installments, maintenance plans	API	No
Paylink	Online (card-not-present)	Link-based payments via SMS or e-mail.	API	No
ACH Transactions	Bank payments	Lower-cost payments and bank-based recurring	API (also supported via JavaScript SDK / PayLink)	No
Payment UI	In-person (card-present)	A ready-to-use interface for handling card payments.	iOS SDK + Mobile Payments API	Yes (VP3300 via Bluetooth)

Next step

If you haven’t onboarded merchants yet, start with Merchant Onboarding.

Once you’re processing payments, you’ll usually want Reporting and Financial Management next.

Need help?

Tell us your channel (POS, mobile, web) and devices. We’ll recommend the fastest path with the lowest compliance overhead.

Get in touch