Non-Seamless Debit Transaction API

The Non-Seamless Debit Transaction API allows you to debit funds from a wallet using a non-seamless integration approach. This API requires user interaction and redirection through a payment interface for transaction authorization.

Environment

HTTP Method: POST

Request Headers

Request Parameters

Body Parameters

The request body is sent as form-encoded parameters.

📘

Note: Either customer_id or walleturn must be provided to identify the wallet.

Hash Calculation

The hash is calculated using SHA512 with the following string:

key|txnId|amount|productinfo|firstName|email|||||||||||||{salt}

Response Parameters

Sample Request

curl --location --request POST 'https://test.payu.in/_payment' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'key=KOEfPI' \
--data-urlencode 'txnid=RAM1234' \
--data-urlencode 'amount=41.00' \
--data-urlencode 'productinfo=iPhone' \
--data-urlencode 'firstname=Ravi' \
--data-urlencode '[email protected]' \
--data-urlencode 'phone=919988776655' \
--data-urlencode 'ws_online_response=https://merchant.com/success' \
--data-urlencode 'ws_failure_response=https://merchant.com/failure' \
--data-urlencode 'pg=CLW' \
--data-urlencode 'walleturn=70000000008' \
--data-urlencode 'hash=6e640b...'

Sample Response

Successful Transaction

{
  "mihpayid": "1735903830180094",
  "mode": "CLW",
  "status": "success",
  "key": "KOEfPI",
  "txnid": "RAM1234",
  "amount": "41.00",
  "net_amount_debit": "41.00",
  "productinfo": "iPhone",
  "firstname": "Ravi",
  "lastname": "Kumar",
  "email": "[email protected]",
  "phone": "919988776655",
  "addedon": "2025-01-13 18:24:06",
  "hash": "def456ghi789...",
  "PG_TYPE": "CLW"
}

Failed Transaction

{
  "mihpayid": "1735903830180095",
  "mode": "CLW",
  "status": "failure",
  "key": "KOEfPI",
  "txnid": "RAM1235",
  "amount": "41.00",
  "productinfo": "iPhone",
  "firstname": "Ravi",
  "lastname": "Kumar",
  "email": "[email protected]",
  "phone": "919988776655",
  "error": "Insufficient balance",
  "error_Message": "Wallet balance is insufficient for this transaction",
  "hash": "xyz789abc123..."
}

HTTP Status Codes

Transaction Flow

1. Initiate Transaction: Send a POST request with all required parameters
2. User Redirection: User is redirected to PayU's payment interface for authorization
3. User Authorization: User confirms the transaction on the payment page
4. Callback: PayU sends the result to either ws_online_response or ws_failure_response
5. Verification: Use the response hash to verify the authenticity of the callback

Difference from Seamless Debit

Best Practices

1. Hash Security: Protect your salt key and never expose it in client-side code
2. Callback Handling: Implement proper callback URL handlers for success and failure scenarios
3. Transaction Verification: Always verify the response hash for authenticity
4. Error Handling: Implement comprehensive error handling for different failure scenarios
5. User Experience: Provide clear messaging during the redirection flow
6. Reconciliation: Use the enquiry API to verify final transaction status

Common Error Scenarios

Security Considerations

1. Use HTTPS for all API communications
2. Validate all input parameters before processing
3. Implement rate limiting to prevent abuse
4. Store sensitive data securely
5. Monitor for suspicious transaction patterns
6. Implement proper logging for audit trails