Background
This is the task to add native support for GPay into the Android Wikipedia App in partnership with fr-tech. Adding Native payment method support was one of the proposed enhancements identified for improving donor experience in the apps. Fr-tech and the iOS team have already added support for ApplePay. Adding support for Google / Apple Pay was also a request in the 2022 Wishlist.
Requirements
- Entry points for flow: 1) From the "Donate" option in settings 2) from an in-app banner
- An option to "Donate with GPay" or via "Other payment method" should be presented when tapping Donate
- The GooglePay option or any branding should not be visible if the user doesn't have GooglePay set-up or is restricted for compliance reasons. In this case, the user should be sent directly to donate.wikimedia.org
- Tapping "Donate with GPay" should launch the Native Donation form
- The Native Donation form should have functional parity with iOS's native donation form
- Array of amounts
- Cursor should be not be active on Amount entry initially
- Choosing an amount button autofills that amount into the amount field.
- Error message for when an amount is below the minimum accepted donation amount (Match donate.wikimedia.org)
- Error message for when an amount is above $25,000 USD (Match donate.wikimedia.org)
- Checkbox for transaction fee I'll generously add X to cover the transaction fees so you can keep 100% of my donation.
- Choosing to pay transaction fees automatically adds that amount into the amount field
- Checkbox for recurring donation Make this a monthly recurring donation.
- Checkbox for email opt-in Yes, the Wikimedia Foundation may send me an occasional email.
- "Donate with GPay" button should use pre-packaged branded button from Google
- Links below the donation form should be:
- After donating via GPay, show a Thank you message in-app (on article or screen that they started on before clicking into Settings or on the banner)
- Tapping "Other payment method" should launch the existing link used in the app to donate.wikimedia.org
- Users should not be able to change or remove the currency within the input field. It should be hard-coded based on location.
Technical notes
- The donation flow should be presentable from any context.
- We will not keep any local information about donation history. In the future, we may want to record a donation that has occurred to facilitate showing donations in the Contributions module, but that will require legal approval.
- This feature must work well with Dynamic Type and Voice Over.
How will we know we are successful?
Report on specific metrics for GPay:
- Indicator: 4.0% average CTR per unique user
- Indicator: 30% higher donation completion rate (Success rate %) for donations made through Native GPay as compared to web view donations (all payment types)
- Indicator: 25% increase in donation completion rate (Success rate %) for all donations made in Android app during campaign as compared to previous year
- Curiosity: What percentage of users use native payment GPay compared to GPay on Web?
- Curiosity: How did the share of GPay donations as a portion of all Android donations change? (compare to last campaign, or before and after of Apps Menu donations)
- Guardrail: Abandonment rate is no more than 25%
Designs:
References:
- Brand guidelines from Google https://developers.google.com/pay/api/android/guides/brand-guidelines
- Can be based on ApplePay general flow (ApplePay Parent task with designs: T288285, figma)
- Also consider existing Android Banner/Donation flow designs: Figma
Release and Testing
- End of April/Early May - internal testing via APK, especially for Japanese/Japan and Spanish/Spain
- 13 - 27 May: Low-traffic external exposure: Release on Japanese and English Wikis, geolimited to Japan T363782, and to Beta testers everywhere
- 3 - 7 June - Release to everywhere in production
- May 28 - June 30: High-traffic exposure during Q4 App Campaigns (Japan will run May 28 - June 25, Spain will run June 3 - June 30)
