Orchestrated, evidenced, recorded — never held.
For the operations lead who routes payments by email today, and the compliance officer who has to evidence it afterwards.
What the record carries
The evidence pack
Bank statements, sale and share-transfer agreements, company accounts, tax filings, inheritance and gift documentation. Where funds originate in digital assets, exchange records, wallet attribution and transaction history.
Different counterparties, different requirements
A bank, a developer, a conveyancer and an exchange house each demand a different subset in a different format. The software maps one file to each.
The payment instruction record
The firm's instruction, who approved it, the documents attached to it, and the date.
Reconciliation
What the file expected against what the firm recorded as received, with the gap flagged before completion rather than at audit.
The line
Wasila is not a party to any payment. The firm's provider relationships are the firm's own.
Six stages. Wasila is not a party to any of them.
| Stage | What happens | Who instructs | What is held | Held by |
|---|---|---|---|---|
| 01 | Enquiry and engagement | The client instructs | The asset as the client already holds it | The firm |
| 02 | Conversion by a regulated provider | The client instructs | AED or USD | Regulated provider |
| 03 | Funds with the firm's counterparty | The client instructs | AED | The firm |
| 04 | Escrow | The client instructs | Escrow | Regulated provider |
| 05 | Registry transfer | The registry instructs | Title deed | Registry |
| 06 | Registered | The client instructs | Registered title | The firm |
Every one of these is somebody else's licence
Wasila holds no financial licence and performs none of the services below. Each is carried out by a third party under its own licence, contracted directly by the firm. The software's part is to pass the request to the provider the firm has chosen and to record what came back: which provider, on what date, against which file.
The firm selects and contracts its own providers. Availability, eligibility and pricing are the provider's to determine, not ours.
Named accounts — opened by an account-issuing institution
A licensed institution opens the account and is the account provider of record. It holds the funds. The software records which account a transfer was made to, and when.
Cross-border transfers — executed by a licensed payment institution
The institution executes the transfer over whichever rails its licence covers. Wasila does not execute, instruct or route a transfer. It records the reference the institution returns, against the file.
Digital-asset conversion — by a VARA-licensed provider
Where a buyer's funds start as digital assets, conversion is carried out by a provider licensed by Dubai's Virtual Assets Regulatory Authority, under that licence and its own acceptance policy. The software records the provider, the date and the evidence returned.
Currency exchange — priced and performed by the provider
The provider sets the rate and performs the exchange. Wasila sets no rate and is not a party to it.
Escrow and registry-accepted instruments — by the escrow agent or issuing bank
The escrow agent or issuing bank operates the account and issues the instrument, under its own licence and the registry's requirements. The software records the instrument reference against the deal.
Screening, identity and blockchain analytics — by the specialist provider
Each check is run by the provider the firm has contracted, against that provider's own lists and data. The software records which check ran, which provider ran it, on what date, and what it returned.
Talk to us about implementing payments orchestration
Record every step against the deal, whichever providers your firm contracts. A member of the team will take you through what implementation looks like.