A demonstration
A Bulbea white label demo: one payment, several parties, each one signed its own share.
There is no company here. PaySplit is a name, a mark, a domain and a colour placed in front of Bulbea's payout contract, so a partner can see exactly what their own clients would see. The page opens in PaySplit's own colour. Switch it to Bulbea's amber, on the left, and you are looking at the product this one stands in front of.
- No company behind it
- Same contract, same address
- Named here, never in the app
- Seller94% of the sale $3,008,0006 days ago
- Lead agent3% commission $96,0009 days ago
- Co-agent2% commission $64,0002 days ago
- Conveyancer1% of the sale $32,000yesterday
Try it
One colour in. The entire product follows, and nothing else moves.
The cyan you landed on is this site's own. Bulbea's amber is one swatch along, every other is somebody else, and switching between them is the whole of what a partner does on their first day: the mark, the rules, the links, the tints and the payout above all follow.
Four values, and three of them are worked out for you.
The readable shade and the tint are derived from the colour, not picked by hand, so a partner cannot arrive with a yellow and end up with a page nobody can read.
/* what a partner owns, in full */ --accent: #0891B2; --accent-deep: #07809D; --accent-soft: #EAF6F8; --accent-on: #0E1416;
Green and red do not move. At rest and cannot be undone are not brand decisions, and a partner who recoloured them would be editing what the screen means rather than what it looks like.
There is no second codebase, no copy of the app kept in step by hand, and no screen a partner is six months behind on. That is the only arrangement under which a white label stays current without anyone maintaining it.
The boundary
What the white label replaces, and what nobody replaces.
The line between the two is not a commercial preference. It is what keeps a payer able to check the payment against something other than the brand asking for the money.
PaySplit's
Everything a client sees. Bulbea appears nowhere in the interface, so nobody is asked to trust a brand they have never heard of.
- The mark and the name
- The colour and the three values drawn from it
- The domain every link lives on: app, pay and sign
- The fonts, served from the partner's own domain
- The two guides a client reads
- The assistant endpoint
Not PaySplit's, and not Bulbea's either
The contract and the published formats behind the checks. A payer verifies those against the chain rather than against either of us, which is the only reason the verification means anything.
- The contract address and its ABI
- The domain record format
- The party card and the fingerprint
- The 2% fee and the 1% rebate
One contract, so a payout follows the wallet and not the brand. Every front end talks to the same contract. Connect a wallet on bulbea.org, on PaySplit, or on any other white label, and the same payouts are waiting, because they were never held by whichever brand happened to be on the screen when they were created.
So two parties paid through two different firms are reading one record, and either of them can work from wherever they prefer, including here. That is not a convenience bolted on afterwards, it is what a single contract with no account in the middle actually buys.
Even the guides
The pages a client reads move too, or the whole thing comes undone.
A payer who stops halfway and clicks to understand what they are looking at is the most suspicious reader the product ever gets. If that click lands them on a brand they have never heard of, they have just learned that the firm they were dealing with is a front for somebody else, at the exact moment they were deciding whether to send the money.
Being paid
For a party about to sign its own share: what it is signing, and what signing does not commit it to.
app.paysplit.org/guides/receiving →Paying
For the payer, read in the minute before the money leaves: the five things worth checking first.
app.paysplit.org/guides/paying →What the guides never do is vouch for anything. They explain how a payer checks a payout against the chain and against the published formats, which is work the reader does themselves, against something neither the partner nor Bulbea can alter.
Why its own domain
A white label is proved by an absence.
An absence cannot be shown on bulbea.org. If these screens lived on Bulbea's own domain, every one of them would still be a Bulbea page: a partner would be looking at the thing they are trying to replace, in the address bar, on every screenshot, with no way to tell what their own client would actually see.
So the demonstration was given a name, a mark and an address of its own. It says Bulbea here, in the header of this page, because a demonstration that hid who ran it would be worth nothing. It does not say Bulbea over there, because that is the exact thing being demonstrated.
The demo
Eight screens, each one complete.
Not a tour and not a video. Every screen is the real interface in a real state, including the states nobody screenshots: the payout still waiting on a signature, and the one already paid.
Awaiting signatures
Four parties, two signed. The link refuses money until the last one has signed its own share.
Payable
Every party has signed. The link will now take the payment, and every share is delivered in the same transaction.
One party
A single recipient, where the split signal does not exist and the page has to earn trust some other way.
The signature screen
What a co-agent sees when it signs its own share, and what that signature does not authorise.
The record
After payment: who was paid, when, and the public reference anyone can take to an explorer.
Connect, split
Wallets on the left, the payout itself on the right, so nobody connects anything before seeing what they are connecting to.
Connect, explained
What connecting a wallet does, and the longer list of what it does not do.
Connect, single
One column, centred. A ten second screen treated as a ten second screen.
The payout in these screens is an example, with invented names and amounts. The app behind them is not an example: it reads the same contract as every other front end.
The same thing, with your name on it.
Your mark, your domain, your colour, your assistant. The same contract underneath, the same 2% on top, and the same 1% back to whoever referred the payer. Your clients never have to trust a brand they have never heard of, because they never see one.