Customer payment requests for multi-branch businesses | DASNET
A payment request records who needs to pay, why payment is due, the amount, and the reference used to match the resulting transaction.
This guide explains the workflow, how to prepare, which checks matter and how to handle common exceptions for multi-branch businesses.
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 Customer payment requests means for multi-branch businesses
A payment request records who needs to pay, why payment is due, the amount, and the reference used to match the resulting transaction. For multi-branch businesses, the goal is to standardise workflows while preserving branch-level visibility. 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 branches may use inconsistent references, permissions and end-of-day processes. 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
- Create a request with the customer, amount, purpose and due date where supported.
- Check contact details and share the request with the intended payer.
- Track the request separately from the payment status; an issued request is not a settled payment.
- Resolve partial payments, cancellations and disputes using a documented process.
A workflow shaped around this use case
- Standardise reference formats, status definitions and approval rules.
- Give staff access only to the records they need.
- Compare branch reports with consolidated source records.
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
Is a request the same as a receipt?
No. A request asks for payment; a receipt records a payment that has been confirmed.
Can I send a request to a remote customer?
Use the supported request or link workflow available to your account.
What reference should I keep?
Keep the internal request or invoice ID together with the provider transaction reference.
When should a request be marked paid?
After a trusted transaction record confirms the correct amount and outcome.
How does this apply to multi-branch businesses?
The main objective is to standardise workflows while preserving branch-level visibility. 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 multi-branch businesses · STK Push integration guide for multi-branch businesses · Safaricom Daraja API workflows for multi-branch businesses · Online payment links for multi-branch businesses · Merchant payment collections for multi-branch businesses · Bulk payouts and bulk payments for multi-branch businesses