Software for splitting and billing in cryptocurrency, run by its operator.

What the platform does

It lets a merchant receive cryptocurrency at an address, wait for the network to confirm it, and then distribute it to several recipients according to fixed percentages — or fulfil an invoice and settle the proceeds. It keeps a double-entry ledger of every movement, emits signed webhooks, and offers the same functions through a dashboard and a REST API.

What it deliberately does not do

• It does not hold private keys and cannot move funds on its own.
• It does not convert between assets or bridge between networks.
• It does not promise settlement times; it waits for confirmations or finality and then broadcasts ordinary transactions.
• It does not automatically refund; held funds are released only on an explicit instruction with a destination.

Custody boundary

Addresses are derived and transactions signed by an external, policy-controlled signing provider. The operator connects that provider, defines its signing policies (limits, allow-lists, approvals) and holds the relationship with it. The platform submits transaction intents and records the outcome; it never sees key material.

External dependencies the operator configures

• Signing provider — address generation, transaction signing and broadcast, subject to the provider's policy engine.
• Chain indexers — one per network family, used to observe deposits, count confirmations, detect reorganisations and check address freshness.
• Price source — optional; required only for fiat-denominated invoices.
• Outbound email — for account notifications and this site's contact form.
• Fee wallets and gas budgets — the operator's commission destination per asset, and native-asset budgets that pay network costs for token transfers.

Which of these are configured, and therefore which assets are operational, is visible on the supported assets page.

Environments

Every account has a sandbox on public testnets (and, where an issuer publishes no testnet token, a simulated one). Live mode is enabled per installation by the operator once the dependencies above are in place.

Contact

Questions about this installation, its operator or its terms go through the contact page.