DMT API in India: Complete Guide to Domestic Money Transfer

Millions of people in India still send money home in cash — migrant workers, daily-wage earners and small traders who either have no bank account of their own, or find it easier to walk into a neighbourhood shop than to use a banking app. Domestic Money Transfer (DMT) serves exactly this need: a customer hands cash to a retail agent, and the money lands in a family member's bank account anywhere in India within seconds.

For fintech platforms, distributors and retail networks, a DMT API is how that service gets built. In this guide we explain what a DMT API does, walk through the transaction flow step by step, cover the compliance rules you must follow, and show what to look for when choosing a provider.

What is a DMT API?

A DMT API is an interface that lets your application send money from a remitter (the person paying) to a beneficiary bank account through a licensed banking partner. Instead of partnering with a bank directly, building IMPS connectivity and running your own compliance stack, you integrate one API from a fintech infrastructure provider that already has those bank relationships in place.

The API typically covers the whole lifecycle: registering and verifying the remitter, adding and validating beneficiaries, executing the transfer over IMPS (or NEFT as a fallback), and reporting the final status, commission and settlement back to your system.

Who Uses DMT in India?

• Retail agents and kirana stores that offer money transfer alongside recharges, bill payments and AePS cash withdrawal.
• Distributors and super-distributors who run networks of retailers and earn on every transaction their network processes.
• Fintech apps and B2B platforms that want to add remittance as a revenue line without becoming a bank.
• Business correspondents serving semi-urban and rural areas where bank branches are far away.

For the end customer the value is speed and convenience. For the retailer it is a service fee or commission on every transfer, plus more footfall for the other services in the shop.

How a DMT API Works (Step-by-Step)

1. Remitter registration: The retailer enters the customer's mobile number. If the remitter is new, the API registers them — the mobile number is verified by OTP and the remitter's identity details are captured as required by the banking partner.
2. Beneficiary addition: The retailer adds the recipient's bank account number and IFSC. The beneficiary is linked to that remitter so repeat transfers take seconds.
3. Account verification (penny drop): Before the first transfer, the API can verify the beneficiary account — typically by sending ₹1 and reading back the account holder's name from the bank. This catches typos and prevents money going to the wrong person.
4. Transaction authentication: Each transfer is authorised by the remitter, usually with an OTP sent to their registered mobile number.
5. Fund transfer: The provider debits the retailer's wallet and pushes the transfer to the beneficiary bank over IMPS, which runs 24x7 including holidays. If IMPS is unavailable at the beneficiary bank, a good provider can route through an alternative channel.
6. Status and callback: The API returns a bank reference number (UTR/RRN) and fires a webhook with the final status. Transactions that come back as pending are resolved later through status checks, and failed transfers are refunded to the retailer's wallet.

Compliance: KYC and RBI Rules

DMT is a regulated activity. The service runs under a partner bank, and the Reserve Bank of India sets the framework for how cash-based domestic remittances work — including remitter registration, authentication of each transaction, and caps on how much a remitter can send per transaction and per month. RBI revised this framework in 2024 to tighten remitter verification and add remitter details to the transaction message.

In practice, this means:

• Retailer KYC is mandatory. Every agent must complete onboarding and verification before DMT is activated on their account.
• Remitters must be registered and verified with a mobile number and identity details before they can send money.
• Transaction limits apply. Per-transaction and monthly limits are set by regulation and the partner bank. Always confirm the current limits with your provider rather than relying on older figures you find online.
• Records must be kept for audit and suspicious-transaction monitoring.

A reliable DMT provider builds these checks into the API itself, so your platform stays compliant as rules change without you having to rewrite your integration.

Key Features to Look For in a Provider

• Multi-bank routing: Transfers routed across more than one banking partner keep success rates high when a single bank's systems are slow or down.
• Built-in beneficiary verification: Penny-drop name matching before the first transfer reduces wrong-account disputes.
• Clear pending-transaction handling: Every DMT system sees pending transactions. What matters is a status-check endpoint, automatic reconciliation and fast refunds for failures.
• Real-time webhooks: Callbacks for success, failure and refund so your ledger never drifts from the bank's.
• Commission and settlement reports: Distributors need to see earnings per retailer and per transaction, not just a wallet balance.
• Security: Encrypted traffic, IP whitelisting and signed requests to protect wallet balances.

DMT API vs White Label DMT Platform

If you are still deciding, our guide to API vs white label fintech platforms compares both models in more depth.

How to Integrate a DMT API

The exact endpoints vary by provider. The flow below is illustrative and shows the typical sequence of calls.

Step 1: Authenticate. Sign every request with your API credentials and call only from whitelisted server IPs — never from the mobile app directly.

Step 2: Look up or register the remitter.

POST /dmt/remitter/lookup
{ "mobile": "9876543210" }

Step 3: Add and verify the beneficiary.

POST /dmt/beneficiary
{
  "remitter_mobile": "9876543210",
  "account_number": "123456789012",
  "ifsc": "SBIN0001234",
  "verify": true
}

Step 4: Send the transfer after the remitter confirms the OTP.

POST /dmt/transfer
{
  "remitter_mobile": "9876543210",
  "beneficiary_id": "BEN_48213",
  "amount": 2500,
  "mode": "IMPS",
  "reference_id": "TXN_20260928_0001"
}

Step 5: Handle the callback. Update your ledger on the webhook, show the UTR on the customer receipt, and poll the status endpoint for any transaction still pending.

Test pending, failed and refunded cases in the sandbox before going live. Those edge cases, not the happy path, are what generate support calls.

Conclusion

DMT remains one of the most-used services at India's assisted retail outlets. It is used often, trusted by customers, and a steady source of commission for retailers and distributors. The hard parts are bank connectivity, compliance and reconciliation, and a good DMT API provider takes those off your plate.

Merchant247 offers a DMT API and white label DMT platform with remitter and beneficiary management, account verification, multi-bank routing and real-time commission tracking. It sits alongside AePS, BBPS and recharge on one platform. Want to understand the payment rails underneath? Read IMPS vs NEFT vs RTGS for businesses.