Checkout payment

Checkout payment, one tap from done — on every surface your shoppers use.

topropay's checkout ships with express buttons, a thumb-first mobile surface and hundreds of payment methods. All of it sits behind a single API. Apple Pay, Google Pay, Click to Pay, BNPL, cards and local APMs route across your connected providers in under 300ms.

See the checkout Read the API docs
Total € 89.40 Pay G Pay Click to Pay or pay with card Pay €89.40
Express buttons up top. Local methods underneath.
1-tap
express checkout from saved methods
<300ms
perceived latency on mobile checkout
300+
payment methods configurable per market

Key benefits

Why express checkout outperforms the long-form alternative

Four outcomes show up again and again. They come from one thing: the checkout, the express buttons and the routing engine all share one layer.

  1. Speed

    Quick checkout from a single tap

    Returning shoppers complete checkout from one tap — no card form, no address re-entry. Apple Pay, Google Pay and Click to Pay surface as express checkout buttons inside the same checkout component; first-time shoppers fall through to a hosted card form built for thumbs.

  2. Coverage

    Every checkout payment method that fits the market

    Cards, wallets, bank rails, BNPL and crypto run through the same unified API. The method list re-orders itself per shopper's market, currency and device, so the highest-converting checkout payment method for that buyer sits at the top of the list.

  3. Conversion

    Mobile checkout designed for thumbs, not desktops

    Touch targets, keyboard handling, scheme detection and pay-sheet integration are tuned for mobile first. A mobile checkout that feels native — even when it isn't — converts visibly better than a checkout that was 'made responsive' from a desktop layout.

  4. Operations

    Routing and reconciliation behind the surface

    Behind every checkout authorisation is the same routing engine — per-transaction scoring, cascade through soft declines — and the same reconciliation feed. The checkout-services surface is the part the buyer sees; the orchestration behind it is what makes the surface earn its keep.

How it works

From shopper open to authorisation in three frames

Three stages: detect, authorise, confirm. All of it renders inside one checkout surface. No full-page redirects.

  1. 01 Detect

    The checkout reads the shopper

    On open, the checkout reads market, currency and saved methods, then orders the payment options accordingly — express buttons up top for returning buyers, local APMs surfaced per region for everyone else.

  2. 02 Authorise

    One tap, routed across the portfolio

    The shopper taps a button. The authorisation flows through topropay's unified API; the routing engine picks the best route across the connected providers; soft declines cascade silently to the next ranked acquirer.

  3. 03 Confirm

    Result back to the shopper in one frame

    Success or fail returns to the checkout in under a second, with the result and any next-step UI (3DS challenge if applicable, error message if hard-declined) rendered inside the same surface — no full-page redirect, no broken flow.

Express checkout buttons

The express checkout buttons surfaced from one component

You turn wallet and saved-method buttons on per market and per device. Below is the set that ships with the hosted checkout, shown as it looks in production.

  • Apple Pay iOS / Safari
  • Google Pay Android / Chrome
  • Click to Pay Visa, Mastercard, Amex
  • PayPal Global, wallet balance + cards
  • Link by Stripe (partner) Saved cards across merchants
  • Shop Pay (partner) Returning Shopify buyers

Brand names referenced are trademarks of their respective owners. Availability per market depends on the underlying provider's regional support; the dashboard exposes the live state for a merchant's contracted region and method mix.

Main use cases

Where a quick checkout earns its keep

Six kinds of merchant stress the same checkout in different ways. They range from mobile-first DTC to hotel express checkout at the property level.

  • E-com

    Direct-to-consumer commerce

    Mobile-first checkout with express buttons on the highest-traffic surface — DTC brands consistently see the conversion lift from a 1-tap path.

  • Subs

    Subscriptions and memberships

    Express checkout on the first sign-up plus network-token recurring billing on every renewal; one-tap reactivation if a member drops off.

  • Marketplaces

    Marketplaces and platforms

    Per-tenant checkout configuration so each seller gets the express-button mix that fits their buyer base, all on one orchestration layer.

  • Travel

    Travel, hospitality and bookings

    Hotel express checkout flows at the property level, staged captures across the booking lifecycle, and multi-currency capture for the inevitable last-minute change.

  • Ticketing

    Ticketing and live events

    Peak-load checkout that holds up under on-sale spikes; express buttons absorb the rush from shoppers who don't have time for a card form.

  • Mobile-first

    Mobile-first commerce and in-app

    Native iOS / Android SDKs surface the same express buttons inside in-app checkout — same routing, same vault, same reconciliation as the web.

