Symptoms
Card works for online purchases but terminal taps fail when the phone has no data service.
Use the following observations to establish that this is the specific failure described here, rather than an unrelated outage or different account:
- Failing behavior: Card works for online purchases but terminal taps fail when the phone has no data service.
- Comparison to run: Test in a trusted merchant setting with connectivity restored first.
- Pass condition: A valid tap succeeds under the card's supported connectivity conditions.
Why It Happens
Payment request approval, authorization and settlement are separate operations. A timed-out page does not prove a transfer was never initiated.
Treat these as competing hypotheses, not confirmed diagnoses. Their implications are different:
- Wallet token requires online refresh — investigate this first only if the local state or controlled comparison supports it.
- Offline spending limits exhausted — a second layer that may survive a simple restart and requires a targeted check.
- Device payment authentication not completed — investigate when the first two paths do not account for the observed behavior.
Before Making Changes
Avoid repeating declined taps without checking pending authorizations. A card authorization, bank posting and merchant order are different states. Treat the authoritative transaction reference and account ledger as evidence rather than assuming a loading spinner represents a failed payment. Write down the working configuration and, if available, export settings or create a test-only copy before changing account permissions, routes or file locations.
Make one change at a time, note the original value, and repeat the exact same test after each change. If the new outcome is worse, restore that single setting; a full reset would erase evidence and can create additional problems.
Problem-Specific Diagnosis
Begin with this controlled observation: Test in a trusted merchant setting with connectivity restored first. Record the result and time; a vague report such as “sometimes fails” cannot distinguish the three hypotheses.
| Check | What to do | What the result tells you |
|---|---|---|
| Compare a working path | Test in a trusted merchant setting with connectivity restored first. | If one controlled route works, the failed route is probably specific to a setting, permission, device, or service rather than a total outage. |
| Check the local state | Reconnect data securely and open the wallet to refresh card status. | This can expose or rule out wallet token requires online refresh without changing several settings together. |
| Inspect the deeper layer | Ask issuer whether offline contactless transactions are supported for this card. | Use the evidence to separate offline spending limits exhausted from device payment authentication not completed; do not assume either is proven. |
If the local comparison is inconclusive, keep the current system unchanged while checking whether offline spending limits exhausted is consistent with the evidence. If not, investigate device payment authentication not completed rather than applying every possible fix.
Use Beginner for reversible checks; use Advanced only when the comparison indicates a deeper fault. Card works for online purchases but terminal taps fail when the phone has no data service. Run a harmless test and write down the time, device/account, current status indicators and the exact difference from normal behavior. Test in a trusted merchant setting with connectivity restored first. Do not erase logs or reset the device yet. Reconnect data securely and open the wallet to refresh card status. Confirm the relevant account, cable, selected output, permission or status before saving changes. If it is already correct, leave it alone and proceed; do not force a change just to try something. Confirm NFC and default payment wallet settings. Change only this one condition after recording the old value. If it does not improve the result, restore the former value rather than layering additional guesses on top. A valid tap succeeds under the card's supported connectivity conditions. Repeat the same comparison used in step one. Record what improved, what remains unchanged and whether a reconnect or normal app restart changes the result. Stop here if the expected outcome is stable. Consider wallet token requires online refresh, offline spending limits exhausted and device payment authentication not completed separately. Compare evidence from the working and failing paths, and avoid interpreting a green status indicator as end-to-end proof. Test in a trusted merchant setting with connectivity restored first. Ask issuer whether offline contactless transactions are supported for this card. Focus on logs, state, permissions, protocol negotiation or version support relevant to this failure. Do not collect or share credentials, account tokens or unrelated private content. Check wallet token provisioning and terminal transaction reason with issuer. Use an isolated or test-only configuration where possible. Keep an explicit rollback path; do not weaken security, replace backup originals or bypass equipment protection to make one test pass. A valid tap succeeds under the card's supported connectivity conditions. Observe the behavior through the original trigger again. If the change does not produce this measurable result, undo that change and escalate with the recorded facts, rather than repeating disruptive reset attempts.Step-by-Step Troubleshooting
Capture the failing state
Check the first reversible condition
Apply the lowest-risk targeted fix
Retest and document
Distinguish the competing root causes
Inspect the deeper system layer
Run a second independent isolation test
Validate stability and rollback readiness
Solution Checklist
Common Mistakes to Avoid
- Treating wallet token requires online refresh as certain before running the comparison: Test in a trusted merchant setting with connectivity restored first.
- Trying several changes at once, such as modifying offline spending limits exhausted and device payment authentication not completed simultaneously, which makes the successful change impossible to identify.
- Ignoring the safety boundary: Avoid repeating declined taps without checking pending authorizations.
- Assuming that a status label or progress indicator guarantees the actual action completed; verify the outcome independently.
How to Verify the Fix
A valid tap succeeds under the card's supported connectivity conditions.
- Repeat the original failing action under equivalent conditions: Card works for online purchases but terminal taps fail when the phone has no data service.
- Run the control again: Test in a trusted merchant setting with connectivity restored first.
- Check the positive pass condition: A valid tap succeeds under the card's supported connectivity conditions.
- Recheck after a normal restart, reconnection or scheduled cycle only when it is safe and relevant.
A single passing attempt is useful but may conceal intermittent failures. Record whether the fix survives the triggering condition without requiring a daily workaround.
If the Problem Continues
Use the deeper comparison rather than repeating the first steps: Ask issuer whether offline contactless transactions are supported for this card. Check wallet token provisioning and terminal transaction reason with issuer.
Use authenticated bank or merchant support. Share only the reference, date and nonsecret status details they request; never hand over OTPs, full card data or a remote-control session.
If the issue affects money, alarms, shared business records, or protective power equipment, stop risky experiments and use the official administrator, provider or manufacturer channel.
Prevent Recurrence
- Keep a record of the previously failing condition: Test in a trusted merchant setting with connectivity restored first.
- Preserve the corrected behavior: A valid tap succeeds under the card's supported connectivity conditions.
- Keep payment receipts and approved security methods current, and review bank alerts through the official app rather than links in messages.
- Review configuration or hardware changes that could reintroduce wallet token requires online refresh.
Frequently Asked Questions
Does this symptom prove wallet token requires online refresh?
No. Start with the controlled comparison: Test in a trusted merchant setting with connectivity restored first. Only treat wallet token requires online refresh as a candidate until the evidence supports it.
What if the first two checks do not change anything?
Move to a different layer rather than repeating the same action: Ask issuer whether offline contactless transactions are supported for this card. That helps determine whether offline spending limits exhausted or device payment authentication not completed fits the symptoms.
How do I know the repair actually worked?
Use this outcome, not just an on-screen status message: A valid tap succeeds under the card's supported connectivity conditions. Keep a record of the working state for future troubleshooting.