Direct Benefit Transfer (DBT)

What it does

A scheme department sends a list of people owed a benefit. Before any money moves, each record is checked against Aadhaar for name and gender, for duplicates, and against the department’s limits on amount and count. Only the records that pass go to the bank, and the bank’s result comes back against each one, so a failed transfer is a named record, not a missing rupee.

Who uses it

The scheme department submits the beneficiary data from its portal, and a validation engine does the checking. The bank processes the payments over AePS through a secure file transfer and returns the status, and the beneficiary receives the money in the linked account.

How it runs

The scheme portal sends the beneficiary data, each record is verified against the UIDAI-authorised Aadhaar service, amounts, counts and duplicates are rechecked against the department’s threshold, validated records go to the bank by SFTP for AePS payment, and the bank status is synced back with invalid records returned to the source.

In government, and in a private business

For a scheme department, the reconciliation that today drags on long after a payment run happens per record, and the officer can say exactly which beneficiaries were paid, which were rejected and why. Duplicates are stopped before the bank sees them.

Paying scheme benefits to citizens is public money work with no owner-run business equivalent as such. The validate, pay and reconcile pattern behind it is what a company would want for bulk payouts to workers or agents.

How it runs, step by step

1. Data intakeScheme portal sends beneficiary DBT data.
2. Aadhaar validationName, Aadhaar and gender verified via UIDAI-authorised API.
3. De-duplicationRecheck amount, count and duplicates against department threshold.
4. Bank paymentValidated data sent to bank SFTP for AePS payment.
5. ReconciliationBank status synced back; invalid records returned to source.