This article covers the most frequently reported Tap to Pay issues and how to resolve them on both iPhone and Android.
Quick Diagnostic Checklist
Before diving into specific errors, verify:
- You are using iPhone XS+ (iOS) or an NFC-enabled Android 8.0+ device
- iOS is 15.4 or later (iPhone)
- NFC is enabled in Android Settings → Connections (Android)
- Aplauso app is up to date (latest version from App Store / Play Store)
- Your Stripe account is fully onboarded (Wallet tab shows "Connected")
- You have an active internet connection
- Location permission is granted (Android - required by Stripe Terminal)
Error: "Tap to Pay Not Available on This Device"
Cause: Your device does not meet the hardware or OS requirement.
Fix:
- iPhone: Must be XS or newer. iPad is not supported for Tap to Pay.
- iPhone: Update to iOS 15.4+ via Settings → General → Software Update.
- Android: Your device may not have NFC hardware. Check the spec sheet or Settings → Connections - if there is no NFC option, the hardware is absent.
Alternative: Use the QR Code tab on the Reward screen - guests can pay from any smartphone without NFC hardware on your end.
Error: "Reader Discovery Failed" or Endless Spinning
Causes & Fixes:
| Cause | Fix |
|---|---|
| No internet connection | Connect to WiFi or ensure mobile data is active |
| Stripe account not connected | Complete onboarding in Wallet tab |
| App cache issue | Force-close the app, reopen, and retry |
| iOS Tap to Pay entitlement issue | Delete and reinstall the app |
| Android: Location permission denied | Grant Location in Settings → Apps → Aplauso → Permissions |
Error: "Payment Declined"
Card declines originate from the guest's bank, not from Aplauso or your device.
Common reasons:
- Card does not support contactless transactions (some older cards require chip/PIN)
- Insufficient funds
- Card is frozen or expired
- Bank velocity limit reached (too many transactions in a short period)
What to do:
- Ask the guest if they have another card or can pay via Apple Pay / Google Pay.
- If they cannot pay contactlessly, direct them to scan your QR code - they can pay with any card on the web kiosk, including chip cards via 3D Secure authentication.
- Never retry a declined card multiple times in quick succession - this can further trigger bank fraud blocks.
Error: "Payment Intent Could Not Be Created"
Cause: The backend failed to create a Stripe payment intent.
Fixes:
- Confirm your internet connection is stable.
- Ensure your Stripe account is fully onboarded and charges enabled.
- Sign out and sign back in to refresh your auth token.
- Check Aplauso status at status.aplauso.io for platform outages.
Guest Card Is Not Reading (NFC Tap Not Detecting)
iPhone:
- The NFC reader on iPhone is at the top of the phone. Tell the guest to hold their card near the top third of the screen, not the center or bottom.
- Remove thick phone cases during testing - some cases impede NFC on older iPhone models.
Android:
- NFC antenna position varies by manufacturer. Common positions: top-center or middle of the back.
- Ensure NFC is enabled.
- Ask the guest to hold still for 1–2 seconds rather than tapping quickly.
App Crashes When Opening Device Tab
- Update the app to the latest version.
- Force-close and reopen the app.
- If the crash persists, uninstall and reinstall the app - your data is stored in the cloud and will sync back.
- Report the issue to support with your device model and iOS/Android version.
Transaction Completed but Tip Not in Wallet
- Allow up to 60 seconds for Stripe to process and the tip to appear.
- Pull down to refresh on the Wallet screen.
- If the tip still does not appear after 5 minutes, check the Stripe dashboard (Wallet → Open Stripe) under Payments to confirm whether the charge was captured.
- Contact support at support@aplauso.io with the approximate transaction time and amount.
Getting More Help
If none of the above resolves your issue, contact Aplauso support:
- Email: support@aplauso.io
- Include: your device model, OS version, app version (Settings → About), and a description of the error message