BUILD WITH QUANTUM

Developer docs.

Integrate payment order creation and status checks into your website, app or bot. Payment confirmation is server-side and must not rely on the payer returning from a UPI app.

Before you start: Create an account, activate a subscription and generate an API key. Set your receiving UPI ID in Merchant Settings.

Base URL

All API endpoints are relative to your installation URL.

https://www.fampay.starspacemovie.xyz/api/create_order.php
https://www.fampay.starspacemovie.xyz/api/order_status.php

Send your key in the X-API-Key header. Query-string API keys are supported for quick testing only; headers are recommended.

1. Create order

POST JSON to /api/create_order.php.

curl -X POST 'https://www.fampay.starspacemovie.xyz/api/create_order.php' \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: YOUR_API_KEY' \
  -d '{"amount":499,"order_id":"ORDER-1001","customer_name":"Customer"}'

Successful response includes order_id, status=pending, checkout_url, upi_uri and expires_at.

2. Check order status

curl 'https://www.fampay.starspacemovie.xyz/api/order_status.php?order_id=ORDER-1001' \
  -H 'X-API-Key: YOUR_API_KEY'

Possible states: pending, success, expired, failed. Treat only success as paid.

3. Checkout and verification

The checkout presents the UPI intent and QR. Your server should poll order status. The notification verifier needs to be configured with the exact sender and message format used by the payment app. Until a unique transaction reference and exact amount can be confidently matched, leave the order pending.

Do not mark an order successful from a screenshot, QR scan, browser redirect, or user-provided UTR alone.

Error codes

401 missing_api_key / invalid_api_key — send a valid API key.
402 subscription_inactive — renew the merchant subscription.
422 invalid_amount — use a valid INR amount.
409 duplicate_order_id_or_database_error — use a unique order ID.
404 order_not_found — the order does not belong to that key.