Put DuePe's services inside your own app

Fintech apps, retailer networks and enterprises connect to DuePe through secure B2B APIs: recharge, BBPS, DMT, AEPS, travel, gift cards, wallet ledger, callbacks and reports.

API / business partnershipHow it works
  • Recharge and BBPS
  • DMT and AEPS
  • Travel and gift cards
What you get

API areas

  • Recharge and BBPSOperator detection, plan fetch, bill fetch, payment, receipt and complaint references.
  • DMT and AEPSSender and beneficiary management, transfers, Aadhaar transactions, bank references and reversals.
  • Travel and gift cardsAvailability, booking, cancellation, catalogue and voucher issue for bus, train, flight and gift card products.
  • Wallet, callbacks, reportsLedger entries, idempotent request IDs, transaction callbacks, status APIs and reconciliation reports.
https://api.duepe.com
POST/v1/rechargeRecharge and BBPS
POST/v1/bbps/payRecharge and BBPS
POST/v1/dmt/transferDMT and AEPS
POST/v1/aeps/withdrawDMT and AEPS
GET/v1/travel/searchTravel and gift cards
GET/v1/wallet/ledgerWallet, callbacks, reports
GET/v1/status/{request_id}Wallet, callbacks, reports
How it works

From sandbox to production

  1. 1

    Partner review

    Business details, use case, services required and integration ownership.

  2. 2

    Sandbox

    Credentials, endpoints, request format, callback URL and sample responses.

  3. 3

    Transaction testing

    Success, pending, failed, reversal and report cases validated before go-live.

  4. 4

    Go live

    Production access with service limits, wallet process, IP rules and escalation contacts.

For shopkeepers and partners

What a stable integration rests on

Sandbox today, production when every case passes.

API / business partnershipTalk to our team

Authentication and IP control

Partner-level credentials, service permissions and IP allow-lists, so only your servers can call your account.

Idempotency and callbacks

Unique request IDs prevent duplicate debits on retry; callbacks and status APIs cover pending responses.

Reconciliation

Every request matches a wallet entry, commission, settlement and support case, so month-end reconciliation is a report, not a project.

Common questions

Questions from developers

Is there a sandbox?

Yes. After partner review you receive sandbox credentials, endpoint documentation, a callback setup and sample responses for every state.

How are pending transactions handled?

A callback is sent when the final state is known, and a status API lets you query by your request ID at any time.

How is the wallet funded?

Prepaid: you fund your DuePe wallet, every request debits it with a ledger entry, and reversals credit it back automatically.

Which services are available by API?

Recharge, BBPS bill payments, money transfer, AEPS, travel and gift cards, together with the wallet ledger, callbacks and reports.

Who can apply for API access?

Fintech apps, retailer networks, cooperative societies, lenders and enterprises with a registered business; access follows a partner review.

Is IP whitelisting supported?

Yes. Production access uses partner-level credentials with IP allow-lists, so only your servers can call your account.

Partner with us
For distributorsDistributor programmeOnboard retailers, fund their wallets, switch services on and off, and watch every transaction on one dashboard, with a share on everything your shops make.Partner with usBecome a DuePe CSPCommission on every transaction, credited the same dayAll BBPS billersPay billsElectricity, water, gas, LPG, broadband, FASTag, insurance and loan EMIs, fetched by consumer number and paid with a receipt.