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
Rule of thumb:
Building for terminals / POS: start with Cloud EMV.
Building mobile in-person payments: use Mobile EMV SDK.
Building web checkout: use the 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 email).
Want lower-cost bank payments: use ACH Transactions.
Card-present options are device-specific:
Cloud EMV supports selected terminals (for example, PAX and Dejavoo).
Mobile EMV SDK uses the ID TECH VP3300 reader.
Comparison Matrix
In-person (card-present)
POS platforms supporting multiple terminals
REST API
Yes (supported terminals)
In-person (card-present)
Mobile apps that want embedded payments
iOS/Android SDK + Mobile Payments API
Yes (VP3300 via Bluetooth)
Online (card-not-present)
Hosted checkout + wallet support with reduced PCI scope
JS SDK + backend token submission
No (optional readers supported)
Bank payments
Lower-cost payments and bank-based recurring
API (also supported via JS SDK / PayLink)
No
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.
Last updated
Was this helpful?

