Understand how Selstack records references, timestamps, final statuses, customer identity and one authorised resolution path, what requires review and how to reach a fast answer that avoids duplicate fulfilment or duplicate refunds.
Selstack separates checkout attempts, paid orders, wallet balances and payout activity so merchants can act from confirmed records rather than screenshots or assumptions.
Start with the recorded transaction
Open the relevant Selstack order, payment or wallet entry and match the reference, customer, amount, currency, gateway and current status. A bank alert or customer screenshot can support an investigation, but it does not replace the platform record or authorise fulfilment, refund or payout action.
Keep each amount in its own currency
For this topic, pay attention to references, timestamps, final statuses, customer identity and one authorised resolution path. Preserve the customer-facing amount, fees, merchant remittance and wallet credit as separate labelled values. Do not overwrite a recorded amount with a hand-calculated conversion or describe pending funds as available cash.
Wait for final states before acting
Pending payments, verification reviews, balance holds and provider callbacks need a defined waiting path. Refresh the canonical record once, note the time and avoid duplicate submissions. Act only when the status and available controls support the next step.
Resolve exceptions through the original record
Use the order or payout record that created the issue. Check for an existing refund, withdrawal or provider attempt before creating another. Keep customer communication factual: say what Selstack currently shows, what is being checked and when the next update will be given.
Protect sensitive financial information
Never ask for passwords, OTPs, full card details or identity numbers in ordinary email, chat or a custom form. Share only safe references and masked evidence with official support. Changes to payout identity, destination or permissions deserve additional verification and an audit trail.
Reconcile and prevent recurrence
A complete review should explain what the customer paid, what the provider confirmed, what Selstack credited and what remains pending or disputed. The intended outcome is a fast answer that avoids duplicate fulfilment or duplicate refunds. Record the lesson in the operating process and avoid assuming two bank alerts always represent two completed Selstack orders.
Put Investigate Duplicate Payment Attempts Safely into practice
Two attempts from one email need separate references and final statuses; fulfil only each genuinely successful order once.
If Investigate Duplicate Payment Attempts Safely breaks down
If the customer reports two debits but Selstack has a pending attempt, preserve both references and contact support before refunding or retrying.
Final checks for Investigate Duplicate Payment Attempts Safely
- The active business, customer or transaction is the intended one.
- The public promise and internal process describe the same outcome.
- Amounts, currencies, dates and statuses are read from their labelled Selstack records.
- No password, OTP, full card detail or identity number is copied into ordinary notes or messages.
- An owner and a clear next review point are recorded for anything still pending.
What good looks like
a fast answer that avoids duplicate fulfilment or duplicate refunds. The main mistake to prevent is assuming two bank alerts always represent two completed Selstack orders.