This task uses the merchant’s authenticated order and contact records as the source of truth. This guide focuses on how to verify payment, complete delivery in the business fulfilment process and retain evidence against the Selstack order reference.
Start from a paid Selstack order
Open Payments and confirm the order reference, successful status, item, customer and amount. A pending attempt or customer screenshot does not authorise fulfilment.
Use your fulfilment process
Prepare the physical item, perform the service or send the agreed hand-off using the order reference. Keep dispatch, delivery or completion evidence in the operational system your business uses.
Understand the current boundary
Selstack’s merchant order detail currently includes the financial record and an authorised refund action, but it does not provide a general Mark fulfilled control. Do not claim Selstack has recorded completion when it has not.
Tell the customer what happened
Send accurate tracking, access, appointment or completion information through the agreed channel. Keep private customer details out of public comments and unrelated tickets.
Troubleshoot a disputed delivery
Match your proof to the exact Selstack order reference and timeline. If a refund is appropriate, use the original order action rather than sending money to replacement details supplied in a message.
Example: Record and Complete Order Fulfilment
Use Selstack order DI-123 to label dispatch proof in your courier or service record, because the merchant page has no general Mark fulfilled action.
If Record and Complete Order Fulfilment is not working
If delivery is disputed, compare proof, address and timeline against the exact order before considering the authorised refund route.
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.