VibeFox PayU India for PrestaShop — Help

Requirements

PrestaShop: 8.0 to 9.x.

PHP: 8.0 or later. The module refuses to install on older PHP versions.

Currency: Indian Rupee (INR). PayU India charges in rupees only. For carts in other currencies the payment method is hidden at checkout.

Phone number: PayU requires a phone number for every payment. Make the phone field of the address required, or at least visible, in your checkout.

PayU India account: you need the Merchant Key and Merchant Salt (v1) from PayU Dashboard > Payment Gateway > Key Salt Details. Switch the dashboard to Test Mode to see the test pair. Use Salt v1, not Salt v2.

Internet access to your shop: needed for the optional webhook. Without it, orders are confirmed when the customer returns from PayU.

VibeFox license key: bought on vibefox.net. One key works on one domain.

Installation

1. In the back office go to Modules > Module Manager and click Upload a module. Choose the module ZIP file.

2. When the upload finishes, click Configure, or find VibeFox PayU India Payment Gateway in the module list later and click Configure.

3. Paste your VibeFox license key into License key in the license block at the top of the Configure page and click Activate (see License key).

4. Enter the Test Merchant Key and Salt and the Live Merchant Key and Salt (see Configuration).

5. Recommended: in PayU Dashboard > Webhooks, add the webhook URL shown on the Configure page for successful and failed payments.

6. Choose the Mode, turn on Enable/Disable and click Save. Test a payment in Test mode, then switch to Live.

On install the module creates two order statuses, Awaiting PayU India payment and PayU India payment on hold. PrestaShop offers a new payment module for all currencies, countries and customer groups. You can limit them in Payment > Preferences; the INR currency must stay allowed for the module.

Configuration

All settings are on the module page: Modules > Module Manager > VibeFox PayU India Payment Gateway > Configure. Each section has its own Save button, which saves the whole page. Above the fields the page warns you when the key or salt of the current mode is missing, shows Test mode is active: payments go to test.payu.in and no real money is charged. in Test mode, and shows an error when the default currency of your shop is not INR (the gateway is then hidden at checkout).

When you save, spaces and line breaks are removed from keys and salts, because a salt with a pasted space would make every PayU response fail the check.

PayU India

Enable/Disable: Enable PayU India Payment Gateway turns the payment method on or off. Default: off. When you turn it on without the key and salt of the current mode, the page warns you after saving.

Title: the payment method title the customer sees during checkout. It is also the payment method name stored in the order. Default: PayU India. Required.

Description: the payment method description the customer sees during checkout. Default: Pay securely via Credit/Debit Card, NetBanking, UPI, or Wallets through PayU.

API credentials

Copy the Merchant Key and Merchant Salt (v1) from PayU Dashboard > Payment Gateway > Key Salt Details. Switch the dashboard to Test Mode for the test pair. The section has a link Open the PayU Dashboard.

Mode: which PayU environment new payments use.

Test (Sandbox): uses the Test key and salt and test.payu.in. No real money is charged. At checkout the description is followed by TEST MODE: no real money is charged. (default).

Live (Production): uses the Live key and salt and secure.payu.in.

Payments already started keep the mode they were started in: their results are checked and their refunds are sent with the key and salt of that mode, even after you switch the mode.

Live Merchant Key: your live PayU Merchant Key.

Live Merchant Salt (v1): your live PayU Merchant Salt (v1). It signs requests and verifies PayU responses. Keep it secret.

Test Merchant Key: your PayU test Merchant Key, used in Test mode only.

Test Merchant Salt (v1): your PayU test Merchant Salt (v1), used in Test mode only.

Saved salts are never shown again. The field stays empty and shows Saved — leave empty to keep it. Type a new value only to change it.

Clear saved salts: tick a salt and click Save to remove it. An empty field keeps the saved value.

Return and webhook URLs

Return URL: looks like https://your-shop/module/wcp_payu_india_payment/return, possibly with a language code such as /en/. It is sent to PayU automatically with every payment; nothing has to be configured.

Webhook URL: looks like https://your-shop/module/wcp_payu_india_payment/webhook, possibly with a language code. Optional, but recommended: it confirms payments even if the customer closes the browser before returning. Add it in PayU Dashboard > Webhooks for successful and failed payments. Copy the URL exactly as the Configure page shows it. It must be reachable from the internet (no basic auth or firewall block). The maintenance mode of the shop and its country restrictions do not block it.

The webhook carries the same signed result as the customer's return. Webhooks without a valid PayU hash are rejected.

Advanced

Verify Payment: double-checks every successful payment with the PayU verify_payment API. Recommended. If the check cannot be completed, the order is put on hold instead of being marked paid. Default: on.

Enable Logging: logs gateway events for troubleshooting to logs/payu_p_debug.log.php in the module folder. The file cannot be opened from the web. Errors and warnings are always logged; this option adds the other events, such as every payment form and PayU result. Keys, salts and customer personal data are never logged. Default: off.

