Legal

How Sluzen works

A plain description of the rail, the fees, and what the product does not include.

Effective 3 September 2026

Is Is not Trust Scope Money Terms Privacy

Is: Payment railAn HTTP gate in front of an API the issuer already runs. Unpaid calls get HTTP 402 and a price. Default: the agent signs an XRP Ledger Payment to the issuer. On a default proxy route, Sluzen submits that signed payment, waits for ledger confirmation, then forwards the request upstream. An issuer who already returns 402 can register that https resource and settle through Sluzen after their handler succeeds. A proxy route can instead call the origin first and submit only when the origin responds OK. Default product Amount is XRP drops; opt-in Amounts include allowlisted RLUSD on XRPL and canonical USDC on Base (compatible with HTTP 402 settlement verification on Base for canonical USDC). 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.

Who the caller trusts

On the default proxy, ledger confirmation is what unlocks the forward path. On a facilitator resource, the issuer's settle call is what submits payment after the handler. Those are different trust boundaries.

Three sale modes. The names match the console.

Default proxy

Sluzen sits in front of your API

Caller hits: A public path on Sluzen.
When the ledger settles: On the paid retry, Sluzen submits the signed payment and waits for tesSUCCESS.
When the payload is released: After tesSUCCESS, Sluzen forwards the request to the origin and returns that response.
If unpaid: An unpaid call gets HTTP 402 from Sluzen. The origin is not called.
Who the agent trusts: The agent pays on-chain to the issuer address (the one that starts with r). Sluzen submits the signed transaction and does not hold the seed. Ledger confirmation unlocks the forward path. On this path the buyer does not depend on the issuer choosing to settle.

Facilitator

Callers stay on your https URL

Caller hits: The issuer's own https URL.
When the ledger settles: The issuer server calls facilitator/settle. Sluzen submits the signed payment only on that call, and only tesSUCCESS completes it.
When the payload is released: The issuer returns the body only after settle succeeds. Sluzen does not see the resource body.
If unpaid: If the issuer never settles, the caller is not charged.
Who the agent trusts: The agent depends on the issuer to settle after a successful handler, and on Sluzen being available for that settle, unless the agent verifies the payment on-chain with @sluzen/sdk verifyBuyerPayment (or an explorer). After tesSUCCESS there is no refund.

Settle-after-origin

Charge only if your API responds OK

Caller hits: A public path on Sluzen, with the proxy checkbox on.
When the ledger settles: Sluzen calls the origin first, then submits the signed payment only if the origin responds 2xx.
When the payload is released: A 2xx body is returned only after the ledger confirms.
If unpaid: A response outside 2xx is not charged. If the origin already changed state and the submit then fails, that work stays unpaid.
Who the agent trusts: The agent still pays the issuer address, and Sluzen still submits the signed payment without holding the seed. The origin can run before the ledger confirms, so unpaid work is possible if submit fails after a change. The 2xx body still waits for ledger confirmation.

Facilitator and settle-after-origin in the terms →

What this rail settles

Supported settlement, and what sits outside this rail.
Topic	Detail
Supported	XRPL mainnet (`xrpl:1`) or testnet (`xrpl:0`) as CAIP-2 on /live. Native XRP drops (`scheme: exact`) and opt-in Payment Channels XRP (`scheme: paychan`) are published on `GET /facilitator/supported`. Allowlisted RLUSD IOU (§2.4) and canonical Base USDC on `eip155:8453` / `eip155:84532` (§2.5) are per-route product Amounts (not listed on `/facilitator/supported`). x402-style headers.
Not supported	Solana USDC, nano, Stellar, Stacks, arbitrary ERC-20s, IOUs outside the closed RLUSD allowlist, Operator gas wallet / EIP-3009 / Permit2, and a multi-rail drop-in. Sluzen is not the payee of the request price.
Notes	Default product Amount is XRP drops. Prepaid platform take (0.8% on mainnet) stays in XRP drops for every product currency. Sluzen does not convert assets for the caller and does not manage DEX auto-bridges. Discovery is an opt-in announcement on proxy routes only, and a route appears on the public list only after a settled payment or a fresh HTTP 402 probe.

Where value goes

Request price: set by the issuer, paid by the agent. Default XRP and allowlisted RLUSD settle on the XRP Ledger to the issuer’s classic address. Canonical Base USDC settles to the issuer’s EIP-55 0x… address. Sluzen is not the payee.
Network fee: on XRPL routes, set by the XRP Ledger and paid by the agent (dust). On Base USDC routes, the agent pays ETH gas. 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 in XRP drops for every product currency. Not a line on the agent’s 402. Testnet does not levy.
Introductory Fee Waiver: new production accounts may receive a one-time promotional waiver of the 0.8% platform fee up to a cumulative 1 XRP equivalent (1,000,000 drops of fee) or for 30 calendar days from window start, whichever occurs first. Non-transferable. Non-redeemable. Not a credit line or cash balance. After the allowance or the period ends, routing requires a positive prepaid fee balance.

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.

Default product Amount and prepaid credits are XRP drops on the XRP Ledger. XRP is not government-issued legal tender. Sluzen does not convert XRP to national currency.

Product settlement destinations are the issuer's classic XRPL address (r…) or, for canonical Base USDC routes, an EIP-55 address (0x…). Compatible with HTTP 402 settlement verification on Base (eip155:8453) for canonical USDC. Prepaid platform take remains XRP drops only. Sluzen does not operate a gas wallet, escrow, or bridge.

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.

Terms →