Buckzy is the gateway. Your store keeps the cart and catalog. We give you UPI Intent, Collect, QR, cards, netbanking and wallets behind one Order API and one webhook.
curl https://api.buckzy.com/v1/orders \ -u rz_test_bckz_live_demo: \ -d amount=2499 \ -d currency=INR \ -d receipt=ATLAS-1042 \ -d methods[]=upi_intent \ -d methods[]=upi_collect \ -d methods[]=upi_qr \ -d methods[]=card \ -d methods[]=netbanking
One order object. The hosted checkout (or your own UI via our tokens) collects on these methods.
Launch GPay, PhonePe, Paytm, BHIM with a native intent. Highest conversion on mobile.
Push a collect request to a VPA. Customer approves in their app.
Dynamic QR per order. Desktop and store-counter flows.
Visa, Mastercard, RuPay, Amex. 3DS2 on the hosted page so PAN never hits you.
Redirect to the issuing bank. Status confirmed only on callback + webhook.
MobiKwik, Amazon Pay, Paytm wallet as fallback rails.
Your backend calls Buckzy with amount, receipt and allowed methods. You get an order_id and a checkout URL.
Redirect to Buckzy hosted checkout. Intent / collect / QR / card / NB / wallet all sit on that page.
payment.captured is the source of truth. Then fulfill the order. The dashboard shows the same ledger.
A fake ecommerce site that calls createOrder and sends the shopper to Buckzy checkout.
Orders, payments, webhooks and the rule that the browser return URL is never enough.
The ops dashboard from your screenshots. Live sandbox payments land here.
This is a demonstration stack in the browser. A production Buckzy would sit on a sponsor bank nodal account, NPCI access and PCI-scoped card fields. The API shapes and the ledger math are the same.