Start with the customer experience
Determine where customers enter payment information and whether the checkout is hosted, embedded or controlled by the ecommerce platform.
Online Payment Processing
Ecommerce merchant account & credit card processing built for the checkout.
Selective Pay helps businesses accept online payments through a secure merchant account and payment gateway structure aligned with the way customers actually buy—whether through ecommerce checkout, payment links, customer portals, subscriptions or integrated business software.
- Merchant account and gateway coordination
- Hosted checkout, tokenization and recurring payments
- Ecommerce, ERP and accounting integration review
Connect the gateway and merchant account
Confirm the supported gateway, processor, fraud controls, tokenization and transaction types before changing the payment path.
Return usable payment data
Preserve order references, transaction IDs, refunds, deposits, fees and exceptions so accounting and operations can reconcile ecommerce activity.
Merchant Account + Gateway
Online payments work best when the merchant account, gateway and checkout are designed together.
An ecommerce merchant account is part of the acquiring relationship that allows a business to accept card payments online and receive settlement proceeds to its business bank account. The payment gateway connects the checkout or software to that processing environment.
Those pieces should not be selected in isolation. Processor compatibility, tokenization, recurring billing, refund workflows, reporting and the ecommerce platform all affect whether the payment setup will work reliably.
Merchant account
The processing relationship through which approved card transactions are authorized, settled and funded according to the merchant agreement.
Payment gateway
The technology layer that securely connects the ecommerce checkout or business application to the supported processing environment.
Ecommerce platform
The website, shopping cart, portal or software where customers place orders and where order, customer and payment references originate.
How Ecommerce Payments Work
Map the transaction from checkout through settlement.
A fast authorization is only one part of a good ecommerce payment setup. The complete workflow should protect card data, maintain order references and make refunds, deposits and reconciliation manageable for the business.
Customer submits payment
The customer enters payment information through a hosted page, embedded checkout, payment link, portal or another supported online payment component.
Payment data is protected and routed
The gateway or payment component securely sends the transaction into the processing environment while applying supported security and fraud controls.
Authorization is returned
The processor and card network route the authorization request to the issuing bank and return the approval or decline result to the checkout.
Orders and payment references stay connected
The ecommerce system should retain the information needed to match the payment to the customer, order, invoice, refund or recurring schedule.
Transactions settle and fund
Approved transactions are submitted for settlement and the merchant receives funding according to the processing agreement and applicable settlement schedule.
Ecommerce Payment Options
Support the payment methods and workflows that make sense for the business.
Not every ecommerce merchant needs the same payment architecture. Selective Pay reviews the merchant's software, transaction types and customer experience before recommending the connection.
Credit and debit card processing
Accept supported card transactions through the merchant's online checkout, portal or payment link workflow.
Tokenized card-on-file
Use supported tokenization for repeat customers without relying on raw card-number storage inside merchant systems.
Subscriptions and scheduled billing
Support recurring payment schedules when the gateway, processor and merchant setup provide the required functionality.
Bank-account payment options
For appropriate business workflows, ACH can complement card acceptance for invoices, recurring payments and B2B transactions where supported.
Security & Fraud Controls
Keep card data exposure low without making checkout difficult.
Payment security should be designed into the checkout architecture. Hosted payment components, tokenization and provider-supported fraud controls can help reduce unnecessary exposure while preserving a practical customer experience.
Hosted or provider-controlled card entry
Keep sensitive card entry outside systems that do not need to handle it directly, where the selected platform and gateway support that architecture.
Tokenization
Replace stored card numbers with supported tokens for recurring and card-on-file workflows.
Fraud-control configuration
Evaluate available tools such as address verification, CVV handling, velocity controls and other provider-supported fraud settings based on the merchant's risk profile.
PCI note: Using hosted payment components or a secure gateway can reduce card-data exposure, but merchants still have PCI DSS responsibilities based on their complete payment environment. Review Selective Pay's PCI Compliance Guide →
B2B Ecommerce
Commercial ecommerce payments may need more than a retail checkout.
Wholesale, distribution, manufacturing and other B2B sellers may need invoice references, customer codes, purchase-order information, tax data, line-item details, ACH and commercial-card optimization in addition to ordinary online payment acceptance.
Connect payments to the order and invoice
Preserve the business data required for accounts receivable, customer service, reconciliation and commercial-card qualification.
- Invoice and purchase-order references
- Customer and order identifiers
- Tax and transaction details
- ERP and accounting workflow
Review commercial-card optimization
Where supported, Level II and Level III data may improve interchange qualification on eligible commercial card transactions.
- Commercial-card data requirements
- Line-item and tax-field mapping
- Gateway and processor support
- Settlement and reporting validation
Choosing an Ecommerce Processor
Compare the complete payment environment—not just the advertised transaction rate.
Pricing matters, but the lowest advertised rate is not useful if the gateway does not support the ecommerce platform, recurring workflow, security model or reporting the business requires.
Pricing and interchange structure
Understand processor fees, gateway fees, transaction costs and how the merchant's card mix and transaction data affect the actual processing cost.
Compatibility and integration
Confirm support for the ecommerce platform, processor, gateway, APIs, tokens, payment methods and transaction functions actually required.
Support and reconciliation
Know who owns implementation, payment issues, refunds, deposits, gateway problems and escalation when more than one provider is involved.
Frequently Asked Questions
Ecommerce merchant account and credit card processing questions.
What is an ecommerce merchant account?
An ecommerce merchant account is part of the acquiring relationship that enables a business to accept card payments online and receive settlement proceeds to its business bank account.
Do I need a payment gateway for ecommerce credit card processing?
Most ecommerce setups use a gateway or provider-controlled payment component to connect the online checkout to the processing environment. The exact architecture depends on the ecommerce software, processor and merchant requirements.
Can I keep my existing ecommerce platform and change processors?
Sometimes. The platform must support the proposed processor directly or through a compatible gateway or integration. The actual certified and supportable path should be confirmed before a migration.
Can ecommerce payments support recurring billing and stored cards?
Many gateway configurations support recurring or card-on-file payments through tokenized credentials. Availability depends on the gateway, processor and merchant setup.
Can B2B ecommerce transactions qualify for Level II or Level III processing?
Potentially. Eligible commercial card transactions may benefit when the gateway, processor and ecommerce or ERP workflow support the required additional data and it is transmitted correctly.
What should I provide for an ecommerce payment review?
We typically start with the ecommerce platform, current gateway and processor, monthly volume, average ticket, statements, recurring or card-on-file requirements, fraud concerns, accounting or ERP integrations and any current checkout or reconciliation problems.
Review Your Ecommerce Payments
Build an online payment setup around your checkout, software and processing economics.
Selective Pay can review your ecommerce platform, merchant account, gateway, statements, recurring-payment needs, transaction data and reconciliation requirements before recommending a payment path.