Google Pay
Type: SDK · Status: Available · Category: Ecommerce and payments
Requirement to start the integration: customer screenshots
Section titled “Requirement to start the integration: customer screenshots”To enable Google Pay on the ecommerce site, the customer must provide Reskyt with five screenshots of their implementation, one for each screen in the table. Reskyt uses them to handle the Google Pay validation. Without the screenshots the validation cannot be started.
The screenshots are taken on the customer’s ecommerce site, following the purchase flow.
| No. | Screen | When to take the screenshot |
|---|---|---|
| 1 | Item selection | When the user is browsing an item or service. |
| 2 | Pre-purchase screen | When the user is ready to make a purchase. |
| 3 | Payment method screen | When the user selects Google Pay as their payment method. |
| 4 | Google Pay API payment screen | When the user is shown the payment information they have saved to Google Pay. |
| 5 | Post-purchase screen | When the user has made a successful purchase. |
Android does not allow a screenshot of the Google Pay API payment screen. In that case, take a picture of the screen with another device.
Send the five images to your Reskyt contact, indicating which number in the table each one corresponds to.
Required credentials
Section titled “Required credentials”This module needs no configuration.
What it adds
Section titled “What it adds”Enables Google Pay as a payment method on Android. The payment is handled in the customer’s ecommerce checkout.
Prerequisites
Section titled “Prerequisites”The module has no configurable fields and does not require supplying credentials to Reskyt. The provider’s reference is the official Google Pay for developers documentation.
Who does what
Section titled “Who does what”The customer has Google Pay implemented on their ecommerce website, provides Reskyt with the five screenshots of that implementation, and maintains the checkout where the payment is resolved.
Reskyt manages the Google Pay validation using the screenshots received and enables the module in the app.
Impact on the app
Section titled “Impact on the app”Because it is a native SDK, after enabling it you must rebuild the app and resubmit it to the stores: a configuration change is not enough.
System permissions
Section titled “System permissions”The module requests no system permissions.
Data and privacy
Section titled “Data and privacy”The module does not collect or process payment data. The payment is made with the customer’s own ecommerce payment method.
Timeline and process
Section titled “Timeline and process”The process starts when Reskyt receives the screenshots from the customer.
- Reskyt receives the five screenshots and handles the Google Pay validation.
- Google reviews the application to enable Google Pay. The approximate time is around 7 days.
- In parallel, the app update is published on Google Play. The approximate time is around 7 days.
Both phases can run in parallel, so their times are not added together. The times are set by Google and are approximate: they are not a commitment by Reskyt.
Validation
Section titled “Validation”Once the app is updated, access the payment method from the app and test that it works.