Symptoms
Two pending entries appear after a single terminal payment.
Use the following observations to establish that this is the specific failure described here, rather than an unrelated outage or different account:
- Failing behavior: Two pending entries appear after a single terminal payment.
- Comparison to run: Compare merchant receipt and bank authorization references, not just displayed amount.
- Pass condition: Only one settled charge remains or duplicate is reversed through bank process.
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:
- Merchant retried authorization — investigate this first only if the local state or controlled comparison supports it.
- One entry is temporary hold — a second layer that may survive a simple restart and requires a targeted check.
- Duplicate capture is possible — investigate when the first two paths do not account for the observed behavior.
Before Making Changes
Do not assume a pending line is a final charge or submit repeated payments. 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: Compare merchant receipt and bank authorization references, not just displayed amount. 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 | Compare merchant receipt and bank authorization references, not just displayed amount. | 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 original receipt and wait for status update within bank's stated window. | This can expose or rule out merchant retried authorization without changing several settings together. |
| Inspect the deeper layer | Ask bank to distinguish authorization holds from settled captures. | Use the evidence to separate one entry is temporary hold from duplicate capture is possible; do not assume either is proven. |
If the local comparison is inconclusive, keep the current system unchanged while checking whether one entry is temporary hold is consistent with the evidence. If not, investigate duplicate capture is possible rather than applying every possible fix.
Use Beginner for reversible checks; use Advanced only when the comparison indicates a deeper fault. Two pending entries appear after a single terminal payment. Run a harmless test and write down the time, device/account, current status indicators and the exact difference from normal behavior. Compare merchant receipt and bank authorization references, not just displayed amount. Do not erase logs or reset the device yet. Keep original receipt and wait for status update within bank's stated window. 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. Contact merchant with transaction identifiers if an actual double charge posts. 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. Only one settled charge remains or duplicate is reversed through bank process. 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 merchant retried authorization, one entry is temporary hold and duplicate capture is possible separately. Compare evidence from the working and failing paths, and avoid interpreting a green status indicator as end-to-end proof. Compare merchant receipt and bank authorization references, not just displayed amount. Ask bank to distinguish authorization holds from settled captures. 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. Open a formal dispute only after gathering the correct references. 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. Only one settled charge remains or duplicate is reversed through bank process. 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 merchant retried authorization as certain before running the comparison: Compare merchant receipt and bank authorization references, not just displayed amount.
- Trying several changes at once, such as modifying one entry is temporary hold and duplicate capture is possible simultaneously, which makes the successful change impossible to identify.
- Ignoring the safety boundary: Do not assume a pending line is a final charge or submit repeated payments.
- Assuming that a status label or progress indicator guarantees the actual action completed; verify the outcome independently.
How to Verify the Fix
Only one settled charge remains or duplicate is reversed through bank process.
- Repeat the original failing action under equivalent conditions: Two pending entries appear after a single terminal payment.
- Run the control again: Compare merchant receipt and bank authorization references, not just displayed amount.
- Check the positive pass condition: Only one settled charge remains or duplicate is reversed through bank process.
- 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 bank to distinguish authorization holds from settled captures. Open a formal dispute only after gathering the correct references.
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: Compare merchant receipt and bank authorization references, not just displayed amount.
- Preserve the corrected behavior: Only one settled charge remains or duplicate is reversed through bank process.
- 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 merchant retried authorization.
Frequently Asked Questions
Does this symptom prove merchant retried authorization?
No. Start with the controlled comparison: Compare merchant receipt and bank authorization references, not just displayed amount. Only treat merchant retried authorization 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 bank to distinguish authorization holds from settled captures. That helps determine whether one entry is temporary hold or duplicate capture is possible fits the symptoms.
How do I know the repair actually worked?
Use this outcome, not just an on-screen status message: Only one settled charge remains or duplicate is reversed through bank process. Keep a record of the working state for future troubleshooting.