Fix · Payments

Payment succeeded but my site never gets the callback (Hesabe, KNET or another gateway)

Blocks your workKuwait and GulfNot checked against the vendor's current screens

What you may see

The customer paid, the order stays pending
The gateway says success but nothing arrives in my logs
It never works in testing on my computer

Most likely cause

The gateway cannot reach the address it should call (a local address, a protected or wrong route), or the route refuses what it sends.

Check first (about two minutes)

Is the callback address public on the internet (not localhost, not behind login)? Try opening it from a phone on mobile data.
Look in the gateway dashboard: is there a record of the call and its answer? (the place may be labelled differently)

The fix prompt

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

The exact error or what you see

What you did before it happened

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a very careful senior engineer who knows online payments (including payment gateways used in Kuwait) and explains them to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

Menu and button names change over time. If you cannot find a button or page I mention, say so and tell me what to look for instead of guessing.

I am in Kuwait. If the service has a Kuwait or Gulf rule or option that matters here (for example KNET, Arabic right-to-left text or local time), take it into account.

THE PROBLEM
Payment succeeded but my site never gets the callback (Hesabe, KNET or another gateway)

THE EXACT ERROR OR WHAT I SEE
[paste the exact error here]

WHAT I DID BEFORE IT HAPPENED
[write in a few words what you did before it happened]

MOST LIKELY CAUSE
The gateway cannot reach the address it should call (a local address, a protected or wrong route), or the route refuses what it sends.

DO THESE STEPS, IN THIS ORDER
1. Find the code that creates the payment (which return and callback addresses it sends) and the route that receives the answer.
2. Check the addresses use the live domain over https (not localhost, not a preview address) and are allowed by any login or firewall rule.
3. Log (without secrets) every incoming call with its time, status and a short reason, so a missing call is visible.
4. Make the receiving route verify the payment with the gateway (ask the gateway for the status) rather than trusting the call alone, and make repeated calls safe.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- A small test payment ends with the order marked paid once, and the log shows the call and its check.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not mark an order paid just because the customer reached a "thank you" page.
- Do not use real customer money or real orders for testing.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Find the code that creates the payment (which return and callback addresses it sends) and the route that receives the answer.
Check the addresses use the live domain over https (not localhost, not a preview address) and are allowed by any login or firewall rule.
Log (without secrets) every incoming call with its time, status and a short reason, so a missing call is visible.
Make the receiving route verify the payment with the gateway (ask the gateway for the status) rather than trusting the call alone, and make repeated calls safe.

Do not do this

Do not disable signature or amount checks to make the callback pass.
Do not mark an order paid just because the customer reached a "thank you" page.
Do not use real customer money or real orders for testing.

Try another entry

Payment succeeded but my site never gets the callback (Hesabe, KNET or another gateway)

What you may see

Most likely cause

Check first (about two minutes)

The fix prompt

Steps

Do not do this

Related

How can we help?