Merchant payment collections for wholesalers and distributors | DASNET
A reliable collection workflow makes payment instructions, order references and final status visible to the people responsible for fulfilment and finance.
This guide explains the workflow, how to prepare, which checks matter and how to handle common exceptions for wholesalers and distributors.
Explore DASNETDeveloper documentation
Understand the workflow, apply the checklist, and confirm which payment channels and features are enabled for your account before using them in production.
What Merchant payment collections means for wholesalers and distributors
A reliable collection workflow makes payment instructions, order references and final status visible to the people responsible for fulfilment and finance. For wholesalers and distributors, the goal is to manage larger orders, customer balances and supplier obligations. A reliable workflow makes the request, responsible person, reference and final outcome visible rather than leaving the process in disconnected messages.
The operational challenge
A common challenge is that orders, partial fulfilment and multiple payments create reconciliation complexity. When the source request, payment status and business record do not line up, staff can repeat work or act on an assumption. A consistent process separates initiation from completion and records the evidence used to make a decision.
A practical end-to-end workflow
- Choose the enabled collection route and confirm the correct merchant destination.
- Show the customer the exact amount, business identity and purpose before payment.
- Match confirmed transactions to orders, invoices or customer accounts.
- Review failed, pending, reversed and unmatched payments as separate exceptions.
A workflow shaped around this use case
- Use a distinct reference for each order and payment allocation.
- Record partial fulfilment and partial payments explicitly.
- Review credit limits, returns and outstanding balances before dispatch.
How DASNET fits
DASNET is a business workspace for supported payment workflows and everyday business operations. Depending on account configuration, teams may use it to manage payment requests and collections, review transaction records, handle supported wallet and payout activity, organise invoices or bills, and keep customer and operational information together. The precise menu, channel and automation available to a business should be confirmed in its account. DASNET is not a promise that every payment rail, bank destination or provider feature is automatically enabled.
Controls and measures to review
- Track the number of unresolved items and how long they remain open.
- Separate pending, successful, failed, reversed and disputed outcomes in reports.
- Keep a clear owner for exceptions and a reference for every consequential action.
- Review access permissions and avoid storing credentials or sensitive authentication data in notes.
- Compare material payment totals with trusted provider or bank records.
Frequently asked questions
Can all collections settle to the same destination?
Destination depends on the enabled route and merchant configuration. Confirm the setup before publishing payment instructions.
What should staff do when a customer shows an SMS?
Follow the business verification process and check the trusted transaction record rather than relying only on a screenshot.
How should unmatched payments be handled?
Keep an exception record, investigate reference and amount details, and document the resolution.
Can reports replace statements?
No. Reports help analyse activity; reconcile important totals against source records.
How does this apply to wholesalers and distributors?
The main objective is to manage larger orders, customer balances and supplier obligations. Start with the workflow and controls on this page, then verify the exact features enabled for your DASNET account.
What should we do if a payment or record looks wrong?
Pause any consequential action, keep the non-sensitive reference and timestamp, check the trusted source record, and follow your documented support or reconciliation process. Never share PINs, OTPs, passwords or API secrets.
Does DASNET guarantee that every feature is enabled?
No. Product availability depends on account setup, permissions, provider approvals and enabled services. Confirm the live configuration before making operational commitments.
Related DASNET guides
Continue with these related workflows:
M-Pesa STK Push for wholesalers and distributors · STK Push integration guide for wholesalers and distributors · Safaricom Daraja API workflows for wholesalers and distributors · Online payment links for wholesalers and distributors · Customer payment requests for wholesalers and distributors · Bulk payouts and bulk payments for wholesalers and distributors