Abandoned cart but payment successful

Topic summary

Issue: Two payments processed via Yoco (South Africa) appeared as abandoned checkouts in Shopify across different stores.

Context: Abandoned checkouts typically occur when customers do not reach the final “Thank you” page, which is when Shopify considers the checkout complete.

Recommended steps:

  • Confirm with the third‑party payment provider (Yoco) that the payments were received.
  • For confirmed payments, create a draft order in Shopify and mark it as paid to proceed with fulfillment.

Outcome: The merchant identified a temporary outage on the Yoco gateway causing the mismatch between successful payments and abandoned checkouts. The gateway issue appears resolved.

Status: Resolved, with monitoring implied for future checkouts.

Key terms:

  • Abandoned checkout: A checkout that was started but not completed in Shopify.
  • “Thank you” page: The final confirmation page signaling a completed order.
  • Draft order: A manually created order in Shopify to record payment and enable fulfillment.
Summarized with AI on December 28. AI used: gpt-5.

Any Shopify/Yoco customers here?

We have now had two payments go through on two different Shopify stores ( we use Yoco payment gateway in South Africa) but it ends up as an abandoned checkout? Please help - how do we resolve this?

Hi @HCGGSJTV ,

Thank you for reaching out to the Community! I’d be happy to provide some assistance with this request, to ensure it gets resolved.

In situations like these, it’s likely that the customer didn’t complete the full checkout process. Customers must see the ‘Thank you’ page to ensure their payment has been successfully processed. To resolve this, you will want to confirm with your third-party payment provider (i.e Yoco) that the payment was received.

If confirmed, you can then simply create a draft order and mark it as paid to begin fulfilling it!

Please let me know if you have any other questions.

1 Like

Thanks we have discovered the payment gateway we used was down for a bit which created this issue. It’s resolved now (I hope).