Before you start
First ask official support to open an integration app. You will get the three values below; every system on this site uses the same set.
| Value | Notes |
|---|---|
| Gateway domain | The payment gateway from support, e.g. https://gateway-domain |
Merchant ID (pid) | Your app's merchant ID |
Merchant key (key) | Your app's key, used for MD5 signing. Keep it secret |
The official legacy Dujiaoka repository stopped being maintained in February 2026 and points users to Dujiao-Next. The two versions are configured differently, so follow the section for the one you run.
Legacy Dujiaoka (2.x)
Sign in to the admin panel and open 支付通道 (Payment channels). Three EPay entries are seeded by default: 易支付-支付宝 (Alipay), 易支付-微信 (WeChat Pay) and 易支付-QQ 钱包. Edit the one you need, or add a new entry if it was removed.
| Admin field | What to enter |
|---|---|
| 支付名称 (Name) | The name buyers see, e.g. Alipay |
| 商户 ID (Merchant ID) | pid |
| 商户 KEY (Merchant KEY) | The full order URL: https://gateway-domain/submit.php |
| 商户密钥 (Merchant secret) | key |
| 支付标识 (Pay code) | alipay (Alipay) or wxpay (WeChat Pay) |
| 支付方式 (Method) | 跳转 (Redirect) |
| 支付场景 (Client) | 通用 (All) |
| 支付处理路由 (Handler route) | /pay/yipay |
| 是否启用 (Enabled) | On |
The field people get wrong is 商户 KEY: Dujiaoka uses it as-is as the redirect URL, so it must be the full address ending in /submit.php, while the key goes into 商户密钥. Swapping them causes a signature error or a 404.
Use one channel for Alipay and one for WeChat Pay. Merchant ID, order URL and key are identical; only 支付标识 differs.
The notify URL is generated automatically as https://your-domain/pay/yipay/notify_url. You do not enter it anywhere; just make sure it is reachable from the public internet.
Dujiao-Next
- Open Payment Channels in the admin panel and add a channel.
- Set Provider Type to Epay and Channel Type to Alipay or WeChat.
- Set Interaction Mode to Redirect (page redirect via
/submit.php) or QR (API order via/mapi.php). - Under Epay Config, change Version to
v1first, then fill in the table below and save.
| Epay Config | What to enter |
|---|---|
| Version | v1 (the default is v2, so change it) |
| Gateway URL | https://gateway-domain/ |
| Merchant ID | pid |
| Merchant Key | key |
| Notify URL | https://your-domain/api/v1/payments/callback |
| Return URL | https://your-domain/pay |
Version must be v1. v2 uses an RSA key pair, which is not interchangeable with the MD5 key PoPoPay issues, and signing will fail.
With the QR interaction mode, Dujiao-Next calls /mapi.php from your server, so send your server's public egress IP to support for the allowlist first. Redirect mode does not need this.
Create one channel for Alipay and one for WeChat Pay. Everything is the same except Channel Type.
Test an order
- List a low-priced test product in your shop.
- Place an order with the payment method you just configured. You should land on the checkout page or see a payment QR code.
- After paying, return to the order page. If the order is marked paid and delivered automatically, the setup works.
If the payment went through but the order stays unpaid, the async notification did not arrive or failed verification. See the next section.
Common problems
| Symptom | Cause and fix |
|---|---|
| “Signature verification failed” after redirect | The key is in the wrong field or has stray spaces. On 2.x make sure key is in 商户密钥, not 商户 KEY; on Dujiao-Next make sure Version is v1 |
| 404 or blank page after redirect | On 2.x, 商户 KEY is missing /submit.php, or the gateway domain is wrong |
| “No product configured for payment method xxx” | That method is not enabled yet, or its code is wrong (WeChat Pay is wxpay, not wechat). If the code is right, ask support to enable it |
| Paid, but the order stays unpaid | The notification did not arrive. Make sure the notify URL is publicly reachable and not blocked by a firewall or CDN; on Dujiao-Next check that Notify URL ends in /api/v1/payments/callback. Then ask support to resend it |
| “Illegal request, add API IP to allowlist” | Dujiao-Next is using QR mode but your server IP is not allowlisted. Send the public egress IP to support, or switch to Redirect |
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