EPay Notification Not Received: A Troubleshooting Checklist

The buyer paid, but the order in your system stays unpaid. Usually the async notification never arrived, or it arrived and your system did not answer correctly. This page is a checklist for finding out which.

  • Async notification
  • notify_url
  • EPay V1
  • Updated

How notifications are sent

After a successful payment the platform sends a GET request to the notify_url from your order, with parameters in the query string. Once your system has verified the signature and processed the order, the page must output only success.

If the platform does not receive success, it retries automatically at increasing intervals. An occasional late notification is normal; one that never arrives needs investigating.

Checklist

CheckHow to confirm
The notify URL is publicly reachableIt must be a public http/https address, not localhost or a private IP. Try opening it from a phone on mobile data
No login requiredOpening the notify URL while signed out must not redirect to a login page
Not blocked by a firewall, CDN or WAFLook for GET requests to the notify path in your access log. If you use bot challenges, geo-blocking or crawler protection, exempt the notify path
GET requests are acceptedA route that only allows POST will reject the request
The response is only successNo HTML tags, spaces, line breaks or debug output
The signature verifiesA request that arrives but fails verification also looks like “not delivered”. See Fixing signature errors

The fastest test is your access log. No request in the log means the notification never reached your server, so look at networking and blocking. A request with no order change means the problem is verification or your own handler.

Notify paths of common systems

Existing systems usually generate the notify URL themselves. Use the paths below to search your access log or to exempt them in your reverse proxy:

SystemNotify path
Dujiaoka 2.x/pay/yipay/notify_url
Dujiao-Next/api/v1/payments/callback, entered manually as a full URL in the channel
ACG-Faka/user/api/order/callback.plugin-id
New-API/api/user/epay/notify, on the callback address or server address
One-Hub/api/payment/notify/an-id
Xboard / V2Board/api/v1/guest/payment/notify/EPay/an-id

Resend a notification

Once the problem is fixed, missed orders can be notified again in two ways:

  1. Call /api.php?act=notify yourself with trade_no or out_trade_no. Only paid orders can be resent. See Query & refund API.
  2. Contact official support with the order number and they will resend it.

/api.php is a server-to-server endpoint, so the public egress IP of the calling server must be on the allowlist first.

Two things that are easy to miss

Make your handler idempotent. The same order can be notified more than once; deliver only once per out_trade_no.

Do not deliver on the return redirect. Whether the buyer is sent back to your site depends on the payment channel, and some never redirect. Deliver only on the async notification.

For other errors see Troubleshooting; for protocol details see Signing and Async notification.

More integration docs

Get your merchant ID and key

Contact official support to open an integration app. Your gateway URL, pid and key are issued directly, with hands-on help during testing.

Contact support