Symptoms
Identity verification finishes but the merchant shows an unpaid order.
Use the following observations to establish that this is the specific failure described here, rather than an unrelated outage or different account:
- Failing behavior: Identity verification finishes but the merchant shows an unpaid order.
- Comparison to run: Check the bank transaction ledger and merchant order ID before repeating checkout.
- Pass condition: One order is confirmed and charged exactly once.
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:
- Browser blocks cross-site return state — investigate this first only if the local state or controlled comparison supports it.
- Merchant callback expired — a second layer that may survive a simple restart and requires a targeted check.
- Authorization succeeded but capture failed — investigate when the first two paths do not account for the observed behavior.
Before Making Changes
Do not submit duplicate payments while the first authorization is pending. 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: Check the bank transaction ledger and merchant order ID before repeating checkout. 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 | Check the bank transaction ledger and merchant order ID before repeating checkout. | 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 | Keep the original order tab open and complete one new verified login. | This can expose or rule out browser blocks cross-site return state without changing several settings together. |
| Inspect the deeper layer | Compare network trace outcome with merchant support without exposing card details. | Use the evidence to separate merchant callback expired from authorization succeeded but capture failed; do not assume either is proven. |
If the local comparison is inconclusive, keep the current system unchanged while checking whether merchant callback expired is consistent with the evidence. If not, investigate authorization succeeded but capture failed rather than applying every possible fix.
Use Beginner for reversible checks; use Advanced only when the comparison indicates a deeper fault. Identity verification finishes but the merchant shows an unpaid order. Run a harmless test and write down the time, device/account, current status indicators and the exact difference from normal behavior. Check the bank transaction ledger and merchant order ID before repeating checkout. Do not erase logs or reset the device yet. Keep the original order tab open and complete one new verified login. 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. Allow required payment-site redirects for the trusted merchant. 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. One order is confirmed and charged exactly once. 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 browser blocks cross-site return state, merchant callback expired and authorization succeeded but capture failed separately. Compare evidence from the working and failing paths, and avoid interpreting a green status indicator as end-to-end proof. Check the bank transaction ledger and merchant order ID before repeating checkout. Compare network trace outcome with merchant support without exposing card details. 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. Ask merchant to reconcile authorization and capture using the reference number. 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. One order is confirmed and charged exactly once. 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 browser blocks cross-site return state as certain before running the comparison: Check the bank transaction ledger and merchant order ID before repeating checkout.
- Trying several changes at once, such as modifying merchant callback expired and authorization succeeded but capture failed simultaneously, which makes the successful change impossible to identify.
- Ignoring the safety boundary: Do not submit duplicate payments while the first authorization is pending.
- Assuming that a status label or progress indicator guarantees the actual action completed; verify the outcome independently.
How to Verify the Fix
One order is confirmed and charged exactly once.
- Repeat the original failing action under equivalent conditions: Identity verification finishes but the merchant shows an unpaid order.
- Run the control again: Check the bank transaction ledger and merchant order ID before repeating checkout.
- Check the positive pass condition: One order is confirmed and charged exactly once.
- 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: Compare network trace outcome with merchant support without exposing card details. Ask merchant to reconcile authorization and capture using the reference number.
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: Check the bank transaction ledger and merchant order ID before repeating checkout.
- Preserve the corrected behavior: One order is confirmed and charged exactly once.
- 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 browser blocks cross-site return state.
Frequently Asked Questions
Does this symptom prove browser blocks cross-site return state?
No. Start with the controlled comparison: Check the bank transaction ledger and merchant order ID before repeating checkout. Only treat browser blocks cross-site return state 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: Compare network trace outcome with merchant support without exposing card details. That helps determine whether merchant callback expired or authorization succeeded but capture failed fits the symptoms.
How do I know the repair actually worked?
Use this outcome, not just an on-screen status message: One order is confirmed and charged exactly once. Keep a record of the working state for future troubleshooting.