🍏 Apple Pay & 🟩 Google Pay Test Guide#
Below are the recommended test scenarios for Apple Pay and Google Pay integration in UseePay's sandbox environment.
🧪 Test Cases#
Via Email#
| Card Number | Expiry | Email Address | CVV | Expected Result |
|---|
| Any valid card | 11/2027 | (no email filter) | 340 | ✅ success |
| Any valid card | 11/2027 | decline@useepay.com | 221 | ❌ failed |
| Any valid card | 11/2027 | pending@useepay.com | 111 | ⏳ pending |
Via Transaction Amount#
| Card Number | Expiry | Amount | CVV | Expected Result |
|---|
| Any valid card | 11/2027 | (any) | 340 | ✅ success |
| Any valid card | 11/2027 | 77.77 | 221 | ❌ failed |
| Any valid card | 11/2027 | 66.66 | 111 | ⏳ pending |
🍏 Apple Pay Testing Notes#
✅ Use a Sandbox Apple ID and Apple’s official sandbox cards.
These cards support various test scenarios.
💡 In production, use a real Apple Pay account tied to a non-mainland China bank card.
You may use a sandbox Apple ID in production only for connectivity testing, but real transactions will fail.
🟩 Google Pay Testing Notes#
1.
Use a Google account and add test cards:Refer to Google’s test suite:
https://developers.google.com/pay/api/web/guides/resources/test-card-suite
2.
Test environment supports:Visa, Mastercard, Discover, Amex
PAN_ONLY and CRYPTOGRAM_3DS auth methods
Shipping to: US, AU, BR, CA, HK, JP, PL, RU, SG
3.
⚠️ In production, use REAL credit cards. Test cards only work in sandbox.
✅ Test Scenarios to Cover#
🔗 References#
Apple Pay testing instructions: sandbox and production flow guidelines :contentReference[oaicite:1]{index=1}
Google Pay test cards & environment support :contentReference[oaicite:2]{index=2}
ℹ️ Tips#
Always test all three result flows (success, failed, pending).
Sandbox vs production environments behave differently—test both.
Ensure HTTPS and proper environment setup for both Apple Pay and Google Pay.
Modified at 2025-07-15 07:12:02
