{"id":647,"date":"2026-11-14T07:15:00","date_gmt":"2026-11-14T07:15:00","guid":{"rendered":"https:\/\/paymentsetu.com\/blog\/?p=647"},"modified":"2026-11-14T07:15:00","modified_gmt":"2026-11-14T07:15:00","slug":"upi-payment-button-for-website","status":"publish","type":"post","link":"https:\/\/paymentsetu.com\/blog\/upi-payment-button-for-website\/","title":{"rendered":"How to Add a Payment Button for Website with UPI"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">A payment button for website can send a customer to a UPI payment screen in one tap, but a basic link cannot confirm whether the order was paid. This guide shows two ways to add one: a simple UPI link for small sites, and a dynamic QR plus webhook flow that verifies each order automatically.<\/p>\n\n\n\n<aside class=\"ap-card\" aria-label=\"PaymentSetu Pro\">\n<span class=\"ap-card__badge\">Best for websites<\/span>\n<div class=\"ap-card__body\"><p class=\"ap-card__name\">PaymentSetu Pro<\/p><p class=\"ap-card__best\">Best for growing WooCommerce \/ WHMCS stores and service businesses with up to 1,000 UPI payments a month (most popular)<\/p><ul class=\"ap-card__features\"><li>1,000 credits (1 credit = 1 successful payment verified)<\/li><li>0% commission, direct-to-bank UPI settlement<\/li><li>Dynamic QR, webhooks and API access<\/li><li>WooCommerce and WHMCS plugins<\/li><li>Priority support<\/li><\/ul><\/div>\n<div class=\"ap-card__side\"><p class=\"ap-card__price\">\u20b9999 <small>Most popular \u00b7 \u20b9999 \/ 30 days \u00b7 1,000 verified payments<\/small><\/p><a class=\"ap-card__btn\" href=\"https:\/\/paymentsetu.com\/auth\/register\">Get Pro \u2192<\/a><\/div>\n<\/aside>\n\n\n\n<h2 class=\"wp-block-heading\">What a payment button does (and what it costs on gateways)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A payment button is a call to action that starts checkout from a product page, invoice, donation page or service form. The button can open a UPI deep link, display a QR code, or call your server to create a payment order.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There are two separate jobs:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li><strong>Starting payment:<\/strong> show the right payee and amount so the customer can pay.<\/li>\n\n\n<li><strong>Confirming payment:<\/strong> match the payment to the right order and tell your website to deliver the product or service.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">The first job is easy with a UPI link. The second needs a reliable verification method. A customer-submitted screenshot is not proof by itself, and a shared static QR does not tell your website which order was paid.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">UPI is designed for account-to-account payments and supports QR-based merchant payments. The <a href=\"https:\/\/www.npci.org.in\/what-we-do\/upi\/faqs\" target=\"_blank\" rel=\"noopener\">NPCI UPI FAQ<\/a> describes QR integration as a merchant feature. PaymentSetu is a payment verification service, not a payment gateway: your customer pays directly into your own Paytm Business or PhonePe Business merchant account, while the service matches the payment and sends your server a webhook.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Gateway button builders can be convenient, but their pricing is normally tied to each transaction. A direct UPI flow changes the cost model to a flat verification plan with 0% commission on the payment amount.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What you need before adding the button<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For the basic option, you need a UPI ID, the payee name that customers should see, and a page where you can add a link or button.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For automatic verification, prepare these items:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>A website with a server-side endpoint. Do not call the PaymentSetu API directly from browser JavaScript.<\/li>\n\n\n<li>An active Paytm Business or PhonePe Business merchant account to receive the payment.<\/li>\n\n\n<li>A PaymentSetu account, API key and webhook URL.<\/li>\n\n\n<li>A unique order ID for every checkout attempt, such as <code>order_1001<\/code>.<\/li>\n\n\n<li>A database field for payment status, such as <code>pending<\/code>, <code>paid<\/code> or <code>cancelled<\/code>.<\/li>\n\n\n<li>HTTPS on the webhook endpoint.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The API surface you need is small: <code>POST \/api\/create_order<\/code> to create a dynamic QR order, <code>GET \/api\/order_status\/{client_txn_id}<\/code> to check an order, and <code>GET \/api\/check_credits<\/code> to see remaining verification credits.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Option 1: Add a static UPI link button<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Use this option when you need a quick pay button for a fixed-price service or a small page. It starts the payment, but it does not give your website an automatic verified order status.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1: Build the UPI link<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Why: a pre-filled amount and order note reduce typing mistakes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Create a link using your own merchant UPI ID. URL-encode the name and note if they contain spaces or symbols.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>upi:\/\/pay?pa=YOUR_MERCHANT_UPI_ID&amp;pn=YOUR_BUSINESS_NAME&amp;am=499.00&amp;cu=INR&amp;tn=ORDER-1001<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The important values are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li><code>pa<\/code>: your merchant UPI ID<\/li>\n\n\n<li><code>pn<\/code>: the payee name<\/li>\n\n\n<li><code>am<\/code>: the amount, with two decimal places when needed<\/li>\n\n\n<li><code>cu<\/code>: <code>INR<\/code><\/li>\n\n\n<li><code>tn<\/code>: a short order or invoice reference<\/li>\n\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2: Put the link behind a button<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Why: a clear action is easier to understand than a raw UPI URL.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Add this Markdown link where your website accepts Markdown, or use the same destination in your CMS button component.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>[Pay \u20b9499 by UPI](upi:\/\/pay?pa=YOUR_MERCHANT_UPI_ID&amp;pn=YOUR_BUSINESS_NAME&amp;am=499.00&amp;cu=INR&amp;tn=ORDER-1001)<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If you control the page layout, use your CMS button component with the same <code>upi:\/\/pay<\/code> destination. Set the button label to <strong>Pay \u20b9499 by UPI<\/strong> and its link to the URL above.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Success looks like the customer\u2019s device opening a compatible UPI app with the payee and amount filled in. Add a visible fallback such as \u201cScan the QR if the button does not open your app\u201d. You can make a <a href=\"https:\/\/paymentsetu.com\/free-upi-qr-code-generator\">free UPI QR code<\/a> for a fixed amount or a reusable payee link.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not mark the order paid just because the customer returned to your page or clicked the button. With this option, reconcile the UTR manually or move to the verified flow below.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Option 2: Use a dynamic QR and webhook with PaymentSetu<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This is the better option for a shop, SaaS, coaching business, freelancer or service website where every payment must be attached to a specific order.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3: Create one order on your server<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Why: a server-created order gives you a unique reference before you show the payment button.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Your server should receive the cart total, validate it against your own catalogue, create an order with status <code>pending<\/code>, and call PaymentSetu\u2019s <code>POST \/api\/create_order<\/code> endpoint. Keep the API key in an environment variable.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The exact request fields and API-key header are shown in your PaymentSetu account documentation. Use the endpoint and order reference pattern below in your server adapter; do not copy a secret into front-end code.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/\/ Example server-side adapter. Run this on your server, never in the browser.\nconst clientTxnId = `order_${order.id}`;\n\nconst response = await fetch(\"https:\/\/paymentsetu.com\/api\/create_order\", {\n  method: \"POST\",\n  headers: {\n    \"Content-Type\": \"application\/json\",\n    \"PAYMENTSETU_API_KEY_HEADER\": process.env.PAYMENTSETU_API_KEY\n  },\n  body: JSON.stringify({\n    client_txn_id: clientTxnId,\n    amount: order.total\n    \/\/ Add the other create-order fields required by your account documentation.\n  })\n});\n\nif (!response.ok) throw new Error(\"Payment order could not be created\");\nconst paymentOrder = await response.json();<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Store the returned order reference and dynamic QR value with your local order. Return only the data needed to render the payment screen to the browser. If the response includes a QR image URL or QR payload, use that value rather than generating a second QR for the same order.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Success looks like a pending order in your database and a payment response your front end can display. The amount shown on the page must match the amount you sent to the server.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4: Render the payment button and QR<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Why: mobile visitors need a one-tap action, while desktop visitors need a scannable QR.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Here is a copy-paste front-end pattern. Create the <code>pay-now<\/code>, <code>payment-box<\/code>, <code>payment-qr<\/code> and <code>payment-reference<\/code> elements with your CMS or page builder, then add this JavaScript. It calls your own <code>\/api\/payment-button<\/code> route, which should perform Step 3 and return the QR data from your server.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>  const button = document.querySelector(\"#pay-now\");\n  const box = document.querySelector(\"#payment-box\");\n  const qr = document.querySelector(\"#payment-qr\");\n  const reference = document.querySelector(\"#payment-reference\");\n\n  button.addEventListener(\"click\", async () =&gt; {\n    button.disabled = true;\n    button.textContent = \"Preparing payment\u2026\";\n\n    try {\n      const result = await fetch(\"\/api\/payment-button\", {\n        method: \"POST\",\n        headers: { \"Content-Type\": \"application\/json\" },\n        body: JSON.stringify({ productId: \"YOUR_PRODUCT_ID\" })\n      });\n\n      if (!result.ok) throw new Error(\"Could not create payment\");\n      const payment = await result.json();\n\n      qr.src = payment.qr_image_url;\n      reference.textContent = `Reference: ${payment.client_txn_id}`;\n      box.hidden = false;\n      button.textContent = \"QR ready \u2014 scan to pay\";\n    } catch (error) {\n      button.disabled = false;\n      button.textContent = \"Try again\";\n      alert(\"We could not prepare the payment. Please try again.\");\n    }\n  });<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Map <code>qr_image_url<\/code> to the QR field returned by your current API response. The important security boundary is unchanged: the browser calls your application, and your application calls PaymentSetu with the private key.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Marking the order paid from the webhook<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5: Receive and verify the event<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Why: your fulfilment logic should run only after an authenticated, successful payment event.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Configure a public HTTPS webhook URL in your PaymentSetu dashboard. The service matches the received payment using the order details, including UTR and amount, then sends a signed webhook event to your server.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Your handler should:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Read the raw request body before parsing JSON.<\/li>\n\n\n<li>Verify the HMAC signature using your webhook secret and the signature header configured in your account.<\/li>\n\n\n<li>Reject an invalid signature with a non-success response.<\/li>\n\n\n<li>Check that the event is for the expected <code>client_txn_id<\/code>, amount and merchant account.<\/li>\n\n\n<li>Make the update idempotent: if the order is already <code>paid<\/code>, do not deliver it twice.<\/li>\n\n\n<li>Mark the order paid only for the documented successful status.<\/li>\n\n\n<li>Return a success response after the event is stored or processed.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">A Node.js-shaped handler looks like this. Replace the placeholder signature header with the one in your PaymentSetu documentation.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>import crypto from \"node:crypto\";\n\napp.post(\"\/webhooks\/paymentsetu\", rawBodyMiddleware, async (req, res) =&gt; {\n  const received = req.get(\"PAYMENTSETU_SIGNATURE_HEADER\");\n  const expected = crypto\n    .createHmac(\"sha256\", process.env.PAYMENTSETU_WEBHOOK_SECRET)\n    .update(req.body)\n    .digest(\"hex\");\n\n  if (!received || received.length !== expected.length ||\n      !crypto.timingSafeEqual(Buffer.from(received), Buffer.from(expected))) {\n    return res.status(401).send(\"Invalid signature\");\n  }\n\n  const event = JSON.parse(req.body.toString(\"utf8\"));\n  const order = await orders.findByClientTxnId(event.client_txn_id);\n\n  if (!order || Number(event.amount) !== Number(order.total)) {\n    return res.status(400).send(\"Order mismatch\");\n  }\n\n  if (event.status === \"success\" &amp;&amp; order.status !== \"paid\") {\n    await orders.markPaid(order.id, { utr: event.utr });\n    await fulfilOrderOnce(order.id);\n  }\n\n  return res.status(200).send(\"OK\");\n});<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If your webhook handler is temporarily unavailable, use <code>GET \/api\/order_status\/{client_txn_id}<\/code> from your server as a reconciliation check. Never trust a browser-only \u201cpayment successful\u201d message to unlock a paid product.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Button design tips that help on mobile<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The payment button is part of checkout, not decoration. Keep the path from product selection to payment obvious:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Use a specific label such as <strong>Pay \u20b9499 by UPI<\/strong> instead of \u201cSubmit\u201d.<\/li>\n\n\n<li>Show the final amount before the customer taps.<\/li>\n\n\n<li>On mobile, keep the button wide enough for a thumb and place it close to the order summary.<\/li>\n\n\n<li>Show the QR and the UPI app instruction on the same screen; provide a copyable reference.<\/li>\n\n\n<li>Explain that the customer should check the payee name before confirming.<\/li>\n\n\n<li>Keep the pending state visible after the QR appears. Do not show \u201cpaid\u201d until your server receives and verifies the event.<\/li>\n\n\n<li>Add a clear support path for a customer who has paid but is still waiting for order confirmation.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">For a fixed-price, low-volume page, a static link plus QR may be enough. For variable carts, invoices or automatic access, create a unique dynamic order every time.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Cost compared: 2% per payment vs a flat \u20b9999 plan<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Use an illustrative rate to see why a flat plan can suit a growing website. At 2% on \u20b95,00,000 of monthly collections, the transaction charge would be \u20b910,000:<\/p>\n\n\n\n<figure class=\"wp-block-table ap-table\"><table><thead><tr><th>Monthly collection<\/th><th>Illustrative per-payment charge at 2%<\/th><th>PaymentSetu Pro plan<\/th><\/tr><\/thead><tbody><tr><td>\u20b91,00,000<\/td><td>\u20b92,000<\/td><td>\u20b9999 \/ 30 days<\/td><\/tr><tr><td>\u20b95,00,000<\/td><td>\u20b910,000<\/td><td>\u20b9999 \/ 30 days<\/td><\/tr><tr><td>\u20b910,00,000<\/td><td>\u20b920,000<\/td><td>\u20b9999 \/ 30 days<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The 2% column is a worked example, not a quote for a particular gateway. PaymentSetu Pro costs \u20b9999 per 30 days and includes 1,000 credits, where one credit equals one successful payment verified. It also includes dynamic QR, API access, webhooks, a unified dashboard and priority support. The customer\u2019s payment goes directly to your connected Paytm Business or PhonePe Business merchant account, with 0% commission on the payment amount.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The live <a href=\"https:\/\/paymentsetu.com\/#pricing\">PaymentSetu pricing<\/a> page shows the available plans. If your website is still small, Starter is \u20b9399 per 30 days for 100 credits. If you need substantially more verification capacity, Business is \u20b91,499 per 30 days for 100,000 credits.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/paymentsetu.com\/blog\/wp-content\/uploads\/2026\/10\/upi-payment-button-for-website-1.webp\" alt=\"PaymentSetu pricing plans for a UPI payment button setup\"\/><figcaption class=\"wp-element-caption\">PaymentSetu pricing plans for a UPI payment button setup<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Verify your payment button before launch<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Run a complete test with a small real order or your documented test process:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Create an order from the website, and confirm its local status is <code>pending<\/code>.<\/li>\n\n\n<li>Check that the displayed amount, payee name and order reference are correct.<\/li>\n\n\n<li>Pay by scanning the dynamic QR from a separate device.<\/li>\n\n\n<li>Confirm the payment reaches your own connected merchant account.<\/li>\n\n\n<li>Confirm your webhook verifies the signature and matches the order.<\/li>\n\n\n<li>Confirm exactly one fulfilment action occurs.<\/li>\n\n\n<li>Query the order status endpoint and compare it with your local record.<\/li>\n\n\n<li>Check that the API key and webhook secret are absent from browser source, logs and error messages.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">If you use WooCommerce, the <a href=\"https:\/\/paymentsetu.com\/woocommerce-plugin\">PaymentSetu WooCommerce plugin<\/a> can update orders after verification without custom API work. For a custom website, keep the same pattern: create the order on the server, show the QR in the browser, and let the signed webhook control fulfilment. When ready, <a href=\"https:\/\/paymentsetu.com\/auth\/register\">create your PaymentSetu account<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting a website payment button<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The button does nothing.<\/strong> Check whether the browser or device supports the <code>upi:\/\/<\/code> scheme. Always show a QR and the merchant UPI ID as a fallback.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The QR opens but the amount is wrong.<\/strong> Compare the amount in your local order, the create-order request and the rendered response. Treat the server-side catalogue price as the source of truth.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The customer paid but the order is still pending.<\/strong> Check the webhook URL, raw request logging, signature verification and the order reference. Use the order-status endpoint for reconciliation, then process the event idempotently.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The webhook creates duplicate access.<\/strong> Put a unique constraint on the local order ID or transaction reference, and check the current order status before fulfilment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The API key appears in page source.<\/strong> Move the PaymentSetu call to your server immediately and rotate the exposed key. Front-end JavaScript should call only your own endpoint.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">How do I add a payment button for website pages?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">For a simple page, create a <code>upi:\/\/pay<\/code> link with your UPI ID, payee name, amount and order note, then put it behind a button. For automatic confirmation, have your server create a dynamic order and render the returned QR data.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I add a UPI pay now button without a payment gateway?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes. A static UPI link or QR can send money directly to your merchant account, but it does not automatically verify the order. PaymentSetu adds order matching and signed webhooks while remaining a payment verification service, not a payment gateway.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How does a UPI button confirm that an order was paid?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The website creates a unique order reference before showing the QR. After the customer pays, PaymentSetu matches the payment details and sends your server a signed webhook; your server verifies it, checks the amount and marks the order paid once.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Should the API key be placed in JavaScript?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. Browser code is visible to visitors, so the API key belongs in a server environment variable. Your front end should call your own backend route, which creates the PaymentSetu order and returns only the QR and order data needed for checkout.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Which PaymentSetu plan is suitable for a website?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Pro is \u20b9999 per 30 days with 1,000 verification credits and is designed for growing WooCommerce, WHMCS and service businesses. Starter is \u20b9399 per 30 days for 100 credits, while Business is \u20b91,499 per 30 days for 100,000 credits.<\/p>\n\n\n\n<aside class=\"ap-cta\" aria-label=\"Put your button live\"><div class=\"ap-cta__content\"><p class=\"ap-cta__eyebrow\">Add UPI checkout<\/p><p class=\"ap-cta__title\">Put your button live<\/p><p class=\"ap-cta__text\">Create verified UPI payment orders that settle directly to your own merchant account.<\/p><\/div><a class=\"ap-cta__btn\" href=\"https:\/\/paymentsetu.com\/auth\/register\">Start with PaymentSetu<\/a><\/aside>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"How do I add a payment button for website pages?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"For a simple page, create a upi:\/\/pay link with your UPI ID, payee name, amount and order note, then put it behind a button. For automatic confirmation, have your server create a dynamic order and render the returned QR data.\"}}, {\"@type\": \"Question\", \"name\": \"Can I add a UPI pay now button without a payment gateway?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Yes. A static UPI link or QR can send money directly to your merchant account, but it does not automatically verify the order. PaymentSetu adds order matching and signed webhooks while remaining a payment verification service, not a payment gateway.\"}}, {\"@type\": \"Question\", \"name\": \"How does a UPI button confirm that an order was paid?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"The website creates a unique order reference before showing the QR. After the customer pays, PaymentSetu matches the payment details and sends your server a signed webhook; your server verifies it, checks the amount and marks the order paid once.\"}}, {\"@type\": \"Question\", \"name\": \"Should the API key be placed in JavaScript?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. Browser code is visible to visitors, so the API key belongs in a server environment variable. Your front end should call your own backend route, which creates the PaymentSetu order and returns only the QR and order data needed for checkout.\"}}, {\"@type\": \"Question\", \"name\": \"Which PaymentSetu plan is suitable for a website?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Pro is \u20b9999 per 30 days with 1,000 verification credits and is designed for growing WooCommerce, WHMCS and service businesses. Starter is \u20b9399 per 30 days for 100 credits, while Business is \u20b91,499 per 30 days for 100,000 credits.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Add a payment button for website with a UPI link, dynamic QR and webhook. Follow the HTML, JavaScript and server setup for verified payments.","protected":false},"author":1,"featured_media":646,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_singular_sidebar":"","csco_page_header_type":"","csco_page_load_nextpost":"","footnotes":""},"categories":[29],"tags":[7,200,17,28,60],"class_list":["post-647","post","type-post","status-publish","format-standard","has-post-thumbnail","category-upi-payment-verification","tag-dynamic-qr","tag-payment-button","tag-upi-payments","tag-webhooks","tag-website-payments","cs-entry"],"_links":{"self":[{"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts\/647","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/comments?post=647"}],"version-history":[{"count":1,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts\/647\/revisions"}],"predecessor-version":[{"id":877,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts\/647\/revisions\/877"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/media\/646"}],"wp:attachment":[{"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/media?parent=647"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/categories?post=647"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/tags?post=647"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}