Platform features

What's in the checkout services API

The moving parts inside the checkout, laid out as a list. Engineering and product can each find the rows they care about.

Hosted checkout
A drop-in checkout component that ships with express buttons, hosted card form, BNPL and APMs — minutes to live.
Embedded fields
Tokenised hosted card fields you can style inside your own page; PCI scope stays at SAQ-A while the surface is yours.
Express checkout buttons
Apple Pay, Google Pay, Click to Pay, PayPal and partner wallets surfaced from a single component, in the right order per shopper.
1-tap returning buyer
Saved network tokens surface as a single-tap option for returning shoppers — no PAN to retype, no second authentication if SCA isn't required.
Mobile pay sheets
Native iOS / Android pay-sheet integrations via the SDK; the in-app surface inherits the same routing engine as web.
Smart routing
Per-transaction scoring on BIN, scheme, currency and risk — every checkout authorisation runs through the same engine.
Cascade & retry
Soft declines cascade to the next ranked acquirer inside the same request, before the shopper ever sees an error.
3DS2 step-up
Selective challenges per transaction; the checkout handles SCA in-frame, no full-page redirect to the issuer.
Vault tokenisation
Card data captures into our PCI DSS Level 1 vault before it touches your origin; refunds and recurring run on tokens.
Webhooks
Signed, normalised checkout events into your SIEM, warehouse or order-management system — replay-safe, idempotent.
Industry callout

Hotel express checkout, from the room to the lobby

Hotels face a checkout problem that retail patterns don't fit. The folio settles on departure. The booking was authorised days or weeks before. And the guest expects to leave without queueing at the front desk. topropay's hotel express checkout uses tokenised authorisations across the whole booking. The folio settles from a 1-tap surface on the guest's phone, or from the property management system — against the same vault token that authorised the booking.

The day-to-day stays simple. Reception sees one dashboard view of every guest's folio and authorisation history. Finance sees one reconciliation feed across every property in the chain. The guest sees a checkout that takes seconds. Behind it all, the engine routes each capture across your acquirers like any other authorisation. The hotel part is only the UX.

Trust & compliance

Security posture you inherit through the checkout

The checkout is one of the most security-sensitive moments in a buyer flow. Here is the posture the platform carries for you.

  • PCI DSS Level 1

    Service-provider posture validated annually; the hosted checkout keeps your scope at SAQ-A even when the surface looks like yours.

  • SCA & 3DS2 in-frame

    Selective challenges handled inside the checkout surface; PSD2-compliant in Europe without breaking the conversion path.

  • Network-tokens-by-default

    Saved cards live as scheme network tokens, not PANs — re-issuance events don't break recurring or express flows.

  • Resilient by design

    Redundant acquiring zones and automatic failover absorb provider outages mid-checkout.

  • Licensed verticals only

    Licensed and regulated merchants only; grey- and black-market verticals are out of scope regardless of integration shape.

Ready to ship a faster checkout

Drop in the checkout, light up the express buttons.

A 30-minute walk-through covers the methods that fit your markets, the express buttons enabled per region and a sandbox to test against before any commercial commitment.

See the checkout Explore the platform

Frequently asked

Buyer questions about checkout payment on topropay

