FAQs (Frequently Asked Questions)

A PayU Payment Button is a Buy Now, Pay Now, Book Now, or Donate Now button you add to your website or blog. You create and configure it in the PayU Dashboard. We give you a short piece of code to paste on your page. When a visitor clicks the button, PayU's payment page opens and they can complete their payment. Once done, they are sent back to your website. No developer or server setup is required. Refer to Add a Payment Button for steps top add a payment button

You do not need a developer to create the payment button. You set it up in the PayU Dashboard and we give you the button code.

You should paste that code onto your website. Most website builders such as WordPress, Wix, Squarespace, Webflow, have an HTML or Code block where you can do this without writing code. If your site is fully managed and you cannot add content yourself, ask whoever looks after your website to paste the code for you.

No. They serve different purposes:

📘

Tips:

Both use PayU's payment page and support the same payment methods.

Customers can pay using any method enabled on your merchant account such as credit and debit cards (Visa, Mastercard, RuPay, Amex), UPI, Net Banking, Wallets, EMI, and BNPL. Contact PayU support to enable or disable specific methods.

You cannot turn-off a payment button. However, you can delete it to stop accepting payments permanently.

If you have already deleted a button and need to accept payments again for the same purpose, create a new button with the same settings and add it to your website.

Yes. PayU Payment Buttons are PCI DSS compliant. We use encryption and tokenisation to protect customer payment data. No card or bank details are ever handled by your website, everything goes through PayU's secure payment page.

Yes. You can create as many Payment Buttons as you need. Each button has its own unique code. For example, you can have a Buy Now button on a product page, a Donate Now button on a fundraising page, and a Book Now button on an events page, all on the same website.

Each button is independent: changing or removing one does not affect the others.

Both options are available:

• Fixed amount: Enter a specific amount in the Amount field when creating the button. Customers cannot change it at checkout.
• Open amount: Leave the Amount field blank. Customers will enter the amount themselves on the payment page.

The open amount option is well suited for donations, tips, or any payment where the value differs per customer.

When creating a Payment Button from the PayU Dashboard, enter the amount in rupees (INR). For example, enter 500 for ₹500.

Do not enter the amount in paise. Paise values are only used in certain API integrations.

No. The button label drop-down is limited to four options such as, Buy Now, Pay Now, Book Now, and Donate Now. Custom labels are not currently supported from the Dashboard.

If none of the presets fit your use case, you can create your own button on your website and attach a Payment Link to it. This way, you get full control over the button text while still using PayU's payment page.

Yes. You can edit a Payment Button settings cannot be changed after it is created. Afer you save the new btton configuration, a new code will be generated. You should copy and paste the new code in your website.

Yes. When creating the button, switch on any standard fields in the Custom Details section such as Customer Name, Customer Address, Customer Email, and Customer Mobile. You can also add your own custom fields (text, calendar, or drop-down) with any label. Mark any field as mandatory to require it before the customer can proceed to pay.

Yes. Under Advanced Options when creating the button, you can enter:

• Success URL: Where customers are sent after a successful payment
• Cancel URL: Where customers are sent if they close the payment page without paying
• Failure URL: Where customers are sent if the payment does not go through
  

These are optional but recommended. Without them, customers land on a default PayU confirmation page and are not automatically returned to your website.

Paste the code in any HTML or Code block on your website. Common placements:

• WordPress: Use a Custom HTML widget or block
• Wix: Use an Embed HTML element
• Squarespace / Webflow: Use a Code block
• Plain website: Paste inside the <body> section of your page wherever you want the button to appear
  

The button appears as soon as the page loads.

Yes. You can paste the same button code on as many pages as you like. Every customer who clicks the button will see the same settings (same amount, label, and checkout fields). If you need different settings on different pages, create a separate button for each page.

The Dashboard lets you choose colour, size, and label. Further styling such as custom fonts, border radius, hover effects, and so on is not supported through the Dashboard.

If you need a fully custom-styled button, create your own button design on your website and attach a Payment Link URL to it to get complete visual control while still using PayU's payment page.

This is almost always a POST vs GET issue. PayU sends the customer to your success page using a POST request, not a GET request. The payment details (transaction ID, amount, status) are sent as POST parameters in the request body.

If your success page is set up to read URL parameters (GET), it will not find the payment data and may show an error, even though the payment went through successfully.

How to fix:

• Update your success page to read POST parameters from the request body instead of URL parameters.
• If your success page just shows a thank-you message and does not need to read payment data, it should load without issues. Check for any server-side errors on the page itself.
  

You can confirm the payment went through by checking the Transactions tab in your PayU Dashboard.

This can happen for one of these reasons:

1. The button code is inside a <form> tag. If the surrounding page has a form that submits on load, it can trigger the button. Move the button code outside any <form> element.
2. A JavaScript conflict on your page. Another script on your website may be triggering a click event on the button automatically. Check your browser console (F12 → Console) for JavaScript errors and test the page with other scripts temporarily disabled.
3. The page is caching an old session. Clear your browser cache and test again in a private or incognito window.

If the issue persists, contact PayU support with your button name and the page URL where the button is added.

The payment appears in the Transactions tab of your PayU Dashboard right away. For instant notifications, set up a webhook under Settings → Webhooks in the Dashboard. PayU will send a payment.success event to your server each time a payment is completed.

→ Webhooks for Payments

Yes. Find the transaction in the Transactions tab of your Dashboard and start a refund from there. The refund process is the same regardless of how the payment was collected.

No. Payment Buttons are for one-time payments only. Each time a customer clicks the button, it is a separate, individual payment.

If you need to charge customers on a recurring schedule, for example monthly fees, membership dues, or subscription plans, use PayU's Recurring Payments product instead.

'Pending' means the payment was started but not yet confirmed by the customer's bank. This usually resolves within a few minutes.

If a transaction stays in Pending for more than 30 minutes, the customer's bank may not have completed the authorisation. The amount (if debited) is typically returned automatically by the bank within 5–7 business days.

If the Pending status does not resolve after an hour, contact PayU support with the transaction date, amount, and the customer's payment method.