A seeded demo workspace.
Everything below is produced by the same services your own traffic would go through — the same state machines, the same audit trail, the same refusals. Nothing is written straight into a table to make a screen look populated.
What gets seeded
A demo workspace
Marked as a demo, with a permanent routing token so pooled provider events can find their way back here.
Platform pool connections
Credential-free references to Pehmen’s own provider accounts. They store no keys, by construction.
Pehmen's own sandbox accounts
Checked against the real providers, through the same validator your pasted credential goes through.
Three sellers, reviewed by an operator
Each with a MANUAL_REVIEW attestation that states its provenance — including one that came back inconclusive — and a verified notification channel.
Twelve orders and payment intents
Real orders through the real state machine, left unrouted so you can route one yourself.
Verified commerce envelopes
One per order, signed by the platform key and independently verifiable against the public keys endpoint.
Seller destinations
Tokenized: the account number is never stored, only a tenant-scoped fingerprint of it.
Payouts, including one that will not move
Two approved by a single reviewer; one above the dual-control threshold left HELD with an open request for a second approver. That refusal is the demo.
A sample savings report
Priced over the seeded traffic, with every assumption listed so the figure can be taken apart.
The demo lives in a workspace of your own, so it needs an account. Seeded data cannot be removed from a workspace afterwards, which is why the demo only ever goes into an empty one.