Mobile payment gateway
topropay is the pay payment gateway that puts every mobile wallet, card scheme and alternative method behind a single integration. Apple Pay and Google Pay buttons render on the same checkout, ride the same vault, settle through the same acquirer — and reach your finance team in the same ledger as everything else.
The short version
Mobile is where most checkouts now live, and it is where typing a card number is at its most painful. Apple Pay and Google Pay solve that — but adopting both, on web and in app, used to mean wiring up a separate payment provider per wallet, juggling certificates, and explaining to finance why the wallet payments cleared on a different schedule from the cards. The result was the same set of buyers paying through three different rails that did not agree on a single report.
topropay collapses that into one mobile payment gateway. A single integration accepts Apple Pay, Google Pay and direct card-form input on the same checkout, with the same tokenisation vault, the same routing engine and the same settlement path. From the shopper's side, the wallet UX is exactly what they expect on their device. From the merchant's side, every wallet payment lands alongside cards in one dashboard and one normalised ledger export.
Key benefits
Three outcomes show up first when a single integration replaces a per-wallet build.
Apple Pay and Google Pay sit on top of the same unified API. Switch them on from the dashboard, render the buttons your design system already ships, and start accepting wallet payments on the same flow you use for cards.
Device-bound tokens replace raw PANs at the checkout. Your origin never sees a card number, so the secure pay systems your CISO expects ship with the integration rather than as a separate project.
Smart routing scores each authorisation and sends the wallet payment to the acquirer most likely to clear it. Cascading retries handle soft declines without bouncing the shopper back to the checkout.
How it works
Four phases run inside the same authorisation request, so the shopper sees a single fast result instead of any of the moving parts behind it.
The shopper taps an Apple Pay or Google Pay button. The wallet returns a device-bound payment token to the page — at no point does your origin see a raw card number.
topropay decrypts the wallet payload inside a PCI DSS Level 1 vault and produces an internal token. Refunds, retries and recurring will all run against this token, never the original card.
Smart routing scores the transaction and picks the acquirer most likely to approve. Soft declines cascade to the next route in the same request, transparent to the shopper.
Approved authorisations clear through the scheme rails and settle into your existing acquirer accounts. Every wallet payment reconciles into the same normalised ledger as cards.
Wallet comparison
Both wallets ride the same integration on the platform. The table below summarises how each one is delivered — buyer surface, token model, authentication, settlement — so a single decision covers both.
Whichever wallet a buyer prefers, the back-end shape stays identical. The same routing engine picks the acquirer, the same vault stores the token and the same export feeds finance — so a team can support both an apple pay payment provider experience and a Google Pay flow without carrying two separate stacks.
Capabilities
Six capability bands cover the lifecycle of a wallet payment, from the button render on the page to the ledger entry your finance team reconciles against.
One request shape covers Apple Pay, Google Pay and card-form checkout, so engineering work scales with traffic, not provider count.
Reference button components for the wallet surfaces, plus headless flows when your design system owns the buttons end to end.
Apple Pay payloads and Google Pay tokens are vaulted as the same internal token type, with refunds, retries and recurring on the token only.
Selective Strong Customer Authentication runs only where the data and market call for it, keeping approval rates high without breaking PSD2.
Per-authorisation routing sends each wallet transaction to the acquiring bank most likely to clear it at the lowest cost.
Every wallet payment shows up alongside cards in the same dashboard and the same normalised ledger export.
Where it fits
A few of the most common patterns where Apple Pay and Google Pay buttons make a measurable difference on mobile.
Apple Pay and Google Pay buttons on the product page lift conversion on small screens, where typing a card number is the most fragile moment in the funnel.
Vault tokens drive recurring billing, so the wallet a user picked at sign-up keeps charging without re-prompting the shopper at renewal.
Wallet payments shorten the checkout on mobile, which is where most travel and ticketing sessions originate. Staged captures still work against the vault token.
One wallet integration covers buyers across browsers, devices and apps, so marketplace operators stop debating which wallet to support first.
Industry relevance
Wherever the checkout lives on a phone, the wallet buttons earn back the friction of card entry. These are the sectors the platform serves most often.
The platform serves mainstream and high-volume merchants, plus payment service providers reselling capacity downstream. Whichever vertical you are in, the wallet integration is the same: one mobile payment gateway, one report, one set of compliance signals.
Trust & compliance
Both wallet payloads and card-form inputs are vaulted under the same PCI DSS posture, so the compliance picture does not fragment when wallets are added.
For the deeper compliance posture see payment card industry PCI compliance; for the routing engine behind every wallet transaction see smart routing and cascading.
Common questions
A mobile payment gateway is the layer that lets a website or app accept payments from a mobile device — wallets like Apple Pay and Google Pay, card-form input, and other account-to-account rails — through a single integration. topropay acts as that gateway and the orchestration layer above it, so a single connection covers the buyer-facing surfaces and the acquiring underneath them.
The platform decrypts the Apple Pay payload inside its PCI DSS Level 1 vault, mints an internal token, and routes the authorisation through the acquirer most likely to approve. From the merchant's perspective, the same request shape is used for an Apple pay payment gateway flow and a card-form flow — only the input changes. Apple Pay payment processing therefore stays inside the same lifecycle as the rest of your card volume.
Yes. The payment gateway Apple Pay integration works on Safari and supported in-app surfaces (iOS, iPadOS, watchOS) using the standard Apple merchant identifier and domain-verification flow. Web integration uses the Apple Pay JS API on the front end and the platform's unified API on the back end, so the engineering shape of an Apple pay payment gateway integration is the same as accepting cards.
topropay sits between both. It is the Apple Pay payment provider that handles enrolment, domain verification, payload decryption and tokenisation, and it is the Apple Pay payment processor at runtime — routing the resulting authorisation through your acquirer of choice. Merchants do not need a separate Apple payment processor relationship; the platform delivers both roles through one contract.
Google Pay rides the same internal token model. When a shopper picks Google Pay, the wallet returns a tokenised payment method through the Google Pay API; topropay vaults it, applies your routing policy and submits the authorisation. The g pay payment gateway flow is identical in shape to the Apple Pay flow, which keeps the operations and finance teams reading one report rather than two.
Yes. A google pay payment gateway for website use is the most common entry point — drop the wallet button on the product or cart page and the same integration handles it. You can extend later to in-app surfaces without re-integrating anything on the back end; the unified API contract does not change.
Refunds and recurring charges run against the vault token, not the original wallet payload. That means the wallet a customer used at sign-up stays usable for renewals, partial refunds and merchant-initiated transactions; the rest of the apple payment processing lifecycle (capture, clearing, settlement) follows the same five-stage flow as cards.
Yes. Both wallets are designed as secure pay systems: the buyer authenticates on-device (Face ID, Touch ID, biometric, passcode) and the merchant only ever sees a token, never a raw card. Combined with the platform's vault and PCI DSS posture, the result is a secure and pay payment gateway flow that keeps card data outside your environment from end to end.
No. The apple payment system and the apple payment gateway pieces — enrolment, domain verification, decryption keys, settlement routing — are all delivered by the platform. Merchants register an Apple Merchant ID during onboarding, paste the domain into the dashboard, and the rest is handled by topropay.
Yes. The same pay payment gateway integration that handles Apple Pay and Google Pay also covers Visa and Mastercard cards, American Express where supported, local card schemes, account-to-account, SEPA online payments, ACH and a long list of regional methods. The shopper picks the method; the engineering layer does not change.
The integration degrades gracefully. If a wallet button cannot render — old browser, opted-out device, supported-market constraints — the same checkout falls back to card-form input on the same gateway, with no provider switch required and no re-integration on your side.
Book a discovery call. We scope an apple pay payment gateway integration on web and app, wire Google Pay alongside it, and show how both flow through the same vault, the same routing and the same reporting as the rest of your payments.
Related