{"id":696,"date":"2026-11-18T12:00:00","date_gmt":"2026-11-18T12:00:00","guid":{"rendered":"https:\/\/paymentsetu.com\/blog\/?p=696"},"modified":"2026-11-18T12:00:00","modified_gmt":"2026-11-18T12:00:00","slug":"add-upi-payment-html-website","status":"publish","type":"post","link":"https:\/\/paymentsetu.com\/blog\/add-upi-payment-html-website\/","title":{"rendered":"Payment gateway integration in HTML website: UPI guide"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Payment gateway integration in html website can be simple: start with a UPI link or QR, then add one small server endpoint when you need automatic verification. This guide shows a plain HTML checkout that sends money straight to your own UPI merchant account and uses a webhook to confirm the matching order.<\/p>\n\n\n\n<aside class=\"ap-card\" aria-label=\"PaymentSetu Starter\">\n<span class=\"ap-card__badge\">Best for small sites<\/span>\n<div class=\"ap-card__body\"><p class=\"ap-card__name\">PaymentSetu Starter<\/p><p class=\"ap-card__best\">Best for small shops, freelancers and new online stores verifying up to 100 UPI payments a month<\/p><ul class=\"ap-card__features\"><li>100 credits (1 credit = 1 successful payment verified)<\/li><li>0% commission &#8211; money goes straight to your own merchant account<\/li><li>Dynamic QR for every order<\/li><li>Webhook + REST API access<\/li><li>Unified dashboard and real-time notifications<\/li><\/ul><\/div>\n<div class=\"ap-card__side\"><p class=\"ap-card__price\">\u20b9399 <small>\u20b9399 \/ 30 days \u00b7 100 verified payments<\/small><\/p><a class=\"ap-card__btn\" href=\"https:\/\/paymentsetu.com\/auth\/register\">Start with Starter \u2192<\/a><\/div>\n<\/aside>\n\n\n\n<p class=\"wp-block-paragraph\">If you want zero commission on payments and up to 100 successful payment verifications, PaymentSetu Starter is \u20b9399 per 30 days. PaymentSetu is a payment verification service, not a payment gateway: the customer pays your connected merchant account, while the service matches the UTR and amount to your order and sends your webhook.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What you need<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Prepare these items before editing your website:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>A plain HTML site served over HTTPS.<\/li>\n\n\n<li>A UPI merchant account that you can connect to PaymentSetu. The active connectors are Paytm Business and PhonePe Business.<\/li>\n\n\n<li>A public HTTPS URL for a small PHP endpoint, or a serverless function that can make outbound HTTPS requests.<\/li>\n\n\n<li>A PaymentSetu API key and a webhook signing secret from your account.<\/li>\n\n\n<li>A place in your database or order file to store <code>client_txn_id<\/code>, amount, order status and UTR.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If your site only needs a payment button and you will reconcile payments yourself, use the manual route below. If an order should be released automatically, use the dynamic route and never treat a customer\u2019s screenshot as payment proof.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Choose manual or automatic verification<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why this matters: static HTML can display payment instructions, but it cannot safely keep an API key or verify a bank transaction in the browser.<\/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>Collect payment details:<\/strong> a UPI link or QR can pre-fill the payee and amount.<\/li>\n\n\n<li><strong>Confirm payment:<\/strong> a backend must receive a trusted status event, match it to your order and then deliver the product or service.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">NPCI describes QR, intent, application-based and collect as merchant integration modes. Its FAQ also explains that a QR can contain the merchant UPI ID and amount, so the payer sees those details after scanning. Read the <a href=\"https:\/\/www.npci.org.in\/what-we-do\/upi\/faqs\" target=\"_blank\" rel=\"noopener\">NPCI UPI FAQ<\/a> when deciding which merchant flow suits your account.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a brochure site, booking enquiry or one-off invoice, manual QR may be enough. For digital downloads, course access, hosting renewals or an online store, dynamic QR plus automatic verification is the safer design.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a simpler link-only implementation, see our guide to <a href=\"https:\/\/paymentsetu.com\/blog\/how-to-create-upi-payment-link\/\">creating a UPI payment link<\/a>. If you are comparing architectures, <a href=\"https:\/\/paymentsetu.com\/blog\/accept-upi-payments-on-website-without-gateway\/\">accepting UPI payments on a website without a gateway<\/a> explains the same direct-to-merchant model at a higher level.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Add a free UPI link or QR<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why this matters: you can launch a static payment option without adding a database or backend.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Create a QR with the <a href=\"https:\/\/paymentsetu.com\/free-upi-qr-code-generator\">free UPI QR Code Generator<\/a>. Enter your UPI ID, business name, and either a fixed amount or no amount. Download the PNG and place it beside the product or invoice. The generator runs in the browser, so it is useful for a simple static page.<\/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\/add-upi-payment-html-website-1.webp\" alt=\"PaymentSetu\u2019s free UPI QR generator can create a printable QR for a static HTML website.\"\/><figcaption class=\"wp-element-caption\">PaymentSetu\u2019s free UPI QR generator can create a printable QR for a static HTML website.<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">For a mobile visitor, you can also add a UPI deep link. Replace every placeholder with your own values and URL-encode the business name and note. Set the destination of a normal page link to this URI and use \u201cPay \u20b9499 by UPI\u201d as its visible label:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>upi:\/\/pay?pa=YOURVPA%40provider&amp;pn=YOUR%20BUSINESS&amp;am=499.00&amp;cu=INR&amp;tn=Order%201002<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>upi:\/\/pay<\/code> link may open a compatible UPI app on a mobile device; a desktop browser may do nothing. Keep a QR or a \u201cpay from another device\u201d instruction beside it. NPCI\u2019s published <a href=\"https:\/\/www.npci.org.in\/PDF\/npci\/upi\/circular\/2017\/Circular18_BankCompliances_to_enbaleUPIMerchantecosystem_0.pdf\" target=\"_blank\" rel=\"noopener\">merchant ecosystem circular<\/a> documents the deep-link parameters and transaction-reference considerations.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Success looks like this: the customer can see your merchant name and amount in the UPI app, and your team can match the UTR and amount in the merchant account before fulfilling the order. This route does not, by itself, update your HTML page automatically.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Add the dynamic-order button<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why this matters: a unique order ID lets the verification service associate one payment with one customer order.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Add a form to your existing product or checkout page with these controls: an item field with the ID <code>item<\/code> and default value <code>Website consultation<\/code>; an amount field with the ID <code>amount<\/code>, numeric validation, minimum <code>1<\/code>, two decimal places and default value <code>499<\/code>; and a submit control labelled \u201cShow UPI payment\u201d. Also reserve a status message with the ID <code>payment-status<\/code>, a hidden QR image with the ID <code>payment-qr<\/code>, and a reference message with the ID <code>payment-reference<\/code>. The browser sends only the amount and item reference to your own endpoint; it never sees the PaymentSetu API key.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>  const form = document.querySelector('#pay-form');\n  const statusBox = document.querySelector('#payment-status');\n  const qr = document.querySelector('#payment-qr');\n  const reference = document.querySelector('#payment-reference');\n\n  form.addEventListener('submit', async (event) =&gt; {\n    event.preventDefault();\n    statusBox.textContent = 'Creating your payment order\u2026';\n    qr.hidden = true;\n\n    const response = await fetch('\/api\/create-order.php', {\n      method: 'POST',\n      headers: {'Content-Type': 'application\/json'},\n      body: JSON.stringify({\n        item: document.querySelector('#item').value,\n        amount: document.querySelector('#amount').value\n      })\n    });\n\n    const result = await response.json();\n    if (!response.ok || !result.qr_url) {\n      statusBox.textContent = result.error || 'The payment QR could not be created.';\n      return;\n    }\n\n    qr.src = result.qr_url;\n    qr.hidden = false;\n    reference.textContent = `Reference: ${result.client_txn_id}`;\n    statusBox.textContent = 'Scan the QR with any UPI app and complete the payment.';\n  });<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The normalised <code>qr_url<\/code> response in this example is produced by your PHP adapter. Keep the real response mapping in that adapter, not in public JavaScript, so a future API response change does not expose secrets or payment logic.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Create the tiny PHP endpoint<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why this matters: the server is the only safe place for your API key, order creation call and price validation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Save this as <code>api\/create-order.php<\/code>. Store secrets in environment variables or your host\u2019s secret manager; do not commit them to the HTML repository. The endpoint names below are the PaymentSetu REST paths. Copy the current request field names and authentication header from the API documentation in your PaymentSetu dashboard before going live, because those details can change independently of your page.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&lt;?php\ndeclare(strict_types=1);\n\nheader('Content-Type: application\/json');\n\n$input = json_decode(file_get_contents('php:\/\/input'), true);\n$amount = filter_var($input['amount'] ?? null, FILTER_VALIDATE_FLOAT);\n$item = trim((string)($input['item'] ?? ''));\n\nif ($amount === false || $amount &lt;= 0 || $item === '') {\n    http_response_code(422);\n    echo json_encode(['error' =&gt; 'Enter a valid item and amount.']);\n    exit;\n}\n\n\/\/ Never trust a browser price for a real shop. Look up the item price here.\n$allowedPrices = ['Website consultation' =&gt; 499.00];\nif (!isset($allowedPrices[$item]) || abs($allowedPrices[$item] - $amount) &gt; 0.001) {\n    http_response_code(422);\n    echo json_encode(['error' =&gt; 'The item price is not valid.']);\n    exit;\n}\n\n$clientTxnId = 'html-' . bin2hex(random_bytes(12));\n$apiKey = getenv('PAYMENTSETU_API_KEY');\nif (!$apiKey) {\n    http_response_code(500);\n    echo json_encode(['error' =&gt; 'Payment API is not configured.']);\n    exit;\n}\n\n\/\/ Use the exact field names shown in your current PaymentSetu API docs.\n$payload = [\n    'client_txn_id' =&gt; $clientTxnId,\n    'amount' =&gt; number_format($amount, 2, '.', ''),\n    'item' =&gt; $item,\n    'webhook_url' =&gt; 'https:\/\/example.com\/api\/payment-webhook.php'\n];\n\n$curl = curl_init('https:\/\/paymentsetu.com\/api\/create_order');\ncurl_setopt_array($curl, [\n    CURLOPT_POST =&gt; true,\n    CURLOPT_RETURNTRANSFER =&gt; true,\n    CURLOPT_HTTPHEADER =&gt; [\n        'Content-Type: application\/json',\n        'X-API-Key: ' . $apiKey\n    ],\n    CURLOPT_POSTFIELDS =&gt; json_encode($payload),\n    CURLOPT_TIMEOUT =&gt; 15\n]);\n$body = curl_exec($curl);\n$httpCode = (int)curl_getinfo($curl, CURLINFO_HTTP_CODE);\ncurl_close($curl);\n\n$decoded = json_decode((string)$body, true);\n$qrUrl = $decoded['data']['qr_url'] ?? $decoded['qr_url'] ?? null;\n\nif (!in_array($httpCode, range(200, 299), true) || !$qrUrl) {\n    http_response_code(502);\n    echo json_encode(['error' =&gt; 'The payment order response did not contain a QR URL.']);\n    exit;\n}\n\n\/\/ Persist this pair in your order store before returning it to the browser.\n\/\/ Store: client_txn_id, item, amount, status=pending.\necho json_encode([\n    'client_txn_id' =&gt; $clientTxnId,\n    'qr_url' =&gt; $qrUrl\n]);<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The sample uses <code>X-API-Key<\/code> and illustrative response keys so the security boundary is easy to see. If your dashboard documents a different header, payload or QR field, change those three mappings together. Do not make the browser call <code>\/api\/create_order<\/code> directly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">PaymentSetu also exposes <code>GET \/api\/order_status\/{client_txn_id}<\/code> and <code>GET \/api\/check_credits<\/code>. Use the status endpoint for an operator-facing lookup or a controlled fallback; the webhook remains the event that should update an order automatically. A plan credit represents one successful payment verified. Starter is \u20b9399 per 30 days for 100 credits; Pro is \u20b9999 per 30 days for 1,000 credits.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Receive and verify the webhook<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why this matters: the redirect back to your site is a browser event, not proof that money arrived. Verify the signed raw request, match the order ID and amount, then make the fulfilment action idempotent.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Create <code>api\/payment-webhook.php<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&lt;?php\ndeclare(strict_types=1);\n\n$rawBody = file_get_contents('php:\/\/input');\n$secret = getenv('PAYMENTSETU_WEBHOOK_SECRET');\n$received = $_SERVER['HTTP_X_PAYMENTSETU_SIGNATURE'] ?? '';\n\nif (!$secret || !$received) {\n    http_response_code(401);\n    exit;\n}\n\n$expected = hash_hmac('sha256', $rawBody, $secret);\nif (!hash_equals($expected, $received)) {\n    http_response_code(401);\n    exit;\n}\n\n$event = json_decode($rawBody, true);\n$clientTxnId = (string)($event['client_txn_id'] ?? '');\n$amount = (float)($event['amount'] ?? 0);\n$utr = (string)($event['utr'] ?? '');\n$status = (string)($event['status'] ?? '');\n\nif ($clientTxnId === '' || $amount &lt;= 0 || $utr === '' || $status !== 'success') {\n    http_response_code(422);\n    exit;\n}\n\n\/\/ 1. Load the pending order by client_txn_id.\n\/\/ 2. Compare the stored amount with $amount.\n\/\/ 3. If already paid, return 200 without fulfilling twice.\n\/\/ 4. Mark it paid and fulfil it in one database transaction.\n\nhttp_response_code(200);\necho 'ok';<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Use the exact signature header, JSON keys and success value documented in your account. Keep the raw body unchanged until after HMAC verification. The <a href=\"https:\/\/www.php.net\/manual\/en\/function.hash-hmac.php\" target=\"_blank\" rel=\"noopener\">PHP <code>hash_hmac<\/code> reference<\/a> documents the function used above; the PaymentSetu webhook secret and header name come from your PaymentSetu configuration.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Your success rule should be strict: known <code>client_txn_id<\/code>, exact stored amount, verified signature, successful status and a new UTR. Record the UTR and webhook event ID if supplied. If the same event arrives twice, return <code>200<\/code> after confirming it was already applied rather than creating a second fulfilment.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 6: Host it on shared hosting or a serverless function<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why this matters: a static front end still needs a public, private, HTTPS-capable execution point for the two server calls.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On shared PHP hosting:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Upload <code>create-order.php<\/code> and <code>payment-webhook.php<\/code> outside the public HTML folder if your host allows it, or protect every other file in that directory.<\/li>\n\n\n<li>Set <code>PAYMENTSETU_API_KEY<\/code> and <code>PAYMENTSETU_WEBHOOK_SECRET<\/code> in the host environment, not in JavaScript.<\/li>\n\n\n<li>Confirm PHP cURL and HTTPS certificate validation are enabled.<\/li>\n\n\n<li>Point your PaymentSetu webhook setting at <code>https:\/\/your-domain.example\/api\/payment-webhook.php<\/code>.<\/li>\n\n\n<li>Replace <code>example.com<\/code> in the create-order code with your real HTTPS domain.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">On a serverless platform, deploy the same two handlers as separate functions. Put the API key and webhook secret in encrypted environment variables, and return a response quickly from the webhook after the signature and idempotency checks. Use your database for pending orders because a serverless function\u2019s local filesystem is not a reliable order store.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Success looks like a public HTTPS endpoint that returns JSON, keeps the API key off the page, accepts a signed webhook, and can find an order after a page refresh.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Going-live checklist<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Run one small real payment before sending customers to the page. Check each item:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>The amount comes from a server-side product lookup, not only from an HTML input.<\/li>\n\n\n<li>The QR or intent shows the correct merchant details and amount.<\/li>\n\n\n<li>A customer can pay from a phone while the website is open on another device.<\/li>\n\n\n<li>The order remains pending until a verified webhook arrives.<\/li>\n\n\n<li>A fake signature gets HTTP 401 and changes nothing.<\/li>\n\n\n<li>A repeated webhook does not fulfil the order twice.<\/li>\n\n\n<li>The UTR, amount, order ID and timestamp are stored for reconciliation.<\/li>\n\n\n<li>Your API key and webhook secret do not appear in page source, browser logs or Git history.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">For a larger HTML shop, you can move to a ready integration later. PaymentSetu\u2019s <a href=\"https:\/\/paymentsetu.com\/woocommerce-plugin\">WooCommerce plugin<\/a> handles the order-status connection without custom API work; the underlying principle remains the same: the customer pays your merchant account and the payment is verified before the order is updated.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The UPI button does nothing.<\/strong> Test the <code>upi:\/\/<\/code> link on a mobile device with a compatible UPI app. Keep the QR option available because a desktop browser cannot open a mobile app on every device.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The QR is displayed but the order is not marked paid.<\/strong> Check that the webhook URL is public HTTPS, the API key and webhook secret belong to the same account, and the stored <code>client_txn_id<\/code> is the one sent when the QR was created. Review the webhook delivery record and your PHP error log.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The webhook returns 401.<\/strong> Verify the exact header name and signature encoding from your PaymentSetu dashboard. Calculate the HMAC over the untouched request body, not over a re-encoded JSON object.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The page says payment succeeded after a redirect, but the order is still pending.<\/strong> Keep the order pending until your server receives and verifies the webhook. A redirect can tell you where the customer\u2019s browser went; it does not replace server-side payment verification.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The API says there are no credits.<\/strong> Check the account\u2019s credit balance with <code>GET \/api\/check_credits<\/code>, then choose the plan that matches your expected successful verifications. Do not display a \u201cpaid\u201d state just because order creation returned a QR.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Can I add UPI payments to a website made with only HTML?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes. A static HTML page can show a UPI deep link or QR code. Automatic order confirmation needs a small backend or serverless function because API keys, price validation and webhook verification should not run in public browser code.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is a UPI QR code enough for automatic payment confirmation?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. A QR starts the payment but does not give your static page a trusted order-status event. Use a unique dynamic order and a signed webhook when fulfilment must happen automatically.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I use a UPI link on desktop?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You can place the link on a desktop page, but <code>upi:\/\/pay<\/code> is intended to hand off to a compatible mobile payment app. Include a QR code that can be scanned from another device and test the experience on the phones your customers use.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does PaymentSetu hold the customer\u2019s money?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. PaymentSetu is a payment verification service, not a payment gateway. The customer pays directly to your connected Paytm Business or PhonePe Business merchant account; PaymentSetu matches the payment and sends the webhook.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Which PaymentSetu plan is suitable for a small HTML site?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Starter costs \u20b9399 per 30 days and includes 100 credits, with one credit representing one successful payment verified. Pro costs \u20b9999 per 30 days and includes 1,000 credits plus priority support; review the <a href=\"https:\/\/paymentsetu.com\/#pricing\">current pricing<\/a> before choosing.<\/p>\n\n\n\n<aside class=\"ap-cta\" aria-label=\"Verify UPI payments automatically\"><div class=\"ap-cta__content\"><p class=\"ap-cta__eyebrow\">Plain HTML checkout<\/p><p class=\"ap-cta__title\">Verify UPI payments automatically<\/p><p class=\"ap-cta__text\">Keep your static site and add dynamic QR, API access and signed webhooks.<\/p><\/div><a class=\"ap-cta__btn\" href=\"https:\/\/paymentsetu.com\/auth\/register\">Create your account<\/a><\/aside>\n\n\n\n<p class=\"wp-block-paragraph\">DONE add-upi-payment-html-website words=1823<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Can I add UPI payments to a website made with only HTML?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Yes. A static HTML page can show a UPI deep link or QR code. Automatic order confirmation needs a small backend or serverless function because API keys, price validation and webhook verification should not run in public browser code.\"}}, {\"@type\": \"Question\", \"name\": \"Is a UPI QR code enough for automatic payment confirmation?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. A QR starts the payment but does not give your static page a trusted order-status event. Use a unique dynamic order and a signed webhook when fulfilment must happen automatically.\"}}, {\"@type\": \"Question\", \"name\": \"Can I use a UPI link on desktop?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"You can place the link on a desktop page, but upi:\/\/pay is intended to hand off to a compatible mobile payment app. Include a QR code that can be scanned from another device and test the experience on the phones your customers use.\"}}, {\"@type\": \"Question\", \"name\": \"Does PaymentSetu hold the customer\u2019s money?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. PaymentSetu is a payment verification service, not a payment gateway. The customer pays directly to your connected Paytm Business or PhonePe Business merchant account; PaymentSetu matches the payment and sends the webhook.\"}}, {\"@type\": \"Question\", \"name\": \"Which PaymentSetu plan is suitable for a small HTML site?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Starter costs \u20b9399 per 30 days and includes 100 credits, with one credit representing one successful payment verified. Pro costs \u20b9999 per 30 days and includes 1,000 credits plus priority support; review the current pricing before choosing. DONE add-upi-payment-html-website words=1823\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Learn payment gateway integration in html website with a UPI link, QR, tiny PHP backend, dynamic orders and signed webhooks, step by step today.","protected":false},"author":1,"featured_media":695,"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,225,226,224,28],"class_list":["post-696","post","type-post","status-publish","format-standard","has-post-thumbnail","category-upi-payment-verification","tag-dynamic-qr","tag-html-website","tag-php-integration","tag-upi-payment","tag-webhooks","cs-entry"],"_links":{"self":[{"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts\/696","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=696"}],"version-history":[{"count":1,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts\/696\/revisions"}],"predecessor-version":[{"id":919,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts\/696\/revisions\/919"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/media\/695"}],"wp:attachment":[{"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/media?parent=696"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/categories?post=696"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/tags?post=696"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}