Understanding Integration
Use an API-driven workflow to onboard new merchants. This automated process streamlines the workflow from application submission to equipment activation, helping merchants get started quickly.
The following image and step-by-step guide outline the integration flow:

Merchant Data Collection
Merchant onboarding begins with Merchant Data Collection, where the integrator collects and submits essential details using the Integrator UI. This interface integrates with Xpor Pay's backend systems to create and manage merchant profiles.
APIs Used:
Boarding Management API – Creates the Merchant Identifier (MID) and merchant profile.
Equipment API, Pricing API, and Demographics API – Processes equipment details, pricing structures, and merchant demographics.
Once the data is submitted, Xplor Pay's system validates the provided details and returns responses for verification.
Data Validation and Correction
After submitting the application, Xplor Pay validates the data. The Application Fixes Webhook notifies the integration system of any required corrections.
Key Validations Include:
Business Contact Validation: Verifies business ownership details and information.
Bank Validation: Confirms banking details to prevent transaction errors.
These validations ensure that all merchant information is accurate and ready for processing.
Note: Merchants can still proceed even if corrections are not made immediately.
APIs Used:
Demographics API: Updates and validates merchant details, taxpayer data, business contacts, and bank account information.
Merchant Agreement and Application Submission
Merchants review their applications, sign agreements electronically, and submit the finalized application. Xplor Pay logs terms, IP addresses, and timestamps to ensure transparency.
Electronic Signature Submission: Merchants sign agreements electronically to streamline the process.
Document Upload Alternative: Pre-signed agreements can also be uploaded for verification.
APIs Used:
Demographics API – Signature Endpoints: Captures electronic signatures.
Boarding Management API – Submit Signature & Submit Application Endpoints: Finalizes the application for review.
Automated Underwriting and Decisioning
Once the application is submitted, Xplor Pay triggers a Webhook URL again to start the underwriting process. The Automated Underwriting system evaluates the merchant’s risk and compliance. There are three possible outcomes:
Approval: The merchant passes underwriting and moves to the equipment setup phase.
Manual Review: Additional verification may be required, such as further documentation or business validation.
Decline: The application is rejected if the merchant does not meet compliance or risk thresholds.
The merchant receives real-time updates on their application status via Webhook Notifications.
Equipment Setup and API Key Integration
For approved merchants, Xplor Pay configures the necessary payment hardware and provides API keys for seamless system integration.
Automated Equipment Setup (Quest/TSYS):
Configures merchant hardware, such as POS systems and card readers.
Assigns API Keys for merchants integrating with the payment processing system.
Step 5.1: Run Card-Not-Present (CNP) Transactions
From this stage, merchants can begin processing Card-Not-Present (CNP) transactions, such as online, phone, or virtual payments, after their profile is created and data is validated.
Note: CNP transactions don’t require physical equipment. Once data validation and underwriting are complete, merchants can start accepting remote payments.
Equipment Shipping and Activation
After approval, equipment is shipped and pre-configured for immediate use. Merchants can activate the equipment and begin in-person transactions.
Stage 6.1: Run Card-Present (CP) Transactions
After receiving and activating equipment, merchants can process Card-Present (CP) transactions in-store using devices like card readers or POS terminals.
Note: CP transactions require functional hardware. Once activated, merchants can immediately start in-person payment processing.
Last updated
Was this helpful?