Connect PayU

1Find your Merchant Key and Salt

picoask reads your transaction reports using PayU's Key + Salt — the same pair PayU already issued you. The Salt is a signing secret; picoask only ever signs read-only reporting calls with it and never charges, refunds or moves money.

• Sign in at merchant.payu.in and switch to Live Mode.
• Open Developer in the left sidebar, then the API Details tab.
• Copy your production Merchant Key and Merchant Salt.

If you're on a legacy PayUmoney-only account rather than the current PayU dashboard, the reporting API isn't available — check with PayU that your account is on the current platform.

2Connect in picoask

In your project's Integrations tab, choose PayU → Connect and fill in:

• Merchant Key — from step 1. It signs the read requests and scopes your data in the warehouse.
• Merchant Salt — from step 1.
• Environment — leave as live for production numbers, or test to trial with a PayU test account.

picoask runs one read against PayU the moment the connector starts provisioning, so a wrong or mistyped Key/Salt is reported immediately. The Salt is stored encrypted and used only by the sync worker.

3What gets synced

• Transactions — every payment with its amount, status, payment mode and date.
• Net & fees — derived from PayU's settled amount on each transaction, so take-home vs gross is visible.

Amounts land in ₹, exactly as transacted, and are never converted. The first import pulls up to two years of history; after that picoask checks every few hours, and because net/fee come from the settled amount, a transaction fills those in once PayU settles it. Settlement-level payouts, refunds and per-customer breakdowns are on the roadmap as PayU's settlement and refund reporting is validated.

4Troubleshooting

• Request rejected — the Key or Salt was copied incompletely, or these are test credentials used with environment live (or vice-versa). Recopy from Developer → API Details and reconnect with the environment matching the keys.
• No data — a new account with no transactions in the window has nothing to pull; data appears after your first live transaction.
• Reporting not enabled — some accounts need the transaction-reporting API turned on. Ask your PayU account manager to confirm it's enabled on your plan.