Log: shows the size and the latest entries of the log. Click Clear log to empty it.

Delete data on uninstall: deletes the module settings and logs when the module is uninstalled. Orders and PayU transaction records are never deleted. Default: off.

Checkout

At the payment step the customer chooses the payment method (by default PayU India) and confirms. If neither the invoice address nor the delivery address has a phone or mobile phone number, the customer stays at checkout with PayU India requires a phone number. Please enter your phone number and try again. Otherwise the customer sees a short page Thank you for your order. You will be redirected to PayU to complete your payment., which sends a signed payment request for the cart total to the PayU hosted checkout. If the browser does not continue by itself, the page has a Pay with PayU button and Back to checkout. On the PayU page the customer pays by card, NetBanking, UPI or wallet. No order exists yet at this point.

Every payment attempt gets its own PayU transaction ID that starts with the cart number, stored with its amount and mode. A payment made in an older open payment page of the same cart is still accepted. A cart that already has an order never gets a new payment form, so the browser Back button cannot start a second payment.

PayU sends the result back with the customer and, if configured, by webhook. A result is accepted only with a valid PayU hash made with the key and salt of the mode in which the payment was started, and only for a transaction ID issued for that cart. With Verify Payment on, a successful result is also checked with the PayU verify_payment API. The paid amount must equal the amount of the attempt and the cart total to the paisa, in INR. The order is marked paid only after PayU confirms it this way. The module handles these PayU results:

success: the payment was made. The order is created as paid when all checks pass, otherwise on hold.

pending: a UPI or NetBanking payment is still in progress. The order is created in Awaiting PayU India payment; the final result arrives with the webhook.

failure: the payment was declined or cancelled by the customer. No order is created and the cart is kept, so the customer can pay again. An order waiting for this payment goes to Payment error. Paid orders are never changed.

After a successful or pending payment the customer sees the standard order confirmation page. A pending payment adds Your PayU payment is pending. The order will be updated as soon as PayU confirms the result — there is no need to pay again., an order on hold adds Your payment is being reviewed. We will contact you if anything else is needed., and an order in Payment error or Canceled shows Your PayU payment was not completed. Please contact us about this order.

After an unsuccessful payment the customer comes back to the checkout with a message: Payment was not completed. Please try again or choose a different payment method., Payment was cancelled. You may try again. or, when the result could not be checked, We could not confirm the payment result. If your account was charged, please contact us before paying again. If the result is still being processed when the customer comes back, a page shows We are confirming your PayU payment. If you completed the payment, your order will be created shortly — please do not pay again. with a Check again button.

The module charges in INR only and has no multi-currency processing (MCP). It has no saved cards or tokenization, no subscriptions, no on-site (seamless) card form, no EMI or offer management and no PayU one-click checkout.

Orders and refunds

Order statuses

No order yet: the customer was sent to PayU and has not paid, or the payment failed or was cancelled. Only the cart exists.

Payment accepted: the payment was confirmed. The payment is recorded with the PayU transaction ID (mihpayid) as the transaction ID, and a note shows PayU payment successful. Transaction ID: …, Mode: …, Bank: …

Awaiting PayU India payment: a UPI or NetBanking payment is still pending at PayU. The order becomes Payment accepted when PayU confirms it.

PayU India payment on hold: the paid amount or currency differs from the cart, the verify_payment API could not be reached or did not confirm the payment yet, or a payment arrived for an order that had been cancelled. The note tells the reason. Check the transaction in the PayU Dashboard, then set the order to Payment accepted or cancel it and refund the payment. When only the verification failed, the order is paid automatically on the next delivery of the result.

Payment error: a pending payment was declined or cancelled later. A later successful result still pays the order.

Refunded: everything paid was refunded through the module.

If PayU reports another successful payment for an order that is already paid, the order is not changed and a note asks you to refund the duplicate in the PayU Dashboard. A PayU payment for a cart that was ordered with another payment method gets a note and does not pay that order.

PayU India payment block

The order page shows a PayU India payment block with the PayU transaction ID (mihpayid), the shop transaction ID (txnid), the environment, the PayU status, the payment mode and bank, the amount paid and the amount of refunds requested, a Test mode badge for test payments, the refund history and the module's notes. For an order on hold it shows a reminder to review the payment.

Refunds

In the PayU India payment block enter the amount (the amount not refunded yet is filled in), optionally a reason, and click Refund via PayU. Confirm the question Refund this amount through PayU? This cannot be undone. Full and partial refunds are supported; the amount must be greater than zero and not more than the rest of what PayU charged. You need the right to edit orders; access to the Modules pages is not needed. The refund is sent through the PayU refund API with the key and salt of the mode the payment was made in, so those credentials must be set. If PayU rejects the refund, the block shows PayU refund failed: with PayU's message and no refund is recorded.

