Blockchain Lab Ops
PayoutOps
PayoutOps is the operating layer around a business payment: who may approve it, which rail is even a candidate, and how finance reconciles it the next morning. The rail itself stays with a provider the buyer and its counsel select.
Not sold as stablecoin development.
Synthetic invoices and a simulated rail. No real funds.
Who it is for
Marketplaces, agencies, exporters, and contractor platforms that already pay people.
The workflow, before and in the demo
Before
- A supplier invoice arrives and sits in a mailbox.
- Approval happens in a chat, with no limit and no second person.
- The payment status is a guess until someone asks the bank.
- Reconciliation takes days, and exceptions become another thread.
In the demo
- A payment request with a named supplier.
- A policy check and a second approval above a limit.
- A selected rail, shown as a simulation. No funds move.
- A reconciliation line, an exception queue, and an audit history.
Modules
- Organisation profile
- Supplier directory
- Invoice or payment request
- Approval workflow and spend limit
- Counterparty allow-list
- Rail selection, including a down rail
- Reconciliation ledger and exception queue
- Remittance note and audit history
What would integrate later
- A licensed payment firm, a bank file, or an accounting export would sit beside the workflow.
- Named providers are chosen later by the buyer and their counsel. None is connected here.
- A stablecoin corridor can be one candidate rail. It is not the product, and it is not a promise of speed.
Controls, and the limit on them
- Dual approval above a limit, a hard cap, a down rail, and a mismatch are shown in the settlement demo.
- Those controls are a synthetic script. They are not a security clearance.
- Blockchain Lab does not send real funds from this service line.
Commercial shape
If a pilot is later agreed, the shape is a workflow fee plus support. No price on this page is a quotation.
Fit scan
Exploring whether the workflow is real
A rail map, the control gaps, and a decision on whether a chain is even relevant.
Illustrative range if a team is later free: 1–2 weeks. Not a delivery promise.
Working demo
Needs something colleagues can click
The settlement desk: synthetic requests, approvals, a down rail, and reconciliation.
The synthetic demo is already on this site. A private walkthrough is not scheduled here. Not a delivery promise.
Pilot scope
Ready to discuss a limited pilot, with counsel
A written scope for a multi-user console. No repository is issued from this page.
Illustrative range only after counsel and a provider are chosen: 6–12 weeks. Not a delivery promise.
Integration design
A provider or system of record is already chosen
Where a provider export and an accounting file would land. Not a live connection.
Illustrative range for a later pilot: 3–6 months. Not a delivery promise.
Managed design
A pilot exists and someone must keep it current
Exception playbooks and corridor reviews after a pilot exists. Not a retainer you can buy here.
Monthly, only after a pilot exists. Not a delivery promise.
A pattern, not a customer
Pattern, not a client: a marketplace pays contractors in more than one country, approval lives in chat, and reconciliation takes days. No company is named because none is claimed.
Questions worth answering first
- Who approves a payment today, and where is that written down?
- Which corridor is actually painful, and which is only unfamiliar?
- What should a second person have to approve?
- What does finance need to see the next morning?
Adjacent lines
What this line will not do
- Not regulated custody. Blockchain Lab does not hold client assets.
- Not payment execution. A rail, when one is used, is operated by a provider the buyer and its counsel select.
- Not legal advice.
- Not financial promotion and not an offer.
- Not an AML or KYC certificate. A demo case file is not a compliance opinion.
- Not a statement of returns. Return: Not shown.
- Not a production security clearance. No audit is claimed.
- Not a new chain by default.
- Demos use synthetic data. No real funds, wallets, private keys, or customer records.
- Business documents do not go on a public chain.
Illustrative commercial design. Not legal advice, not an offer, and not a delivery promise.