Card-present · EMV chip-and-PIN

Chip and PIN payment system — EMV acceptance on a unified platform.

Chip-and-PIN via licensed partner terminals, orchestrated behind one topropay merchant record. Vault tokens shared with the online surface; refunds work across channels; finance reads one ledger tagged by channel, terminal and acquirer.

Book a card-present review Read the API docs
EMV
chip-and-PIN via licensed partner terminals
PCI L1
vault inherited across every channel
Cross-channel
vault tokens shared with online
1 ledger
reconciliation across in-person + online

Key benefits

Why a unified chip and pin payment system beats a siloed one

Four properties that show up the moment card-present acceptance stops being a separate stack from the online surface.

  1. 01

    EMV chip-and-PIN, delivered right

    Card-present acceptance runs through licensed partner acquirers on EMV-certified terminals. Chip insertion and PIN entry follow scheme CVM rules; magnetic-stripe fallback is bounded per acquirer policy where it's still allowed.

  2. 02

    Same merchant record online and in-store

    The card-present terminal estate rides the same topropay merchant record as the online checkout. Refunds, chargebacks and recurring can reference the vault token regardless of which channel took the original sale.

  3. 03

    Faster PIN paths where available

    Contactless and mobile-wallet flows sit alongside chip-and-PIN on the same terminal — under CVM thresholds the customer taps without a PIN entry; above them the terminal steps up to PIN by scheme rule.

  4. 04

    One reconciliation feed

    Settlement files from every partner acquirer normalise into one ledger; each row tagged with channel (card-present vs card-not-present), terminal ID, acquirer and currency.

How it works

From chip insertion to reconciliation in five steps

What happens between the customer inserting the card and finance seeing a merged row in the reconciliation feed.

  1. 01

    Card inserted and PIN prompted

    The chip contact activates the EMV kernel on the terminal; card data reads from the chip, not the stripe; the terminal prompts for PIN entry under scheme CVM rules.

  2. 02

    Terminal builds the authorisation

    Terminal composes the ISO 8583 / EMV authorisation request with cryptogram, PIN block and transaction data; the partner acquirer's switch carries the request to the issuer.

  3. 03

    Issuer approves or declines

    The issuer verifies the cryptogram and PIN; approval or decline flows back through the acquirer to the terminal within seconds; on approval the terminal prints or emails the receipt.

  4. 04

    Vault token issued back to the platform

    An authorised chip-and-PIN transaction produces a vault token on the platform side, reusable for cross-channel refunds or recurring on the same customer.

  5. 05

    Reconciliation in one ledger

    Settlement files from the partner acquirer flow into the unified ledger alongside online receipts; finance imports the merged feed into the accounting system.

Main use cases

Where card-present chip-and-PIN earns its keep

Six recurring merchant shapes that benefit from chip-and-PIN alongside online — retail, hospitality, travel, field-services, events and B2B.

  • Retail

    Multi-store retail with chip-and-PIN counters

    Countertop terminals across stores handle in-person chip-and-PIN acceptance; head office sees one ledger across stores, channels and currencies with per-terminal tagging.

  • F&B

    Restaurants and hospitality

    Portable pay-at-table terminals accept chip-and-PIN; contactless caps handle small tickets; pre-auth + tip-on-receipt runs through the same authorise endpoint as online.

  • Travel

    Travel counters and hotels

    Front-desk chip-and-PIN authorisation at check-in, capture at check-out, refunds on cancellation — all against the same vault token as the online booking, avoiding split-record reconciliation.

  • Field

    Field-services and mobile teams

    Portable terminals or SoftPOS on a phone accept chip-and-PIN at the customer's location; the receipt lands in the merchant's back-office in real time via signed webhook.

  • Events

    Events, box-offices and ticketing

    Pop-up terminals accept chip-and-PIN for high-value tickets where contactless would exceed CVM caps; portable terminal fleets scale up for the event and back down afterwards.

  • B2B

    B2B with in-person presence

    Wholesalers, distributors and trade counters take chip-and-PIN at the counter, plus SEPA / ACH for recurring B2B contracts on the same merchant record — one dispute queue, one ledger.

Platform features

Capabilities behind the chip and pin payment system

Twelve capabilities grouped into terminal / scheme, platform / tokens and operations / finance. Each applies to both card-present and online traffic on the same merchant record.