PayU queues refunds and completes them asynchronously; the customer usually receives the money in 5–7 working days. The refund history and the notes show the amount, the PayU request ID and the reason. A full refund sets the order to Refunded; a partial refund does not change the status. Refunds are available once PayU has reported the transaction ID of the payment. The module does not check the refund status later and does not create credit slips. The standard PrestaShop refund buttons of the order page do not send money back through PayU.

License key

The module works with a VibeFox license key from vibefox.net. The license block License — VibeFox PayU India Payment Gateway is the first block on Modules > Module Manager > VibeFox PayU India Payment Gateway > Configure, above the settings. Paste the key into License key and click Activate. After that the block shows the key masked, the status (for example the date the license is active until and your domain) and the buttons Check now to check the status again, Change key to enter another key and Remove key to remove the key from this shop. Below them are the line Product: presta-payment-payu-india and the link Manage licenses and domains in your account, which opens your vibefox.net account. Only employees with the Configure permission for the module can change the key. The texts of the block follow the back office language (English and Russian are included).

If the key is not accepted, the block says why, for example Key not found, This key belongs to another product, Domain limit reached or License expired on a date. After the shop address changes, or after you free a domain slot in your account, click Check now. If the license server cannot be reached, the module keeps working on the last known status.

One key works on one domain: the domain of the main shop, also in a multistore setup. Removing the key from the shop does not free its domain slot. Free the slot in your vibefox.net account.

Without an active key, PayU India is not shown to customers at checkout. If a payment is started anyway, the customer sees This payment method is not available. Please choose another one. The PrestaShop storefront does not know that you are logged in to the back office, so the payment method is hidden for you too: you can set up the module before you buy a key, but not test it at checkout. A reminder appears in Modules > Module Manager on the Alerts tab. Existing orders are not affected: payments already started are still confirmed, and refunds work.

When a license expires, the module keeps working, but updates and support need a renewal. The status is checked again automatically while you work in the back office: once a day for the first 14 days after the key is entered, then once a week. No cron job is needed. Uninstalling or resetting the module always removes the license key and license status.

Troubleshooting

PayU India does not appear at checkout: check that the license is active, Enable/Disable is on and the key and salt of the selected Mode are filled in. Check that the cart currency is INR and that the module is allowed for that currency, the customer's country and group in Payment > Preferences. The Configure page shows a warning for missing credentials and a non-INR shop currency.

The payment went through, but no order was created: the customer did not come back to the shop, and no webhook arrived. Add the webhook URL from the Configure page in PayU Dashboard > Webhooks for successful and failed payments, and make sure it is reachable from the internet.

Webhook answers invalid_signature: the PayU hash did not match. Check that the key and salt of the payment's mode are correct and that Salt v1 is used, not Salt v2. A result of a live payment signed with the test salt, or the other way round, is rejected too. Nothing is changed.

Webhook answers not_configured: the key or salt of the mode in which the payment was started is missing. Enter them; PayU retries the webhook.

Webhook answers verify_unavailable: the verify_payment API could not confirm the payment yet. The order is on hold, and the next delivery verifies again.

Webhook answers busy or retry: the customer's return of the same cart was being processed at the same moment, or the order could not be created (for example, the module is disabled). PayU retries the webhook. The reason is written to the log.

Webhook answers ignored_unknown_txnid: the transaction was not started by this shop, for example another shop using the same PayU account. Nothing is changed.

The customer sees PayU India requires a phone number: make the phone field of the address required or visible in the checkout. The invoice address is used first, then the delivery address.

The order is PayU India payment on hold: read the notes in the PayU India payment block. The reason is an amount or currency mismatch, a failed or pending verification, or a payment for a cancelled order.

Refund fails: PayU transaction ID not found for this order. means the order has no PayU payment yet. This payment was made in Test mode, but the Merchant Key/Salt of that mode are not set. (or Live mode) means you must enter the credentials of that mode first. Invalid refund amount: at most … INR can be refunded. means the amount is more than the rest of the payment.

Too little in the log: errors and warnings are always written; turn on Enable Logging to see every payment form and PayU result as well.

Developer hook: actionPayuPRequestFields changes the payment request fields before they are signed. The key, transaction ID, amount and return URLs cannot be changed by it.

Uninstall

Go to Modules > Module Manager, open the menu next to VibeFox PayU India Payment Gateway and choose Uninstall. The license key and license status of this module are always removed. If Delete data on uninstall is on, the module settings and the log are removed. If it is off, all settings are kept for a later re-install. The PayU transaction records and refund requests and the order statuses Awaiting PayU India payment and PayU India payment on hold are always kept, so orders paid before can still be refunded after a re-install. Existing orders keep their payment notes and PayU transaction IDs.

PayU is a trademark of its respective owner. This module is not affiliated with or endorsed by PayU.