Issuer-in-a-Box · Live
This is not a brochure and not a mock. Every button below runs the real Issuer-in-a-Box engine: it puts each request through a hardwired compliance gate and — only on an explicit ALLOW — builds the exact unsigned XRPL blueprints (TrustSet, Payment, Clawback) you would sign and submit on-ledger. It never holds keys and never moves funds: it emits the instructions, you sign and broadcast. The gate is hardwired — a denied request produces no mint at all, with no blueprint.
A realistic tokenized-asset issuance: a USD-pegged token delivered to a new institutional holder. Run it two ways — a KYC-verified holder that the gate clears (real TrustSet + Payment blueprints), and a sanctioned account the gate denies (no blueprint). The engine decides; we never fabricate the outcome.
Raw engine JSON (receipt + unsigned blueprints)
A secondary-market transfer of the issued asset. It is
gated identically to a mint — the issuer's compliance policy applies to the
recipient on every transfer, not just issuance. A KYC-verified
recipient clears (unsigned Payment blueprint); a non-compliant
one is denied.
Raw engine JSON (receipt + unsigned blueprint)
Clawback is issuer-only and powerful, so it
never auto-allows. It does not consult the compliance gate; instead
it requires proof that the issuer authorized this specific action (an
attestation). Without it, the engine raises a real
AuthError (HTTP 403) and builds no blueprint. With
a valid attestation, it returns an unsigned Clawback
blueprint.
Raw engine JSON (clawback record / fail-closed AuthError)
Runs the real Issuer-in-a-Box engine. It emits unsigned blueprints — it never holds keys or moves funds; you sign and submit. The compliance gate is hardwired: deny means no mint, with no blueprint. Want the production control plane wired to your own compliance backend and signer? See pricing → Talk to us →