Short answer
Omnichannel payments means taking cards everywhere you sell (the store counter, your website, phone orders, invoices, payment links, and mobile) through one processing setup. For a merchant, the payoff is one provider and records that line up, which makes cross-channel returns and saved cards easier to handle. The cost is more PCI and fraud work than a single channel brings.
With omnichannel payments, every channel you sell through runs on one processing setup instead of a separate provider for each. A gift shop might take cards at the counter, on its website, over the phone, through invoices and payment links, and on a phone at a weekend market. In an omnichannel setup, those sales run through one merchant account and one gateway, so a customer can buy online, pick up in the store, and return the item at the counter without the payment side breaking.
Below we go channel by channel, then cover the gateway, tokens, the cross-channel flows that trip stores up, PCI scope, cost, and when it isn't worth doing. Facts are current as of October 2026.
What is omnichannel payments?
It's one payment setup behind every place you sell. Card terminals handle the counter, a gateway handles every sale where the card isn't present, and both settle to the same merchant account. The alternative is a patchwork: one company for the store, another for the website, a third for invoices. That's multichannel, and it works, but each piece comes with its own contract, its own statement, and its own vault of saved cards.
| Multichannel: a setup per channel | Omnichannel: one setup | |
|---|---|---|
| Providers and contracts | One for each channel | One |
| Saved cards | Locked in each provider's vault | Held by one provider, usable wherever its tokens work |
| Returns | Usually refunded where the sale happened | Can cross channels, if staff can find the order |
| Dispute evidence | Scattered across systems | Kept with one provider |
For a merchant, that means fewer contracts and fewer places where card data sits. Customers also get to move between channels without the payment getting in the way.
Which channels can one payment setup cover?
Six channels cover most setups. Each one takes the card differently, and that drives its cost and its PCI paperwork.
| Channel | How the card arrives | Card present? | Clearo service | Likely PCI questionnaire |
|---|---|---|---|---|
| Store counter | Chip, tap, or swipe on a terminal | Yes | POS terminals | SAQ B-IP, or SAQ P2PE with a validated solution |
| Website | Hosted checkout or embedded payment fields | No | Online payments | SAQ A, or longer if your site builds the form |
| Phone and mail orders | Staff key the card into a virtual terminal | No | Virtual terminal | SAQ C-VT |
| Invoices and payment links | The customer pays on a provider-hosted page | No | Virtual terminal invoices and payment links | Usually SAQ A |
| Subscriptions and deposits | A saved card charged on a schedule | No | Virtual terminal recurring billing | Depends on how you collected the card |
| Markets, deliveries, field work | Tap to pay on a phone, or a mobile card reader | Yes | Mobile payments | Ask your acquirer |
Clearo's payment processing covers each of these channels: terminals for the counter, online payments with hosted checkout and gateway integration, a virtual terminal with invoices, payment links, and recurring billing, and mobile payments with tap to pay and mobile card readers. Our guide on how to accept payments online compares the online options in more depth.
Where does a payment gateway fit in omnichannel payments?
The gateway runs every channel where the card isn't in front of you. Website checkout, payment links, invoices, and the virtual terminal all send card data through a gateway for approval, while your store terminals connect to your processor without a separate gateway purchase. So the omnichannel payments gateway you want is simply one gateway, tied to the same merchant account as your terminals, behind all of your card-not-present channels.
What to check in that gateway:
- Hosted checkout or embedded fields, so card numbers never touch your own server.
- Payment links and invoices from the same account, with no second signup.
- A virtual terminal for phone and mail orders.
- Tokens for saved cards, plus a written answer on whether you can take them with you if you leave.
- Refunds against the original sale from any channel, found by order number or transaction ID.
- Fraud screening you can tune, such as AVS, CVV checks, and velocity rules.
Our guides to what a payment gateway is, the hosted payment page, and the payment link explain each piece.
How do tokens let one card work across channels?
Tokens let a card saved in one channel be charged in another without anyone keeping the card number. Under EMVCo's framework, a payment token is a substitute for the card number that can be limited to one merchant, one device, or one kind of payment. Three kinds show up in an omnichannel setup:
- Processor or gateway tokens. Your provider issues them for cards you save, and they work only with that provider.
- Network tokens. Visa's Token Service swaps Visa card numbers for tokens in digital payments. Mastercard's MDES for merchants exchanges a card number, whether a customer types it in or it's already on file, for a token, provided the card's issuer takes part. Mastercard adds that merchants then don't need to keep card numbers on file, which lowers the fraud risk if their data is breached.
- Device tokens. Digital wallets carry their own. When a customer adds a card to Apple Pay, the phone stores a Device Account Number, and Apple says the actual card number isn't sent when the customer pays in a store.
That last one is where omnichannel and digital payments meet. A wallet works the same way at your counter as on a phone at a market stall, and Clearo terminals accept Apple Pay and Google Pay alongside cards.
Saving a card online and charging it later by phone or invoice has rules attached. Visa's stored credential framework says you need the cardholder's agreement before keeping their card for future use, and that the first storage and each later charge should be flagged as such in the transaction data. Before you rely on tokens across channels, ask your provider two things in writing: does a token created at your online checkout work in your virtual terminal, and can your saved cards move to a new provider if you ever switch? Our guides to payment tokenization, card on file, and recurring billing go further.
How do buy online, pick up in store and cross-channel returns work?
These two flows are where omnichannel either works or falls apart at the counter.
Buy online, pick up in store
The payment happens online, so it's a card-not-present sale even though the customer walks in to collect. That shapes your dispute risk. Visa's dispute guide for merchants notes that card-absent merchants may see more disputes than card-present ones, since the card isn't read electronically. Your best defense against a "never received it" claim is the pickup record.
Say a bike shop in Boise sells a $480 bike online for Saturday pickup. At the counter, staff check the order number and a photo ID, and the customer signs a pickup slip that's saved with the online order. If the cardholder later disputes the sale as not received, that slip is the evidence the shop sends. Our guide to chargeback representment covers how to package it.
There's a simpler variation: reserve online, pay in store. If the customer pays at pickup, the sale runs on your terminal by chip or tap, and the online order only holds the stock.
Returning an online order in store
Refund the original card. Visa's guidance on processing refunds in a store starts with the card used for the purchase. If that card has been closed or replaced, the refund can go to another Visa card once you've confirmed the purchase was made on a Visa account, and other forms of credit come only after that. Refunds also need approval now: Visa began requiring a purchase return authorization in October 2018 for US and Canadian merchants above set return volumes, and in April 2019 for all others.
Speed counts as well. Regulation Z puts a clock on credit card returns: once you accept one, you have 7 business days to send the credit to the card issuer. The practical test for your store: can someone at the counter find an online order and refund it to the original card without that card in hand? If the terminal can't, the virtual terminal or your gateway's refund screen can do it from the back office. Decide which before you advertise in-store returns.
How does PCI scope change by channel?
Each channel comes with its own self-assessment questionnaire, so every channel you add can add PCI work. These are the questionnaires PCI SSC writes for each kind of setup:
| Your setup | Questionnaire | PCI SSC document |
|---|---|---|
| Website redirects to a hosted payment page, or you send payment links | SAQ A | SAQ A update |
| Website embeds the provider's payment fields | SAQ A, once you confirm your site isn't open to script attacks | FAQ on the SAQ A criteria |
| Your own site builds the payment form | SAQ A-EP | SAQ A-EP |
| Card numbers pass through your own servers | SAQ D | SAQ D |
| Standalone approved terminals with an IP connection | SAQ B-IP | SAQ B-IP |
| Terminals from a validated point-to-point encryption solution | SAQ P2PE | SAQ P2PE |
| Staff key phone orders one at a time into a hosted virtual terminal | SAQ C-VT | SAQ C-VT |
The embedded-fields condition has applied since March 31, 2025, and PCI SSC's FAQ says it doesn't apply to plain redirects or emailed payment links. Two lessons follow. Build online channels on hosted pages and payment links, which can keep you in SAQ A, the shortest questionnaire. And before you add a channel, ask your acquirer how it wants a business with several channels to validate.
Visa rewards the safer options too. Its Technology Innovation Program can remove the annual validation requirement for eligible merchants that run at least 75% of their yearly transactions through EMV chip terminals, a validated P2PE solution, or EMVCo-standard tokenization. Ask your acquirer whether you qualify.
What does each channel cost?
Card-not-present sales cost more in interchange, so a shift toward online sales changes your blended rate. On Visa's US schedule effective April 18, 2026, a Traditional Rewards credit card carries 1.65% plus a fixed fee when it's dipped or tapped in person, and 2.04% plus the same fee when it's used online.
Put that on a home goods store in Cincinnati with $20,000 a month on those cards. The percentage part of interchange is $330 at the counter ($20,000 × 1.65%) and $408 online ($20,000 × 2.04%), a $78 gap before fixed fees and the provider's markup. Phone orders keyed into a virtual terminal are card-not-present as well, so when a customer is standing in front of you, tap the card rather than typing it. On interchange-plus pricing, which Clearo uses, each sale's interchange appears on your statement, so you can see that gap instead of guessing at it.
What are the trade-offs of going omnichannel?
What you gain:
- One provider, one contract, and one rep to call.
- Saved cards that work across your channels, where your provider's tokens allow it.
- Returns and exchanges that can cross channels.
- Dispute evidence for each sale in one place.
What it costs you:
- A bigger share of card-not-present sales, with higher interchange and more dispute exposure.
- More PCI questions, one set per kind of channel.
- Tokens that tie you to the provider that issued them.
- Staff training on pickups, cross-channel refunds, and phone orders.
- Order and stock data that still live in your POS and e-commerce software, which you have to connect yourself.
Retail omnichannel payments: what changes for a store?
Stores feel this most, because shoppers mix channels freely. By the Census Bureau's seasonally adjusted count, e-commerce made up 17.1% of US retail sales in the second quarter of 2026. For retail omnichannel payments, plan four flows: buy online and pick up in store, buy in store and ship, return anywhere, and save a card for next time. Most of the payment side is covered above, and buy in store and ship is a card-present sale with a delivery record to keep.
The stock side isn't a payments job. One inventory count shared by the counter and the website comes from your POS and e-commerce software, so judge it there. Our guide to a retail POS system covers what to look for, and our retail page covers the card side of a store.
Omnichannel payments setup checklist
- List every place you take money today, including the ones nobody owns, like the market stall or the deposit invoices.
- Put every channel on one merchant account, with one gateway behind your online, phone, invoice, and link payments.
- Use hosted checkout or payment links online, and chip and tap terminals in the store.
- Turn on fraud screening for card-not-present sales: AVS, CVV checks, and velocity rules.
- Get consent before saving any card, and keep tokens, never card numbers.
- Ask your provider in writing whether its tokens work across your channels and whether they can move if you leave.
- Write a rule for online orders that come back to the store, then test a refund to the original card.
- Save the pickup record with every online order collected in person.
- Confirm with your acquirer which PCI questionnaires you'll file.
- Compare your effective rate by channel on your statement every quarter.
When isn't omnichannel worth the effort?
When you really sell in one channel. A food truck that takes taps, or a consultancy that only sends invoices, gets nothing from consolidating channels it doesn't use. The same goes for a shop whose online sales are a sliver, where a payment link may be all the online side needs. And if your POS software bundles its own payments, price out the switch before you move.
Our view: consolidate once you run at least two channels with real volume, or once customers already cross between them. Below that, keep it simple and look again in a year. When you're ready to compare providers for selling both online and in person, our best payment processor for small business list ranks seven and spells out the criteria. Card network rules and PCI requirements apply the same way to merchants anywhere in the United States, so the size of your channels decides this, not your location.
Next step
Count your channels and what each one costs you. Send us a recent statement for a free statement review, and we'll show you what you pay and where the card-not-present costs sit. Or contact us to plan terminals, online payments, and a virtual terminal with one dedicated rep.
About this guide
Written by the Clearo Payments team. Clearo provides interchange-plus payment processing to merchants in the US and Canada, with no long-term contracts and no cancellation fees. Card network rules and laws change, so check the sources below before you act on anything here. Our editorial standards explain how we source and update guides. Questions about your own setup? Ask our team.
Sources
Official and primary sources we checked while writing this guide.
- EMV Payment Tokenisation | EMVCo (emvco.com)
- Visa Token Service (visa.com)
- Card On File Tokenization: MDES for Merchants - Mastercard Developers (developer.mastercard.com)
- Apple Pay security and privacy overview - Apple Support (support.apple.com)
- Visa Transactions Initiated with Stored Credentials (usa.visa.com)
- Dispute Management Guidelines for Visa Merchants June 2024 (usa.visa.com)
- Processing Refunds to Cardholders in a Merchant Store - Visa (usa.visa.com)
- Improve the Customer Return Process - Visa (usa.visa.com)
- § 1026.12 Special credit card provisions - CFPB (consumerfinance.gov)
- Important Updates Announced for Merchants Validating to Self-Assessment Questionnaire A (blog.pcisecuritystandards.org)
- FAQ Clarifies New SAQ A Eligibility Criteria for E-Commerce Merchants (blog.pcisecuritystandards.org)
- PCI DSS v4.0.1 SAQ A-EP (docs-prv.pcisecuritystandards.org)
- PCI DSS v4.0.1 Self-Assessment Questionnaire D for Merchants (docs-prv.pcisecuritystandards.org)
- PCI DSS v4.0.1 SAQ B-IP (docs-prv.pcisecuritystandards.org)
- PCI DSS v4.0.1 SAQ P2PE (docs-prv.pcisecuritystandards.org)
- PCI DSS v4.0.1 SAQ C-VT (docs-prv.pcisecuritystandards.org)
- Account Information Security (AIS) Program and PCI | Visa (corporate.visa.com)
- Visa USA Interchange Reimbursement Fees (rates effective April 18, 2026) (usa.visa.com)
- Quarterly Retail E-Commerce Sales, 2nd Quarter 2026 (US Census Bureau) (www2.census.gov)