Payment technology, pricing and support aligned with your business.

Online and Card-Not-Present Payments

Build a checkout that is easy to use and hard to abuse.

Selective Pay connects the gateway, checkout experience, tokenization, recurring billing, fraud controls and reporting around the way your business sells online—without treating every website or transaction the same.

  • Hosted checkout, payment links and API options
  • Tokenization and recurring payment workflows
  • Fraud controls matched to the customer journey
CHECKOUT

Shape the buying experience

Use hosted pages, embedded fields, payment links or integrated checkout based on the website, software and customer journey.

TOKEN

Protect repeat payments

Replace stored card data with provider-supported tokens for card-on-file, recurring billing and customer-account workflows.

ROUTE

Connect the payment rails

Align the gateway, processor, fraud tools, settlement data and integrations so the transaction can move cleanly through the business.

Checkout Hosted pages, embedded fields, links and integrations
Customer Accounts Tokens, card-on-file, subscriptions and invoices
Risk Controls AVS, CVV, velocity rules, authentication and review
Operations Settlement, reconciliation, refunds and chargebacks

More Than a Payment Button

Online payments work best when checkout, risk and operations are designed together.

A gateway can move transaction data, but the full payment environment also includes how the customer enters information, how repeat payments are stored, how suspicious activity is handled and how the accounting team reconciles deposits.

01

Reduce unnecessary checkout friction

Capture the information required to approve and manage the transaction without adding fields, redirects or steps that do not support the sale.

02

Apply controls where the risk appears

Use transaction rules, customer history, order value, velocity and verification signals instead of relying on one universal fraud setting.

03

Keep payment data usable after authorization

Carry references, tokens, order information and settlement details into customer service, recurring billing, refunds and reconciliation.

Choose the Integration Depth

Use the checkout model that fits your technology, timeline and control requirements.

The right architecture may be a hosted payment page, a secure payment link, embedded payment fields or a deeper API integration. The decision should account for development resources, customer experience, security scope and the information that must travel with the transaction.

HOSTED

Launch with provider-managed payment collection

Use a secure hosted environment when speed, simplicity and reduced handling of sensitive card data are the priorities.

  • Hosted checkout and invoice payment pages
  • Text or email payment links
  • Virtual terminal and back-office entry
  • Branded confirmation and receipt flows
  • Lower development and maintenance demands
API

Integrate payments into the customer experience

Use embedded fields, APIs, SDKs or platform integrations when payment data must connect more deeply with the website or software.

  • Embedded or headless checkout experiences
  • Customer profiles and token management
  • Subscriptions and usage-based billing
  • Order, invoice and line-item references
  • Custom reporting, webhooks and reconciliation

Architecture principle: the most customized checkout is not automatically the best checkout. Selective Pay helps balance customer experience, development effort, security responsibilities and long-term operating needs.

A Connected Payment Flow

Map the transaction from the customer’s first click through settlement.

We review each step so the checkout, gateway, processor, fraud controls and business systems support the same transaction strategy.

01

Define the buying journey

Website, mobile, invoice, subscription, customer portal, call center or another card-not-present channel.

02

Choose the checkout model

Hosted page, payment link, embedded fields, ecommerce plugin, SDK or custom API integration.

03

Configure verification and fraud rules

AVS, CVV, transaction limits, velocity, device or identity signals, authentication and manual review.

04

Authorize and tokenize

Send the transaction through the selected gateway and store supported tokens instead of raw card information.

05

Capture, settle and notify

Coordinate authorization, capture timing, order status, receipts, fulfillment and customer communication.

06

Reconcile and improve

Connect deposits, fees, refunds, chargebacks and decline patterns back to the order and accounting records.

Online Payment Workflows

Support the transaction types your customers and teams actually use.

The ecommerce strategy should account for both the public checkout and the payment activity that happens after the first sale.

WEB

Ecommerce checkout

Product, service, donation, registration and account-payment experiences across desktop and mobile.

LINK

Payment links and invoices

Send customers to a secure payment page without manually collecting card details by phone or email.

RECUR

Subscriptions and recurring billing

Use customer profiles, tokens, schedules, retries and account-updater capabilities supported by the selected platform.

B2B

Customer portals and card-on-file

Allow approved users to pay invoices, manage stored payment methods and reference orders or purchase information.

Ecommerce Payment Review

Evaluate the complete payment stack—not only the quoted processing rate.

Selective Pay reviews the checkout, gateway, processor, risk controls, recurring workflows, integrations and reporting before recommending a change.

Checkout and conversion

Payment fields, redirects, mobile experience, confirmation flow and the information required to complete the order.

Gateway and processor fit

Connectivity, supported transaction types, settlement options, commercial requirements and migration considerations.

Tokens and recurring billing

Customer profiles, portability limitations, retries, account updates, cancellation and card-on-file permissions.

Fraud and chargebacks

Verification settings, transaction rules, review processes, evidence collection and customer-service handoffs.

Reliability and redundancy

Failure points, gateway availability, retry behavior, alternate acceptance paths and business-continuity planning.

Reporting and reconciliation

Order references, funding reports, fees, refunds, disputes, location or department reporting and accounting exports.

Security note: PCI DSS responsibilities and security scope depend on the checkout architecture, systems, vendors and the way payment data is handled. Selective Pay helps evaluate solution design and provider capabilities but does not provide legal or formal compliance certification.

Frequently Asked Questions

What businesses usually ask before changing an ecommerce payment setup.

What is the difference between a payment gateway and a processor?

The gateway securely carries transaction information between the checkout and the payment ecosystem. The processor and acquiring relationship handle authorization, clearing, settlement and merchant-account functions. Some providers bundle these layers while others connect multiple partners.

Do we have to rebuild our website to change processors?

Not always. The answer depends on the existing cart, plugin, gateway, token storage and processor connection. Some changes are configuration-based, while others require a gateway migration or development work.

Can we keep customers’ stored payment methods?

Stored cards are normally represented by provider-specific tokens. Whether those tokens can be migrated depends on the current and future providers, contractual permissions, security procedures and technical support for a token-transfer process.

Can one gateway support both online and in-person payments?

Some platforms can support multiple channels and shared token or reporting environments. The actual capabilities depend on the gateway, processor, hardware, software integration and merchant setup.

How should fraud controls be configured?

Controls should reflect the product, order value, delivery method, customer type, geography, transaction velocity and chargeback history. Rules that are too loose increase exposure, while rules that are too strict can reject legitimate customers.

What do you need for an initial ecommerce review?

We start with the website or software, current gateway and processor, monthly volume, average and maximum tickets, transaction channels, recurring needs, fraud or chargeback concerns and three recent processing statements when available.

Connect the Entire Online Payment Flow

Build a checkout, gateway and processing environment around the way your business sells.

Selective Pay will review the existing stack, customer journey, payment types, risk controls, recurring workflows and integration requirements before recommending a solution.