This task uses the merchant’s authenticated order and contact records as the source of truth. This guide focuses on how to distinguish attempts, pending outcomes, successful payments, failures and refunds.
Open the authoritative record
Start in Payments or Contacts and locate the exact order or person by safe reference, email and date. The aim is to distinguish attempts, pending outcomes, successful payments, failures and refunds. Do not rely on list position, a bank alert or a customer screenshot.
Read identity, offer and status together
Confirm the customer, offer, amount, currency and current payment or fulfilment state. Similar names and repeated attempts can belong to different records. A pending or failed attempt does not authorise delivery as a paid order.
Take only an available action
Use only controls that are visible on the correct record. The merchant order page supports authorised refunds but does not provide a general Mark fulfilled control. Keep dispatch or service-completion evidence in your own fulfilment process with the Selstack order reference.
Protect customer information
Share only the details needed to fulfil or investigate. Keep addresses, private messages and delivery links out of public notes and unrelated screenshots. Selstack support does not need passwords, OTPs or full payment credentials.
Confirm the downstream result
Reopen the order, customer portal or fulfilment state and check that it now reflects the intended action. Tell the customer what changed, what remains pending and when the next update will be available.
Example: Understand Order and Payment Statuses
A bank debit with a pending Selstack order remains pending until the provider produces a verified final result.
If Understand Order and Payment Statuses is not working
Do not ask for another payment or deliver twice while the original attempt is still unresolved.
Confirm the result
- The customer, offer, reference and status match the intended record.
- Fulfilment, refund or access action was taken only once.
- The order now shows the expected downstream result.
- No unrelated customer information was exposed.
When to ask Selstack for help
Contact official Selstack support when the saved result, status or resolved identity still conflicts with the intended record after one refresh. Include the business, page, time, safe reference and visible message. Do not include passwords, OTPs, recovery codes, full card details, BVN, NIN or unmasked bank documents.