Terminal & scheme

  • EMV chip-and-PIN certified terminals

    Countertop, portable and mPOS terminals via licensed partner acquirers with scheme-side EMV certification.

  • Contactless + mobile wallets

    Apple Pay, Google Pay and Click to Pay tap flows on the same terminal, under and over CVM thresholds.

  • Chip + contactless + MSR fallback

    Chip preferred by scheme rule; contactless within limits; magnetic-stripe fallback bounded per acquirer policy.

  • Scheme CVM rules respected

    PIN required over threshold, biometric-on-device for wallets, signature only where the scheme still permits.

Platform & tokens

  • Cross-channel vault tokens

    One token per card, usable across POS and online for refunds, recurring or cross-channel purchase history.

  • PCI DSS Level 1 vault

    Vault, switch and tokenisation are PCI DSS Level 1 service-provider components; sub-merchants inherit the posture across channels.

  • Signed webhook events

    Authorisation, capture, settlement and dispute events fire signed, replay-safe webhooks per transaction.

  • Operator dashboard

    Refunds, disputes, settlements and per-terminal reports in one console alongside the online-side data.

Operations & finance

  • Operator-side refund controls

    Refunds require justification and log every event with actor identity, reason and timestamp.

  • Tip and pre-auth flows

    Restaurant-style pre-auth + tip-on-receipt exposed on the same authorise endpoint as one-off card sales.

  • Unified dispute queue

    Chargebacks from POS card-present and online CNP share one queue and one evidence-pack template per vertical.

  • One reconciliation feed

    Settlements from every partner acquirer normalised into one ledger, tagged by channel, terminal / device, acquirer and currency.

Industry relevance

Card-present acceptance for licensed EU, UK, APAC and LATAM merchants

topropay's card-present posture targets licensed merchants operating across Europe, the UK, APAC and LATAM — multi-store retail, restaurant and hospitality estates, travel counters and hotels, field-services businesses, events and ticketing operations, and B2B counters with an in-person presence. Partner terminal estates are sized to the merchant's footprint; the online side rides the same merchant record.

Trust & compliance

Compliance posture across the card-present estate

One audited platform-side environment plus EMV certification and scheme CVM rules inherited from the licensed partner acquirer estate.

PCI DSS Level 1
Vault, switch and tokenisation are PCI DSS Level 1 service-provider components; the merchant inherits the posture across every channel the terminal estate covers.
EMV certification
Terminals in the connected estate carry scheme-side EMV certification (Visa, Mastercard, Amex, Discover, JCB where applicable) issued through the licensed partner acquirer.
Scheme CVM rules
PIN, contactless CVM caps and wallet-biometric flows follow the scheme's regional rules; the acquirer's policy dictates any residual magnetic-stripe fallback.
SCA & PSD2 (online leg)
Selective EMV 3DS2 on the online surface keeps European card-not-present approval high; card-present clears under its own CVM rules.
Sanctions & AML alignment
Sanctions screening on onboarding; AML monitoring tuned per merchant vertical, volume and channel mix.
Licensed verticals only
Licensed gaming, regulated financial services and other compliance-bound verticals supported only where current operating licences exist. Grey and black-market verticals are out of scope regardless of channel.

Ready to unify card-present with online

Bring your card-present estate onto one platform.

A 30-minute review covers the partner terminal estate for your geographies, cross-channel vault behaviour, and a sandbox you can test against before any commercial commitment.

Book a card-present review Read the API docs

Frequently asked

Buyer questions about the chip and pin payment system on topropay

