Use cases
Built for agreements where delivery and payment depend on each other.
Dhira Pay is not built around one industry or around its maker's own business. The model is general: parties, obligations, conditions, evidence, acceptance and controlled release. These four examples are all running in the sandbox.
Services and projects
A manufacturer commissions a software build
The client does not want to pay in full before anything exists. The provider does not want to build for three months on an invoice that may be queried.
How the transaction is structured
- Four milestones, each with its own acceptance criteria and required evidence
- The full amount is funded and safeguarded before work starts
- The client reviews each submission within five days
- A finance approver releases each accepted milestone
The provider knows the money is there. The client pays only for work it has accepted.
Supply of goods
A fabricator calls off steel in three deliveries
The supplier wants certainty of payment before it reserves stock. The buyer wants to pay for what actually arrives, with certificates.
How the transaction is structured
- One milestone per delivery, due on the agreed schedule
- Signed delivery note and mill certificates as required evidence
- Acceptance against tonnage and certificate coverage
- Release per delivery, not for the order as a whole
Each delivery stands on its own record. A short delivery affects one release, not the relationship.
Construction and installation
A plant owner installs rooftop solar
Large staged payments, technical acceptance, and a real chance of disagreement about whether what was delivered matches what was specified.
How the transaction is structured
- Funding per milestone, so the owner does not fund commissioning before design is approved
- A quantity surveyor both sides trust is named as adjudicator in the agreement
- A dispute holds only the disputed milestone and its funds
- The adjudicator records a decision with reasons. The decision directs the money
A disagreement about inverters does not become a disagreement about everything.
Multi-party delivery
One payer, a rigging contractor and a haulier
Moving a press line takes three businesses. The payer wants one record. Each contractor wants to be paid for its own part when its own part is done.
How the transaction is structured
- Three parties to one transaction
- Each milestone names its own payee
- Each payee can act only on its own milestones
- Every party sees the same record and the same financial position
No party waits on another party's paperwork to be paid for work that was accepted.
Dhira Pay is for transactions between businesses and other legitimate commercial counterparties. It is not a consumer payment product and it is not a marketplace.