Legal
How Sluzen works
A plain description of the rail, the fees, and what the product does not include.
Effective 3 September 2026
- Is
- Payment railAn HTTP gate in front of an API the issuer already runs. Unpaid calls get HTTP 402 and a price. The agent signs an XRP Ledger Payment to the issuer. Sluzen submits that signed payment, waits for ledger confirmation, then forwards the request upstream. Settlement unit is XRP. The HTTP pattern follows x402, an open standard.
- Is not
- Out of scopeNot a wallet, exchange, or bank. Not a marketplace or a public signup product. Sluzen is not the seller of the issuer’s resource. XRP is a ledger asset, not government-issued money.
Where value goes
- Request price — set by the issuer, paid by the agent, settled on the XRP Ledger to the issuer’s classic address. Sluzen is not the payee.
- Ledger fee — set by the XRP Ledger, paid by the agent. Dust. Not Sluzen revenue.
- Platform fees — on mainnet Split only: 0.8% of settled GMV from call 1. Billed from issuer non-refundable API fee credits. Not a line on the agent’s 402. Testnet does not levy.
API fee credits are a prepaid SaaS consumption allocation. They buy platform capacity only. They are not redeemable and have no use outside this rail. Credits are granted only after a top-up from the issuer’s registered XRPL address; they are not a wallet balance. Issuer keys and credits are provisioned out-of-band.
XRP is a digital asset used as the settlement unit on the XRP Ledger. It is not government-issued legal tender. Sluzen does not convert XRP to national currency.
Keys
The agent’s seed never belongs on sluzen.network. The SDK signs locally. Sluzen does not custody agent keys. The official XRPL Testnet faucet is external.