PayU
Merchant key, salt and the webhook.
PayU is one of the four gateways GoSell can take money through, on your account, settling straight to your bank.
Like PhonePe, PayU takes the customer to its own page and returns them afterwards, rather than opening a window over your store. There is nothing to configure for that.
Before you start
- Create a merchant account at payu.in and complete KYC.
- PayU gives you test credentials immediately and production ones after approval.
Getting your credentials
- PayU dashboard → Payment gateway → API keys (called Merchant key and salt on some accounts).
- Copy the Merchant key and the Salt.
- Test and production credentials are different. Note which pair you are holding.
Entering them
Integrations → PayU:
| Field | What it is |
|---|---|
| Merchant key | Identifies your account to PayU. |
| Salt | Signs every request and verifies every reply. Treat it as a password. |
| Mode | Test while trying it out, Live once approved. |
Leave either credential blank and PayU is not offered at checkout, so a half-finished setup cannot take a real order and fail on it.
The webhook
In the PayU dashboard, set the webhook or server-to-server callback URL to:
https://yourbrand.com/webhooks/payment/payu/This is what confirms the order, not the customer's return trip. A customer who pays and closes the tab still gets their order. Every call is hash-checked against your salt before it is believed.
Testing it
- In Test mode, place an order and pay with PayU's test card.
- Confirm the order moves to Paid without you touching it.
- Switch to Live, swap in the production key and salt, and place one real low-value order. Refund it from the PayU dashboard afterwards.
Test credentials left in place on launch day is the most common payment mistake there is. Everything looks like it works and no money ever arrives.
Still stuck? Message us on WhatsApp — we would rather answer than have you guess.