Do I need both polling and webhooks?

Webhooks should be your primary confirmation path. Status checks are useful for support tools, reconciliation, or rare recovery scenarios—not as a substitute for webhook trust.

Can I use the API from the browser?

Do not call authenticated create-order endpoints directly from browsers if that exposes credentials. Proxy through your server or edge function.

Is the popup checkout a separate API?

No. Popup mode uses the same payment_url from create-order—only the presentation layer changes. See JavaScript SDK.

UPI payments for Indian businesses

UPI payment gateway API for modern stacks

One HTTP API to originate payments, one webhook to finalize them. Upibridge offers redirect checkout by default and optional popup checkout (free) for smoother UX. Webhook delivery is the only reliable source of truth for payment success—see webhook documentation.

Start free Read the docs

How Upibridge checkout works

Redirect checkout is the default: customers complete UPI payment in a full-page flow.
Popup checkout is an optional, free upgrade for UX—open the same payment URL in a focused window when browsers allow it.
Webhook is the only source of truth for payment success. Always confirm funds and order fulfillment server-to-server from your webhook handler.
Treat redirect/return URLs and client-side callbacks as UX hints only—not proof of payment.

Webhook verification guide · Popup checkout (JavaScript SDK)

Product Features

POST /api/create-order

Returns a payment_url for redirect or popup checkout—amount, customer mobile, order id, and redirect_url in JSON.

POST /api/check-order-status

Poll transaction state when you need a backstop—useful for ops dashboards and reconciliation.

Webhook callbacks

Receive structured, server-to-server callbacks when payments settle—ideal for fulfillment automation.

Multi-language examples

Copy-ready snippets for PHP, JavaScript, and Python in our public docs—no vendor lock-in sample apps required.

SDK-ready popup flow

Load our lightweight JS helper to open payment_url in a popup when policy allows, with graceful redirect fallback.

Transparent error model

Structured JSON responses for duplicate order id, validation issues, and downstream provider errors.

Flow How it works

1

Obtain credentials

Create an Upibridge merchant account and gather your API user token from the dashboard.
2

Create order server-side

Call create-order from your backend (never expose secrets in mobile clients without a proxy).
3

Send customers to payment_url

Use full redirect or optional popup checkout via our JavaScript SDK.
4

Verify webhook

Parse fields, validate authenticity per our webhook guide, and upsert order state idempotently.

Developers Integration

Jump to Create order reference, Check order status, Webhook format, and PHP example / JavaScript SDK.

Frequently asked questions

Do I need both polling and webhooks?: Webhooks should be your primary confirmation path. Status checks are useful for support tools, reconciliation, or rare recovery scenarios—not as a substitute for webhook trust.
Can I use the API from the browser?: Do not call authenticated create-order endpoints directly from browsers if that exposes credentials. Proxy through your server or edge function.
Is the popup checkout a separate API?: No. Popup mode uses the same payment_url from create-order—only the presentation layer changes. See JavaScript SDK.