Skip to main content

How do I resolve issues with online payments?

E
Written by Emira Sibic

Online payment issues can be frustrating, especially when the payment process gets stuck on an endless loading screen or payments to a specific merchant only work occasionally. This article provides a step-by-step troubleshooting guide and explains how you can effectively resolve such issues.

Common Causes of Payment Problems

Endless Loading Screen: If the payment process fails to complete—regardless of your browser, device, or account—the problem is often due to the merchant’s payment processing system. The card usually works fine, but the payment process on the merchant’s site isn’t completing correctly.

Occasional payment issues: If payments to a specific merchant only go through sporadically, this also indicates a problem with the merchant’s payment processing.

Troubleshooting Steps

Check the card’s functionality: - Test your card with other merchants to ensure it’s working properly. This helps narrow down the problem to the affected merchant.

Document the problem: - Note whether the problem occurs only at a specific merchant and whether it works intermittently. This information is important to help the merchant troubleshoot the issue.

Contact the merchant: - Inform the merchant about the problem and let them know that your card works without issues at other merchants. Ask the merchant to check their payment processing system.

Additional Tips

Try a different browser or device: Although the problem is usually on the merchant’s end, switching browsers or devices can help in rare cases.

Be patient: Some payment issues may be temporary and resolve on their own.

Conclusion

Most online payment issues, such as endless loading screens or sporadic errors, are caused by the merchant’s payment processing system. By following the steps above, you can narrow down the problem and help the merchant resolve it. If the problem persists, contact the merchant’s customer support or your bank.


last updated on October 21, 2026

Did this answer your question?