A payment gateway connects website, checkout, transaction processing and status return. This troubleshooting article does not replace the payment widget product page.
Identify the symptom
The customer may not reach checkout, the payment may be declined, the status may be unknown or the customer may report a charge. Each symptom needs a different check.
Where the issue can happen
The cause may be website, widget, customer bank, network or risk checks. Do not promise success or refund without confirmed status.
Support diagnostics
| Symptom | Check | Customer response |
|---|---|---|
| form did not open | browser, link, order | retry or send link |
| payment declined | failure category | explain next step |
| unknown status | operation log | do not fulfil yet |
Developer checks
Order ID, callback, mobile checkout, repeated clicks and timeout handling. For card flows, see card payments.
Money left the account but the order is unpaid
This gap usually means the charge went through while the final status never reached your system. Check the operation log: if the payment is confirmed, fulfil the order manually and fix status handling. If there is no confirmation, wait for the final status and hold fulfilment — funds on an unconfirmed operation are returned under the provider's rules.
Reducing repeated errors
Test checkout, collect symptoms, store statuses and use a demo payment before launch.
When to switch payment gateway
A switch makes sense when declines repeat across different customers and their banks do not explain them, when the payment methods you need are missing, or when statuses arrive late and orders have to be reconciled by hand. Before migrating, collect decline statistics by category — the same data helps when connecting a new solution.
If you are choosing a payment gateway for your website and want to start accepting online payments, take a look at the MulenPay payment gateway.
FAQ
What is a website payment gateway?
It connects website, checkout, transaction handling and status return.
How is a widget different from redirect?
A widget stays within the site journey; redirect sends the customer to a hosted payment page.
Why do payment errors happen?
The cause may be website, network, customer bank, operation data or risk checks.
What should support do with unknown status?
Check the operation log and avoid fulfilment without confirmation.
