Start with the operating software
Identify where invoices, orders, customers, products, locations and payment requests originate before choosing the payment connection.
ERP, POS, Ecommerce and Software Connections
Connect the payment layer without rebuilding the business.
Selective Pay maps the processor, gateway, software, customer tokens, devices and reporting around the systems your team already uses—so payment data can move cleanly from the customer interaction through settlement and reconciliation.
- Gateway and processor compatibility review
- ERP, POS, ecommerce and accounting workflows
- Tokenization, reporting and support ownership
Connect the gateway and processor
Confirm supported APIs, certified devices, transaction types, settlement paths and the providers responsible for each part of the flow.
Return usable information
Bring authorization results, tokens, invoice references, deposits, fees and exceptions back into reporting and reconciliation workflows.
More Than an API
A payment integration must work technically, financially and operationally.
A connection can authorize a card and still create problems if it loses invoice detail, separates customer tokens, complicates deposits or leaves no one accountable when systems disagree. We evaluate the complete transaction lifecycle before recommending a path.
Compatibility assumptions
A software logo or general API claim does not confirm support for the required processor, gateway, device, transaction type or data fields.
Fragmented transaction data
Payments may settle successfully while invoice numbers, customer references, tips, line items or location details fail to return to the source system.
Unclear support ownership
When the software company, gateway, processor and device provider are separate, merchants can be left coordinating every technical problem themselves.
Choose the Right Connection
Match the integration method to the workflow, security scope and required data.
The best architecture may use one connection or a combination of supported methods. The objective is a stable payment path that preserves the information the business needs.
Hosted and semi-integrated payment paths
Reduce direct card-data handling while keeping the customer and employee experience connected to the business application.
- Hosted checkout pages, payment links and embedded payment fields
- Semi-integrated terminals and provider-supported device connections
- Virtual terminal, invoice and recurring-payment workflows
- Provider-managed tokenization and stored-payment capabilities
Direct API, gateway and middleware connections
Support more customized transaction, customer, product and reporting requirements when the software environment can maintain the integration.
- Authorization, capture, refund, void and recurring transaction APIs
- Customer, token, invoice, order and line-item data mapping
- Webhooks, status updates and exception handling
- ERP, accounting, ecommerce and vertical-software connectors
Architecture note: An available API does not automatically mean every processor, gateway, token, device or commercial-card data requirement is supported. Selective Pay confirms the actual certified and supportable path before a migration is recommended.
A Supportable Payment Architecture
Map the full transaction before selecting the providers.
We document where the payment begins, which system controls the customer experience, how transaction data moves and who owns each operational responsibility.
Identify the system of record
Determine where customers, invoices, orders, products, locations, recurring schedules and accounting references are created and maintained.
Document every payment action
Map authorizations, captures, tips, partial payments, refunds, voids, card-on-file, recurring payments, ACH and exception workflows.
Confirm the supported connection
Verify gateway, processor, API, device, tokenization, operating-system and software certifications rather than assuming compatibility.
Design the return data
Define the authorization response, token, transaction ID, invoice reference, settlement status, fee and exception data that must return to the business.
Assign implementation and support ownership
Set responsibilities for development, testing, credentials, device staging, certification, deployment, reconciliation and ongoing escalation.
Where Integration Strategy Matters
Built for businesses whose payment data must serve more than the checkout.
Invoice, commercial card and accounts-receivable workflows
Connect payments to invoices, purchase orders, customer records, Level II or Level III data and cash-application processes.
Integrated devices and customer-facing transactions
Coordinate the POS, terminal, tips, tabs, tokens, mobile workflows, settlements and location reporting.
Checkout, subscriptions and customer accounts
Align hosted or embedded checkout, fraud tools, stored credentials, recurring schedules, refunds and customer portals.
Healthcare, field service and distributed businesses
Connect office, mobile, online and recurring channels while preserving department, location and customer references.
What We Review
A complete integration review looks beyond whether a transaction can be approved.
We evaluate the software, payment providers, data requirements, security model, settlement process and support structure as one operating environment.
Current software environment
ERP, POS, ecommerce, accounting, CRM, practice-management and vertical platforms involved in the payment workflow.
Gateway and processor compatibility
Supported processors, gateways, APIs, devices, merchant-account structures, transaction types and certification restrictions.
Required payment functions
Sales, authorizations, captures, tips, partial payments, recurring billing, refunds, ACH, stored credentials and multi-location needs.
Data and reconciliation
Invoice, order, customer, product, tax, location, deposit, fee, refund and exception data required by operations and accounting.
Security and token strategy
Hosted data capture, encryption, token ownership, token migration, permissions, device security and provider-supported controls.
Implementation and support
Development resources, testing, credentials, staging, cutover, fallbacks, monitoring and the escalation path across all providers.
Compatibility note: Integration features and processor availability vary by software version, gateway, device certification, merchant category and provider agreement. We verify the proposed configuration with the involved providers before implementation.
Frequently Asked Questions
What businesses usually ask before changing a gateway or payment integration.
Can we keep our existing software and change processors?
Sometimes. The software must support the proposed processor directly or through a compatible gateway or integration. We confirm the certified options, contract requirements and required features before recommending a change.
What is the difference between a gateway and a processor?
The gateway generally connects the payment experience or software to the processing environment, while the processor and acquiring relationship authorize, settle and fund the transactions. The exact responsibilities depend on the providers and architecture.
Can existing customer tokens move to a new gateway?
Possibly, but token portability is provider-specific. A migration may require cooperation from the current and new providers, customer or transaction matching, testing and a plan for tokens that cannot be transferred.
Does using an API remove PCI responsibilities?
No. The payment design can reduce direct exposure, but the merchant still has responsibilities based on how card data is collected, transmitted, stored and accessed. Hosted or provider-controlled payment components may help reduce scope when implemented correctly.
Can one integration support cards, ACH and recurring payments?
Some gateways and software connections support multiple payment methods and recurring workflows. Availability depends on the processor, gateway, software capabilities, underwriting and the transaction types required.
What do you need for an initial integration review?
We start with the software names and versions, current gateway and processor, payment channels, required transaction functions, merchant accounts, device inventory, token use, statements, reporting needs and any current reconciliation or support problems.
Connect the Payment Environment
Build a payment architecture your software, accounting team and customers can all use.
Selective Pay will review the current systems, gateway, processor, devices, tokens, transaction data, settlement and support requirements before recommending an integration path.