A checkout attempt is not the same as a successful payment. Selstack statuses help merchants decide whether to wait, ask the customer to retry or begin fulfilment without relying on screenshots or debit alerts alone.
Treat successful as the fulfilment signal
Confirm the successful or paid state in your own Selstack Payments area and verify the amount and offer before delivery.
Give pending transactions time
Pending means the final result is not yet confirmed. Avoid duplicate fulfilment and ask the customer not to create repeated attempts unless the original result becomes final or support advises a retry.
Handle failed or cancelled attempts clearly
Explain that no successful payment was recorded and provide the current canonical link. Never ask the customer to email card details or one-time codes.
Escalate with safe references
When a status does not resolve, collect the Selstack reference, time, amount and non-sensitive error message. Send those details through official support.
Review Payment Pending, Failed or Successful: What Each Status Means before publishing
Match status, reference, amount, customer and offer before acting.
Avoid this: Do not fulfil from a bank alert, screenshot or customer message when Selstack still shows pending or failed.