FOR INDEPENDENT MERCHANTS & DEVELOPERS

Your payments.
Your UPI.
STORM PAY.

Give your customers a simple UPI checkout. Manage payment links, connect your FamApp receipt inbox, and bring your applications into the same workspace.

✓ Direct UPI payments✓ Your own receiving account✓ Signed webhooks
STORM PAY / CHECKOUTILLUSTRATION
S
Sample merchantUPI checkout
Amount to pay₹499.00

Your payment QR appears here
when a merchant creates an order.

Payment destinationMerchant’s UPI ID
Order statusAwaiting payment
A clear checkout. A traceable order.
PAYMENT LINKSUPI CHECKOUTMERCHANT APIRECEIPT RECONCILIATIONWEBHOOK EVENTS
CONNECT. CREATE. RECONCILE.

From your account to your application.

Every merchant has a separate workspace and receiving account.

01 / CONNECT

Make it your own.

Register, get administrator approval, and connect the Gmail inbox receiving your FamApp credit emails with your UPI ID.

02 / CREATE

Share a checkout.

Create a payment link in the dashboard or use the API. Customers scan a QR or open their UPI app to pay you directly.

03 / CONFIRM

Keep records in sync.

Authenticated receipts with an exact order reference can confirm automatically. Review unmatched receipts, then notify your app with a signed webhook.

ONE MERCHANT WORKSPACE

Built around the way you collect.

Open your workspace ↗
↗

Hosted payment links

A shareable, mobile-friendly checkout with UPI QR, app intents and payment status.

⌘

Developer API

Create orders and check their status from your backend with merchant API keys.

⌁

Signed notifications

Receive payment confirmation events with HMAC signatures and queued retries.

✓

Receipt review

Keep unmatched credits visible and reconcile them to the correct customer and order.

◎

Separate merchant accounts

Your orders, inbox connection, API credentials and transaction history stay in your workspace.

ϟ

Direct UPI collection

Payments go to the merchant’s configured UPI account. STORM PAY does not hold customer funds.

SMALL API. CLEAR RESPONSES.

Connect your shop,
app or bot.

Use an idempotency key when creating orders. Verify payment on your backend before fulfilling a purchase.

Read integration documentation →
POST /api.php?action=create-order
X-Api-Key: YOUR_MERCHANT_KEY
Idempotency-Key: checkout-123

{
  "amount": "499.00",
  "customer_name": "Your customer"
}

→ order_id · checkout_url · upi_intent
BEFORE YOU START

A few things to know.

Who enters the Gmail and UPI details?

Each merchant enters their own Gmail address, dedicated Google app password and receiving UPI ID after registration and approval. Never share these credentials in chat.

Is every payment confirmed automatically?

Automatic matching requires an authenticated receipt containing the exact order reference, amount and payment time. If the email lacks the order reference, the receipt needs merchant review. A payment note is not guaranteed to appear in a FamApp email.

Where does the customer’s money go?

The customer pays the merchant’s configured UPI ID directly. STORM PAY records and reconciles payments; it does not collect, hold or refund those funds.

Is STORM PAY an official FamPay product?

No. STORM PAY is an independent merchant application. FamApp and FamPay names belong to their respective owners.

YOUR NEXT PAYMENT STARTS HERE

Put your UPI payments
in one workspace.

Create merchant account →