Omnichannel · POS + online
Partner-delivered terminals, SoftPOS / Tap-to-Phone and the online checkout all run on topropay. They share one vault, one set of tokens and one reconciliation feed. A single merchant record covers every channel, so finance reads just one ledger at the end of the day.
Key benefits
Four properties that show up in production the moment POS and online stop being two separate stacks and become two faces of one platform.
A card tokenised at a POS terminal is the same vault token the merchant uses online. Returns, refunds and recurring renewals work whether the original sale was tap-to-pay in store or hosted-checkout online — no per-channel reconciliation reshuffle.
Terminal hardware, SoftPOS apps and Tap-to-Phone come from licensed partner acquirers. topropay's API in front of them means the merchant integrates once and swaps the terminal estate without re-coding.
Apple Pay, Google Pay, Click to Pay and EMV contactless cards work through the partner terminals out of the box. The merchant doesn't certify per wallet — that sits with the acquirer.
On supported devices, SoftPOS (Tap-to-Phone) turns an NFC-equipped phone or tablet into the terminal. Mobile POS payment solutions ride the same authorisation engine as fixed terminals and online.
How pos payment processing works
What actually happens between the tap on a terminal and the row in the merchant's general ledger — and where topropay sits inside that chain.
EMV chip, contactless tap, mag-stripe fallback, or SoftPOS Tap-to-Phone on supported devices. Apple Pay, Google Pay, scheme-tokenised credentials all accepted at the partner terminal.
The terminal builds the authorisation request; the partner acquirer carries it to the issuer with topropay's orchestration metadata attached for cross-channel reconciliation.
Card-present transactions clear without 3DS; high-value contactless can be PIN-stepped per scheme rules. Soft declines surface to the operator on the terminal screen.
An authorised transaction produces a vault token plus signed receipt event. The token is identical to one issued from the online surface — reusable for cross-channel refund, recurring or upsell.
Settlements from every terminal estate plus online traffic normalise into one ledger. Daily exports tagged by channel, terminal ID, acquirer and currency.
Main use cases
Six recurring merchant shapes that use POS and online side-by-side — retail, F&B, field-services, events, service businesses and omnichannel commerce.
Each store keeps its terminal estate; head office sees one ledger across stores, channels and currencies. New stores onboard against the same merchant master record.
Tableside Tap-to-Pay on phones or tablets, plus fixed counter terminals. Pre-auth + tip-on-receipt flows on the same API as online ordering.
Engineers, technicians and delivery couriers run mobile pos payment solutions on company phones. SoftPOS turns the phone into the terminal — no extra hardware to ship.
Pop-up shops, festivals and ticketing booths take contactless payment pos via SoftPOS or compact terminals. The estate scales up for an event and back down afterwards.
Salons, clinics, fitness studios — book online, pay in-person, or vice versa. The token is the same; the customer doesn't re-enter card details across channels.
Buy-online-return-in-store (BORIS) and reserve-and-collect work because POS and online share the same vault. Refunds reverse the original authorisation regardless of where it was taken.
Platform features
Twelve capabilities grouped into terminal-side, platform-side and operator-side. Each applies to both card-present and online traffic on the same merchant record.
Countertop, portable and mPOS terminals via licensed partner acquirers.
NFC-equipped Android (and supported iOS) devices act as PCI MPoC-aligned terminals.
Contactless wallets accepted by default through the partner acquirer estate.
Chip, tap and stripe fallback per scheme rules; per-terminal capability flags.
One REST contract for online checkout and POS metadata, settlement and dispute lookups.
POS and online share one vault; tokens reusable across channels for the same customer.
POS authorisations follow the acquirer's switch; online cascades through the connected processor panel.
Settlements from POS and online into one ledger tagged by channel, terminal and acquirer.
Refunds require justification and log every event with actor identity, reason and timestamp.
Restaurant-style pre-auth and tip-on-receipt are exposed on the same authorise endpoint.
Chargebacks from POS card-present and online CNP share one queue and evidence-pack template.
Reporting splits by channel (POS vs online), by terminal ID and by store / location.
Industry relevance
topropay serves licensed merchants across EU, UK, APAC and LATAM markets. That includes retail and hospitality estates, regulated subscription businesses, licensed gaming where an operating licence is in place, and service businesses. Each one can take both card-present and online payments under a single merchant record. Partner terminal estates are sized to the merchant's footprint, and the online side cascades through topropay's connected processor panel.
Trust & compliance
One audited environment for the orchestration layer; PCI MPoC and EMV rules inherited from the partner terminal estate. Sub-merchants inherit the relevant posture without carrying separate certifications themselves.
Ready to unify the channels
A 30-minute omnichannel review covers the partner terminal estate for your geographies, the mobile POS / SoftPOS option, and the cross-channel vault that ties POS and online together — followed by a sandbox you can test against before any commercial commitment.
Frequently asked
Definitions, partner-estate questions, SoftPOS / Tap-to-Phone mechanics, cross-channel refunds and the practicalities of running POS and online through one platform.
topropay delivers the orchestration layer — unified API, vault, tokenisation, reconciliation and reporting — sitting in front of partner-delivered POS terminal estates. Terminal hardware, SoftPOS apps and the card-present acquiring relationships come from licensed partner acquirers; topropay knits them together with the online side so the merchant runs one stack across channels.
POS payment processing is card-present: the card or wallet is physically tapped or chip-dipped, the issuer treats the transaction as lower-risk, and 3DS doesn't apply. Online is card-not-present (CNP) with 3DS / SCA in jurisdictions where it's required. On topropay both produce the same vault token shape, so the merchant's downstream systems don't care which channel the original sale came from.
POS payment methods supported through the partner terminal estate include EMV contact (chip-and-PIN / chip-and-signature), EMV contactless (tap), magnetic-stripe fallback per scheme rules, Apple Pay, Google Pay, Click to Pay, and scheme-tokenised credentials. Where the partner estate supports it, regional schemes (e.g. Cartes Bancaires, Bancontact, Interac) are also acceptable at the terminal.
Yes. pos online payment is the omnichannel pattern — the same merchant accepts in-person via a terminal estate and online via the unified API. topropay's vault and tokenisation are shared, so a customer who paid in-store can be refunded or re-billed through the online surface, and vice versa. Reporting splits the activity by channel for finance.
Mobile payment pos works through SoftPOS / Tap-to-Phone on NFC-equipped Android (and, where supported, iOS) devices. The partner's SoftPOS app uses the phone's NFC reader to accept a contactless card or wallet; the authorisation runs through the partner acquirer; topropay receives the settlement and reconciliation events. No external terminal hardware is required.
Contactless payment pos rides on EMV contactless and scheme-tokenised credential flows. The card or wallet doesn't transmit a static PAN — the terminal exchanges a cryptogram that's single-use for that authorisation. Contactless transactions above the regional CVM threshold step up to PIN or device biometric; below it, the cryptogram itself is the security boundary.
POS payment solutions for multi-store retail typically pair a partner-delivered countertop terminal estate (one or two SKUs across stores for serviceability) with topropay's orchestration on the back. Head office gets one ledger across the estate, store-tagged settlement, and a single dispute queue. New stores onboard against the same merchant master record rather than as separate merchant entities.
The 'pos payment gateway' on topropay isn't a separate product — it's the same orchestration platform exposing channel-aware endpoints. The terminal estate sits with partner acquirers; the platform's gateway role is on the online leg of the same merchant account, plus the cross-channel vault and reconciliation that tie POS and online together.
POS card payment reconciliation pulls settlement files from each partner acquirer carrying the in-person traffic; topropay normalises them, tags each row with channel (POS), terminal ID and acquirer, and merges with the online settlement feed into one ledger. Finance exports the merged feed as CSV or via API per the merchant's preferred cadence.
POS payment processors are licensed partner acquirers active in the merchant's target geographies. The platform doesn't lock the merchant to one — the partner estate can be split per region (EU partner for SEPA-zone stores, UK partner for UK stores, etc.) while the online side cascades through topropay's wider connected processor panel.
Yes — mobile pos payment solutions scale per device, and a fleet of devices scales linearly. The bottleneck is the partner acquirer's switch capacity, not the SoftPOS app or topropay's orchestration. For peak events, the partner estate's switch is sized in advance against forecast volume.
From contract to first POS transaction typically runs 2–6 weeks depending on the partner acquirer's underwriting timeline, the volume of terminal SKUs being shipped, and any KYB checks outstanding. Online integration can be live before terminals arrive; the same merchant record covers both.
Modern partner terminals support store-and-forward for a bounded queue of EMV contact transactions, replayed when connectivity returns. Contactless and online-only schemes require live connectivity. Operator-side reporting flags any store-and-forward backlog and the partner acquirer's clearing of it.
Partner SoftPOS apps used through topropay follow PCI's MPoC (Mobile Payments on COTS) programme, which is the current PCI standard for accepting card-present transactions on commercial off-the-shelf devices. topropay's vault and tokenisation are PCI DSS Level 1; the combination keeps PAN exposure out of the merchant's app code and devices.
Refunds run against the vault token issued by the original authorisation. A POS sale produces a token; a refund initiated from the merchant's online back-office targets that token and reverses the authorisation through the same partner acquirer. The customer doesn't need to return to the original store.
Related