Payment Gateway API Integration for Developers — India

Integrate VyaparGateway payment gateway in your website: dynamic UPI QR, pay links, server-verified payments, and webhooks for ecommerce, Shopify, and WordPress — without exposing API secrets on public pages. This guide is text-first so it loads fast for users and crawlers (better LCP on the marketing shell). For Shopify, WordPress, webhook, and comparison guides, see the blog.

Who this is for

Engineering leads at D2C brands, SaaS teams billing in INR, agencies wiring WooCommerce or headless Shopify, and startups that need a single integration surface for UPI across mobile and web. If you can run HTTPS and verify HMAC, you can integrate.

What you integrate

  • Order & QR creation — Create payable sessions, return a hosted pay link or encoded UPI intent, and track status as customers pay from PhonePe, GPay, Paytm, or any UPI app.
  • Server-to-server verification — Poll or reconcile transaction state from your backend before you ship physical goods, unlock subscriptions, or credit wallets.
  • Signed webhooks — Receive JSON callbacks and verify X-VyaparGateway-Signature / X-VyaparGateway-Timestamp with your dashboard webhook secret.

Integration checklist

  1. Create a merchant account and complete onboarding.
  2. In the dashboard, open API Keys & Webhooks and configure a TLS webhook URL.
  3. Implement pay-session creation from your backend using your API key (never expose keys in mobile clients).
  4. Verify webhook signatures before mutating order state; reject replays and stale timestamps.
  5. Test with small INR amounts and your QA devices before going live.

Dashboard-only docs & keys

API documentation (endpoints, examples, errors) and the Plugins guide open only after sign-in, inside the merchant app with the sidebar. Your API keys and webhook secrets live under API Keys & Webhooks.

Open API documentationCreate merchant accountProduct overview

Platforms & patterns

Shopify (including headless), WordPress & WooCommerce, SaaS with usage-based billing, D2C Next.js or custom storefronts — same APIs; different glue code. After login, use the Plugins page for platform-specific talking points.

Plugins & integrations (sign in) →

Base URL & regions

Production REST is typically under /api/v1/ on vyapargateway.com or your deployed API host. Content on this page targets India (en-IN) and UPI settlement patterns; keep compliance review with your payments partner.

Partners: earn a backlink

If you write an integrations directory, case study, or tools page, you can link to VyaparGateway — quality backlinks help discovery. Suggested HTML (copy as-is):

<p><a href="/" rel="noopener noreferrer" title="VyaparGateway — UPI for Indian businesses">VyaparGateway</a> — UPI collection &amp; webhooks for Indian merchants.</p>

Backlinks are earned on other sites; we cannot create them automatically — only make it easy for partners who already want to cite you.

FAQ

Common questions below match structured data on this page for rich results eligibility.

What is VyaparGateway for developers?
VyaparGateway is merchant-side software to collect UPI via dynamic QR, verify payments server-side, and receive signed webhooks. You integrate HTTPS APIs and optional hosted pay flows — we are not a bank; you use your own compliant UPI acceptance context where required.
Do I get API keys without signing up?
No. API keys and webhook secrets are issued only inside the merchant dashboard after you create an account and complete onboarding. This page is an overview for SEO and discovery; it never embeds credentials.
Can I use VyaparGateway with Shopify or WooCommerce?
Yes. Merchants use server-side or app-bridge patterns: create pay sessions from your backend, show QR or redirect, then confirm status via API or webhooks before fulfilment. See the Plugins section in the dashboard after sign-in.
How do webhooks stay trustworthy?
We sign payloads with HMAC using your webhook secret. Your server must verify X-VyaparGateway-Signature (and timestamp) against the raw body before updating order state — same pattern as Stripe or similar providers.
What is the API base URL in production?
REST lives under your deployment’s host, typically https://vyapargateway.com/api/v1/ when the API is same-origin, or a dedicated API hostname if you configure one. Exact paths and examples are in the authenticated API documentation.
Is there a sandbox?
Use a staging or test merchant account and low-value flows with your team’s test UPI apps where your acquirer allows it. Product-specific sandbox policy is documented for merchants in the dashboard.
How does pricing affect integration?
Billing is subscription-oriented with plan limits; platform positioning emphasizes zero *platform* per-transaction fees — settlement still follows your bank and UPI PSP rules. Integration code does not change per transaction fee tier beyond plan feature flags.
Who should I contact for integration support?
Email [email protected] with your stack (e.g. Node, Laravel, Django), storefront, and timelines. For sensitive data, avoid pasting live API keys in email — use redacted snippets only.

Engineering contact: [email protected]