Introduction

BucksBox is a bank-grade fintech platform offering money transfer (DMT), Aadhaar-enabled payments (AEPS), and UPI/QR collection services.

There are two APIs, for two different callers — pick the one that matches who's integrating:

Who it's forAuthDocs
Merchant APIA merchant integrating for itselfJWT Bearer, direct to paymentSystem/services/
Partner APIAn aggregator/reseller managing multiple merchantsAPI key + AES-256-GCM, via fintech-gateway/vendor/

Both reach the same underlying AEPS/DMT/UPI operations on paymentSystem — they differ in transport and in whose identity a call carries. A merchant's JWT already says which merchant it is; a partner's API key doesn't, so partner calls include a merchantId field to say which managed merchant the call is for.

Architecture

Merchant's own app                    Partner's backend system
      │                                     │
      │ Authorization: Bearer <JWT>         │ X-Client-Id + AES-256-GCM body
      │             +                       | X-Client-Id + AES-256-GCM body
      │ X-Client-Id + AES-256-GCM body      │
      ▼                                     ▼
  paymentSystem(BUCKS-SWITCH)  ◄───────────────────   gateway
  (direct)                             (decrypts, verifies, forwards with
      │                                 X-Api-Key: <partner's own apiKey>)
      │
      └─► Bank / UPI System / AEPS SYSTEM / DMT SYSTEM

Partner account-management calls (profile, wallet, managed merchants, commission) skip the gateway entirely — same direct JWT flow as a merchant, just for the partner's own account. See the Partner API overview for the full picture of which calls use which transport.

Base URLs

Environmentfintech-gateway (Partner API)paymentSystem (Merchant API)
Productionhttps://api.bucksbox.in/gatewayask your integration contact — not fixed in this documentation set
Staginghttps://api.bucksbox.in/gateway-stageask your integration contact — not fixed in this documentation set

Where to go next