← Payment methods

Mobile wallets

Google Pay

Tokenized contactless payments on Android devices

Google Pay works on every contactless-enabled Surfboard terminal and on online checkout.

Accepted on every Surfboard channel, in every market we acquire In-storeOnlineSoftPOSUnattended
Google Pay

About Google Pay

Google Pay is a mobile wallet that tokenizes the customer's underlying credit or debit card on Android devices. Like Apple Pay, it processes as a card transaction with strong device-level authentication. Surfboard supports Google Pay across every contactless terminal and on hosted/embedded online checkout.

When to enable Google Pay

Always enable. Google Pay drives higher online conversion and faster in-store checkout — particularly in markets with high Android share like Eastern Europe and parts of Asia.

Customer base

Android device users globally. Higher penetration in markets where Android dominates.

What merchants build with Google Pay

Common use cases where partners and merchants enable this method through Surfboard.

Faster contactless checkout in retail

Higher conversion rates on online checkout

Tap to Pay on Android via SoftPOS

Subscription and recurring billing

Unattended self-checkout flows

How to accept Google Pay on Surfboard

Google Pay runs on the same Payment Methods system as every other method on Surfboard. Enable it per merchant, store, or terminal — through the portal or the API, no re-deployment required.

1

Enable in the portal or via API

Partners flip Google Pay on for their merchants in the Partner Portal, merchants enable it for their own stores in the Merchant Portal, and developers can do the same programmatically through the Payment Methods API. Surfboard handles scheme registration where required.

2

Available everywhere

Becomes available immediately on the channels Google Pay supports — in-store terminals, online checkout, SoftPOS, and unattended where applicable.

3

One settlement

Google Pay transactions roll into the same settlement reports as every other payment method on the platform — no separate reconciliation pipeline.