What should your store do with a pending payment?

A customer pays, closes the banking window and returns later. Your store may know that an order exists without knowing that payment succeeded. Treating every return to the website as a paid order creates work for staff and can send goods before the transaction is confirmed.

Describe the states first

Write down what your chosen provider calls a pending, successful, failed or cancelled payment. Keep these distinct from fulfillment states such as packed or dispatched. A payment provider's vocabulary and actual merchant-account settings should guide the integration.

Make the waiting screen useful

For a Colombian store, a practical pending screen might show the order reference, the current payment status and how to ask for help. It should avoid instructing someone to pay again simply because a browser page did not update. Staff need the same reference so they can investigate without requesting card details.

Test the notification path

A provider notification can arrive after the browser session ends. It can also be repeated. Ask the developer to demonstrate that one confirmed payment updates the intended order once, that a repeated notice does not duplicate fulfillment and that an unresolved payment remains visible for review.

Wompi's Colombian site describes its own payment options; confirm account eligibility and current integration guidance directly with the provider. The checkout design does not settle tax or accounting treatment. Bring the provider name and a sample pending order when discussing an ecommerce improvement.