Skip to main content

Onboard Digital Wallets (Playbook)

Apple Pay and Google Pay transactions see 50%+ lower fraud and 3-5% higher auth rates than raw card entry. If you're not accepting them, you're leaving money on the table. This playbook gets you live in 2-4 weeks.

Timeline: 2-4 weeks. Faster if your processor has streamlined onboarding.

Workflow Overview​

PhaseKey Tasks
Processor SetupConfirm wallet support, Apple Pay Merchant ID, Google Pay console access
IntegrationHosted or custom checkout, Apple Pay + Google Pay code
TestingTest matrix (iOS, Android, desktop), all devices, refund flows
LaunchEnable production, track metrics (auth, fraud, conversion), optimize placement

Prerequisites: Processor with wallet support, Apple Developer account, Google Pay Business Console access, developer resources.

Trigger Criteria​

Use this playbook when:

  • You don't accept Apple Pay or Google Pay
  • Mobile conversion is below desktop
  • Auth rates on mobile are lagging
  • You want to reduce CNP fraud without adding friction

Prerequisites​

Before starting:

  • Active processor account with digital wallet support
  • Access to your payment gateway dashboard
  • Developer resources (or gateway handles integration)
  • Apple Developer account (for Apple Pay)
  • Google Pay Business Console access (for Google Pay)

Week 1: Processor Setup​

Step 1: Confirm Processor Support​

ProcessorApple PayGoogle PayNotes
StripeNativeNativeJust enable in dashboard
BraintreeNativeNativeMinimal config needed
AdyenNativeNativeEnable per merchant account
WorldpaySupportedSupportedMay need separate enrollment
First DataSupportedSupportedCheck terminal compatibility

Checkpoint: Processor confirms wallet support is enabled on your account.

Step 2: Apple Pay Merchant ID​

  1. Log into Apple Developer account
  2. Create Merchant ID (Certificates, Identifiers & Profiles)
  3. Generate Payment Processing Certificate
  4. Upload certificate to processor/gateway
  5. Domain verification (add file to /.well-known/)

Checkpoint: Apple Pay Merchant ID active, domain verified.

Step 3: Google Pay Setup​

  1. Register in Google Pay Business Console
  2. Request production access
  3. Configure merchant info (name, country)
  4. No certificate required (easier than Apple Pay)

Checkpoint: Google Pay production access approved.

Week 2: Integration​

For Hosted Checkouts (Stripe Checkout, PayPal, etc.)​

Most hosted checkouts auto-enable wallets. Verify:

  1. Check your checkout config
  2. Enable Apple Pay / Google Pay toggles
  3. Test on iOS (Apple Pay) and Android (Google Pay)

Checkpoint: Wallet buttons appear on mobile checkout.

For Custom Checkout​

Apple Pay Integration​

// Check if Apple Pay is available
if (window.ApplePaySession && ApplePaySession.canMakePayments()) {
  // Show Apple Pay button
}

// Create payment request
const paymentRequest = {
  countryCode: 'US',
  currencyCode: 'USD',
  total: { label: 'Your Store', amount: '10.00' },
  supportedNetworks: ['visa', 'masterCard', 'amex'],
  merchantCapabilities: ['supports3DS']
};

Google Pay Integration​

// Check if Google Pay is ready
const paymentsClient = new google.payments.api.PaymentsClient({
  environment: 'PRODUCTION'
});

// Create payment request
const paymentDataRequest = {
  apiVersion: 2,
  apiVersionMinor: 0,
  allowedPaymentMethods: [{
    type: 'CARD',
    parameters: {
      allowedAuthMethods: ['PAN_ONLY', 'CRYPTOGRAM_3DS'],
      allowedCardNetworks: ['VISA', 'MASTERCARD', 'AMEX']
    },
    tokenizationSpecification: {
      type: 'PAYMENT_GATEWAY',
      parameters: { gateway: 'yourgateway', gatewayMerchantId: 'yourId' }
    }
  }]
};

Checkpoint: Wallet buttons appear; test transactions succeed in sandbox.

Week 3: Testing​

Test Matrix​

ScenarioApple PayGoogle Pay
Safari iOSTestN/A
Chrome iOSN/ATest
Safari macOS (Touch ID)TestN/A
Chrome AndroidN/ATest
Chrome Desktop (with phone)N/ATest

Test Cases​

  • Successful payment on iOS device
  • Successful payment on Android device
  • Payment with saved card in wallet
  • Refund processes correctly
  • Wallet shows in transaction details
  • Auth rate tracking captures wallet type

Checkpoint: All test cases pass in production with real cards.

Week 4: Launch and Monitor​

Step 1: Enable in Production​

  1. Remove feature flags / enable for all users
  2. Ensure buttons appear on mobile and desktop (where supported)
  3. Monitor error logs for first 24 hours

Step 2: Track Metrics​

Set up reporting to compare:

MetricCard EntryApple PayGoogle Pay
Auth rateBaselineTarget +3-5%Target +3-5%
Fraud rateBaselineTarget -50%Target -50%
Checkout conversionBaselineTarget +5-10%Target +5-10%

Step 3: Optimize Placement​

Best practices for wallet buttons:

  • Above the fold on checkout
  • Before card entry form (not hidden below)
  • Equal visual weight to card option
  • On product pages for express checkout (optional)

Checkpoint: Wallets live in production; metrics tracking enabled.

Success Criteria​

You're done when:

  • Apple Pay and Google Pay both accepting live transactions
  • Metrics show auth rate improvement vs card entry
  • Mobile conversion stable or improved
  • No increase in support tickets

Scale Callout​

VolumeConsiderations
Under $100k/moHosted checkout with wallet support is fastest path; prioritize this over custom integration
$100k-$1M/moTrack wallet adoption rate; A/B test button placement; ensure both iOS and Android covered
Over $1M/moWallet-specific auth analysis; push wallets in marketing; consider express checkout on PDPs

Where This Breaks​

  • Processor doesn't support wallets. Switch processors or use third-party tokenization.
  • Apple domain verification fails. Check .well-known file is accessible; no redirects.
  • Low adoption after launch. Button placement issue; A/B test position and size.
  • Auth rate same as cards. Expected improvement may vary; still worth it for fraud reduction.
  • Desktop Safari users confused. Requires Touch ID Mac or iPhone nearby; consider tooltip.

Next Steps​

After wallets are live:

  1. Track adoption rate: What % of customers use wallets? Set targets for growth
  2. A/B test placement: Experiment with button position and size to drive adoption
  3. Add express checkout: Consider wallet buttons on product pages for one-click purchase
  4. Measure fraud impact: Compare fraud rates between wallet and card-entry transactions
  5. Enable PayPal/Venmo: If not already, consider additional wallet options