Why are webhooks mandatory for production?

Browsers are unreliable witnesses. Webhooks are server-to-server with definitive payment outcomes.

Is popup checkout a different API?

No—only presentation changes. See JavaScript SDK.

API integration overview

Integrate Upibridge in four layers: create order on your server, present checkout (redirect by default; optional popup via our JS SDK), and confirm payment exclusively through webhooks. Use check-order-status for operations—not as your primary success signal.

Prerequisites

Upibridge merchant account and user token (dashboard).
HTTPS-accessible webhook endpoint with fast HTTP responses and idempotent processing.
Server that can call POST https://upibridge.com/api/create-order with JSON.

Architecture

Backend creates an order and maps your internal order id.
Customer opens payment_url—full-page redirect (default) or optional popup.
Webhook notifies your backend—only source of truth for fulfillment.
Optional polling via check-order-status for support tooling.

Checkout modes

Redirect checkout is the default. Popup checkout is a free, optional UX enhancement using the same payment_url. Regardless of mode, finalize from webhooks.

Next steps

Product: UPI gateway, UPI payment gateway API, Blog.

Frequently asked questions

Why are webhooks mandatory for production?: Browsers are unreliable witnesses. Webhooks are server-to-server with definitive payment outcomes.
Is popup checkout a different API?: No—only presentation changes. See JavaScript SDK.