What buyers ask before they commit: what the terms mean, how it works on mobile, how the express buttons behave, and what it takes to drop the component in.

  1. 01

    What does 'checkout payment' actually cover on topropay?

    Checkout payment on topropay covers the visible surface (hosted checkout component, embedded fields, mobile pay sheets, express checkout buttons) and the orchestration behind it (routing, cascade, vault, reconciliation). One unified API connects both — a single integration replaces what would otherwise be a per-method front-end plus a per-provider back-end.

  2. 02

    How is the checkout payment gateway behaviour different from a single-acquirer gateway?

    A single-acquirer checkout payment gateway sends every authorisation to one acquirer. topropay's checkout sends each authorisation through the routing engine, which scores the route per BIN, scheme, currency and risk segment across the connected portfolio. From the integration's perspective the gateway surface is the same; under the hood it's a per-transaction decision rather than a static contract.

  3. 03

    What does the payment checkout look like on mobile?

    Payment checkout on mobile renders as a thumb-first sheet with express buttons on top (Apple Pay, Google Pay, Click to Pay), a hosted card form below, and local APMs sequenced underneath per region. Keyboard handling, touch targets and scheme detection are tuned for mobile first; the checkout mobile surface is not a responsive desktop layout, it's a separate design target.

  4. 04

    How does apple pay express checkout work specifically?

    Apple pay express checkout surfaces as a native Apple Pay sheet from a button rendered by the hosted checkout component. The user confirms with Face ID or Touch ID; the authorisation flows through topropay's routing engine on the same path as a card form authorisation. Behind the surface it's just another route the routing engine scores; on the surface it's a 1-tap experience.

  5. 05

    Are express checkout buttons configurable per market?

    Yes. Express checkout buttons are enabled per market and per device class from the dashboard. A US-facing checkout might surface Apple Pay, Google Pay, PayPal and Click to Pay; an APAC-facing one might emphasise wallets and bank rails instead. The component reads the configuration at render time.

  6. 06

    What's the difference between checkout express and 'quick checkout' as terms?

    'Checkout express' usually refers to the button-driven 1-tap flow surfaced via wallets and saved methods. 'Quick checkout' is a broader term — it can include express buttons, but also covers things like single-page checkouts, pre-filled address fields and tokenised returning-buyer flows. topropay's hosted checkout covers both senses of the term.

  7. 07

    How does checkout processing latency stay under 300ms on mobile?

    Checkout processing latency under 300ms on mobile is the sum of three things: an edge-served checkout surface, an authorisation routing decision under 200ms, and pay-sheet UI rendered natively on the device. The orchestration layer doesn't add a network hop the merchant's own checkout wouldn't already have — it replaces several with one.

  8. 08

    Does the platform offer easy checkout for low-code stacks?

    Easy checkout for low-code stacks usually means embedding the hosted checkout via a single script tag or an iframe, plus one webhook handler. Most merchants on Webflow, Wix, Framer or similar are live within a day. The SDK and hosted-fields path is reserved for teams that need full control of the visual surface and have engineers to maintain it.

  9. 09

    Can the platform support a hotel express checkout flow at the property level?

    Hotel express checkout flows are supported through staged captures, partial captures and tokenised authorisations across the booking lifecycle. The guest can settle their folio from a 1-tap surface on their phone or have the front desk push a tokenised charge through the operator portal — same checkout-services back-end either way.

  10. 10

    How does mobile checkout compare to the desktop surface?

    Checkout mobile and desktop share the same component and the same back-end, but the layout, default method order and pay-sheet integrations differ. Mobile prioritises express buttons and pay sheets; desktop tends to surface the card form earlier because shopper intent on desktop is often a planned, larger ticket.

  11. 11

    Are there checkout services beyond the hosted component?

    Beyond the hosted component, the platform exposes checkout services as APIs: tokenisation, 3DS orchestration, saved-method retrieval, dispute evidence and reconciliation. Merchants that build their own surface use these directly; merchants that drop in the hosted component get them implicitly.

  12. 12

    How is the checkout payment method selection actually made?

    Checkout payment method selection is driven by three inputs: shopper data (market, device, saved methods), merchant configuration (which methods are enabled per market) and a ranking function that scores each method's likely conversion at the top of the list. The buyer sees a sequenced list; the configuration that produced it lives in the dashboard.

Related

Related on the topropay platform