Client payment
Received$1,200USD
60% of invoice received
- Invoice total
- $2,000
- Still to receive
- $800
Manage contractor payments from partial client receipts, with a separate balance and reserve for each project.
Open demoA $2,000 invoice. A $1,200 receipt. See exactly what goes to your team and what stays in reserve.
$1,200USD
60% of invoice received
$700
Full obligation covered
$200
$300 carried forward
Held outside this allocation.
$300
Example values in USD. Payments settle in USDC.
Follow the payment from the client’s receipt to your final review.
$1,200
Applied to a $2,000 invoice
A payment should fit the project, its commitments and the cash you choose to keep.
$300 reserve excluded from the plan
Your client’s payment stays assigned to its project. Other projects’ funds are kept out of the allocation.
Your reserve, daily cap and per-payment limit define what the planner can propose.
Review the exact recipients and amounts. If anything changes, a new approval is required.
Agencies, studios and project teams that pay contractors from client receipts, including clients who pay in stages.
Splitt works with the cash received. It proposes payments for approved work, keeps the reserve aside and carries unpaid obligations into the next plan.
No. Each project has its own accounted balance. A proposed allocation cannot spend funds assigned to a different project.
No. Live execution requires the owner’s signature for the exact recipients and amounts. Changes require a new approval.
The example displays dollar values for clarity. Payments settle in USDC on Arc Testnet; Splitt does not send bank transfers.
Yes. On 15 October 2026 the demo scenario ran on Arc Testnet at 1/1000 scale, with owner-signed batches executed by a Circle wallet through ProjectVault. The transactions are linked at the end of the demo.
Splitt is currently a testnet application. It is not available for mainnet business payments.