Documentation Index
Fetch the complete documentation index at: https://integration.wpay.com.au/llms.txt
Use this file to discover all available pages before exploring further.
PAN_ONLY and CRYPTOGRAM_3DS authentication methods are supported for Google Pay.
PAN_ONLY- the card is stored on file within your customer’s Google Account and not bound to an Android device.CRYPTOGRAM_3DS- the payment credentials are bound to an Android device.
Web (Embed)
On the web, Google Pay can be easily integrated both with and without Embed. In both offerings, the need to sign up for a Google Developer account has been removed, reducing additional financial and maintenance costs.| Using SDK (Embed) | Without SDK | |
|---|---|---|
| Google Developer account required? | No | No |
| Customization & Theming? | Limited | Full |
| Integrated with Checkout Flow? | Yes | Optional |
Mobile (Android)
On Android, Google Pay can be easily integrated both with and without the SDK. In both offerings, the need to sign up for a Google Developer account has been removed, reducing additional financial and maintenance costs.| Using SDK | Without SDK | |
|---|---|---|
| Google Developer account required? | No | No |
| Customization & Theming? | Limited | Full |
| Integrated with Checkout Flow? | Yes | Optional |
Recurring payments
This is in limited release and is being made generally available soon.