Terminal ownership, cross-channel refunds, dispute mechanics, high-value tickets and the practicalities of running card-present alongside online through one platform.

  1. 01

    What does chip and pin payment system mean on topropay?

    A chip and pin payment system on topropay is card-present EMV acceptance delivered through licensed partner terminal estates, orchestrated behind topropay's platform. Terminals read the card's chip, prompt for PIN under scheme CVM rules, and clear through the partner acquirer. The vault, tokenisation, dispute queue and reconciliation sit on the topropay platform alongside the online-side flow.

  2. 02

    Does topropay ship the terminals directly?

    Terminals are supplied and maintained by licensed partner acquirers, not by topropay directly. The platform handles the back-end orchestration (vault, tokenisation, dispute queue, reconciliation) and the merchant onboarding; the partner acquirer handles the hardware supply chain, EMV certification and physical support for the terminal estate.

  3. 03

    How does chip-and-PIN interact with the online side?

    Chip-and-PIN transactions produce a vault token on the platform side just like online transactions. That means refunds, recurring authorisations and cross-channel purchase history can reference the token regardless of which channel took the original sale. Finance reads one ledger across both channels, with per-row channel tagging.

  4. 04

    What if a customer wants to tap instead of insert?

    Contactless flows sit on the same terminal as chip-and-PIN. Under the local contactless CVM threshold the customer taps their card, phone or watch without a PIN entry. Above the threshold, the terminal steps up to PIN entry — or biometric on-device for wallet flows — per scheme rule. The merchant doesn't configure this manually; the terminal handles it in EMV firmware.

  5. 05

    Is magnetic-stripe fallback supported?

    Magnetic-stripe fallback is supported only where the partner acquirer's policy and the scheme still permit it (typically only after multiple failed chip reads). Most regions have effectively phased mag-stripe out for domestic transactions; the terminal firmware enforces the rules per region and per issuer BIN.

  6. 06

    How long does a merchant take to go live on chip-and-PIN?

    From contract to first chip-and-PIN transaction is typically 2–6 weeks depending on the partner acquirer's underwriting timeline, the terminal SKU volumes being shipped, and any KYB checks outstanding. The online integration on the same merchant record can be live before terminals arrive, so the first receipt-in-cash-flow date is often much sooner.

  7. 07

    What happens when a terminal goes offline mid-shift?

    Partner terminals typically support store-and-forward for a bounded queue of EMV chip transactions when connectivity drops, replaying them when the terminal reconnects. Contactless and online-only schemes require live connectivity. Operator-side dashboards flag any store-and-forward backlog and the partner acquirer's clearing of it.

  8. 08

    Are refunds available on chip-and-PIN transactions?

    Yes. Refunds reverse the original authorisation through the same partner acquirer that cleared it. The operator triggers the refund from the platform dashboard (or the terminal itself, depending on the acquirer's flow); the customer doesn't need to re-insert the card. Operator-side controls require a reason code on every refund for audit.

  9. 09

    How are disputes handled?

    Disputes on chip-and-PIN transactions share the unified dispute queue with card-not-present chargebacks. Evidence-pack templates per vertical pre-fill the terminal ID, transaction cryptogram evidence, receipt copy and any refund history — reducing the manual work on representment. Card-present chargebacks are generally easier to defend than CNP because the chip cryptogram is strong evidence of physical card presence.

  10. 10

    Which schemes are supported on the chip-and-PIN side?

    Visa, Mastercard, Amex and Discover chip-and-PIN acceptance are supported on the vast majority of connected partner terminal estates. JCB, UnionPay and some regional schemes (Cartes Bancaires, Bancontact, Interac) are supported where the partner acquirer holds the relevant scheme membership and EMV certification.

  11. 11

    Can we mix chip-and-PIN with a fully mobile POS approach?

    Yes. Chip-and-PIN fixed terminals can coexist with SoftPOS / Tap-to-Phone on the same merchant record. Fixed terminals are typically used at the counter or the front desk; SoftPOS covers pay-at-table, mobile teams or pop-up sales. Both settle into the same reconciliation feed.

  12. 12

    Does chip-and-PIN lower chargeback exposure vs CNP?

    Yes, materially. Card-present chip-and-PIN transactions carry the strongest scheme-side evidence of physical card presence (chip cryptogram + PIN) and are treated as substantially lower risk by issuers. Chargeback rates on chip-and-PIN volume are typically a fraction of CNP rates for the same merchant vertical.

  13. 13

    How does the merchant see per-terminal performance?

    The platform dashboard breaks out authorisation counts, approval rates, average ticket size and refund / dispute rates per terminal ID, per store location and per acquirer. Multi-store merchants use this to spot underperforming locations or terminals that need firmware updates.

  14. 14

    Is chip-and-PIN suitable for high-value transactions?

    Yes. Chip-and-PIN is the standard for high-value card-present acceptance across most regions. Above the local contactless CVM threshold, the customer must enter a PIN — which is exactly the point of the flow for high-value transactions. Issuer approval rates on chip-and-PIN over high-value tickets are typically high because the PIN provides strong CVM.

  15. 15

    Which geographies is chip-and-PIN acceptance available in?

    Chip-and-PIN acceptance is available wherever the connected partner acquirer holds a licence and can supply EMV-certified terminals — across EU, UK, APAC and LATAM as a baseline, with additional geographies added as partner relationships expand. A coverage review confirms availability for the merchant's specific footprint before any commitment.

Related

Related on the topropay platform