PayU analytics: revenue by channel

Setup steps

1. In PayU, open Developers → Key and Salt and copy both.
2. In ProductLense, open Settings → Billing connections → PayU, paste them and set the mode.
3. In PayU Dashboard → Developers → Webhooks, add a webhook endpoint with the URL ProductLense shows after you save the connection (pattern https://api.productlense.app/api/webhooks/{provider}/{connection_id}).
4. Create one webhook for Successful and Failed payments and one for Refund, both pointing at the same URL.
5. ProductLense backfills 12 months of transactions and their refunds.

Credentials and permissions

Webhook

URL pattern, shown with your connection id after you save:

https://api.productlense.app/api/webhooks/payu/{connection_id}

Events: Successful, Failed, Refund

Verification: Payment webhooks: PayU’s SHA-512 reverse hash with your salt and merchant key. Refund webhooks are unsigned, so ProductLense fetches each refund from PayU before recording it.

What ProductLense reads

Customers

The payer’s email, else phone: PayU has no customer object.

Subscriptions

Not read: recurring (SI) charges arrive as payments.

Payments

Captured transactions as revenue; failed, dropped and cancelled ones are kept as failed.

Refunds

Refunds of each captured transaction, and every refund webhook, confirmed with PayU’s API.

Fees

mer_service_fee plus mer_service_tax when PayU reports them; otherwise an editable estimate of 2.36% (2% plus 18% GST).

What ProductLense never touches

• Never creates, changes, refunds or cancels anything: read-only API calls and incoming webhooks only.
• Never moves money, issues payouts, or reads bank account details.
• Never sees full card numbers; providers do not expose them.
• Never sends your customer data to the AI model: Ask and the daily insight see aggregates only.

Match payments to your users

Send your user id in udf5 and the ProductLense visitor id in udf4 of the payment request so revenue matches by id rather than email.

// Add to the fields you post to PayU, and include them in the request hash:
const fields = {
  key, txnid, amount, productinfo, firstname, email, phone,
  udf4: visitorId, // ProductLense visitor id
  udf5: user.id,   // your user id
  surl, furl,
};