What to do when payment succeeds but an order stays pending

A debit alert confirms that money moved or was reserved at the bank, but it does not always mean the payment provider has returned a final successful transaction to the store. A network delay, an abandoned browser redirect, or a provider callback that arrives late can leave the order pending for a short period.

Keep the original order reference and return to that order instead of starting a second checkout. A new payment creates a separate transaction and can turn a temporary verification delay into a duplicate-charge case.

Open My account, choose Orders, and select the pending order. The Check payment action asks the configured provider for the transaction again and compares the returned reference, status, amount, and currency with the order before fulfilment can begin.

An exact comparison protects both the buyer and the store. A successful transaction for a different amount, currency, or reference must not release a digital item automatically. If the order reports a mismatch, keep the reference and contact support rather than paying again.

If the provider confirms the exact transaction, the order should move to paid and then into its stated delivery flow. Automatic stock can proceed without a staff handoff; manual or team products continue according to the delivery estimate shown on the listing.

If the provider still reports pending, wait briefly and recheck the same order later. If it reports failed while your bank shows a completed debit, open a support case. If the amount or currency does not match, the order remains safely held for review instead of being fulfilled against the wrong transaction.

Start support from the signed-in order whenever possible so the case remains connected to the product, amount, payment method, and order timeline. Include the store order reference, the non-secret provider reference, the amount, the time of payment, and the exact status shown on screen.

A screenshot can be useful after account numbers, card details, balances, QR codes, and personal notifications have been covered. Scrid support should not need the secret value used to authorise a payment. Keep replies in one case so payment checks and fulfilment updates form a single traceable history.

Manual review is appropriate when the provider and bank disagree, the transaction was completed for the wrong amount or currency, the same reference appears on another order, or a duplicate debit is reported. These cases should not be forced into automatic delivery because doing so can hide the original payment problem.

Support can compare the provider verification, callback history, order amount, and previous recheck attempts. If a refund or reconciliation is required, keep the order and case references until the provider or bank confirms the final outcome.