'sorry some error occurred' while integrating PayUMoney payment gateway in Test mode

'sorry some error occurred' while integrating PayUMoney payment gateway in Test mode

  1. Blog
  2. 15 November 2026
  3. 1 min read

Stefan Bogdanescu

Founder & Senior Architect

Decoding "Sorry Some Error Occurred" in PayUMoney Test Mode

When integrating a payment gateway, receiving a vague error message like "sorry some error occurred" is frustrating because it offers zero context for debugging. In the case of PayUMoney's test environment, this specific error usually stems from a fundamental misunderstanding of how their sandbox credentials work versus production ones. The issue isn't necessarily that your code logic is flawed, but rather that you are likely trying to use live merchant keys in a test endpoint, or conversely, using test credentials without proper initialization.

To resolve the integration failure where you cannot find a "Developer site" to create a test account, it is crucial to understand PayUMoney's sandbox architecture. Unlike some gateways that provide a standalone developer portal for sandbox testing independent of your merchant account, PayUMoney often requires you to use the same credentials provided by your client but switch the endpoint URL. However, if the error persists despite switching https://secure.payu.in to https://test.payu.in, the root cause is almost always the Merchant Key and Salt mismatch.

PayUMoney test mode keys are distinct from live keys. If your client provided you with a live Merchant Key (e.g., JBZaLc) and a live Salt (e.g., GQs7yium), attempting to use these against the https://test.payu.in endpoint will trigger security validation failures on the server side. The gateway detects that the signature generated by your client-side salt does not match what their test environment expects for that specific key, or worse, the key simply isn't registered in the test database.

The provided PHP code snippet demonstrates a classic implementation

Our network