Terms of Service

1. Operator

“Sluzen” is the service. This agreement is entered into by the Operator and you. Until RUC inscription is published here, identity fields are marked [pending RUC].

• Legal name: [pending RUC]
• Ecuadorian ID: [pending RUC]
• RUC: [pending RUC]
• Contact: [email protected]

The Operator reserves the right to assign, transfer, or delegate this agreement and all rights and obligations hereunder to any affiliated entity, including a future incorporated company (e.g., SAS), without prior consent from the Issuer, by providing notice via the Sluzen platform or email.

2. The service

Sluzen is a payment rail in front of an HTTP API. It issues an HTTP 402 challenge when a protected route is unpaid; accepts a payment the agent has already signed; submits that transaction to the XRP Ledger; and, after the ledger confirms, forwards the request to the issuer’s origin. The issuer sets the request price. The destination of that price is the issuer’s classic XRPL address, not the Operator.

3. What this is not

The service is not a wallet, exchange, broker, bank, electronic-money institution, deposit-taker, marketplace, or custodian of the request price. The Operator is not the merchant of record for the issuer’s resource. XRP is not government-issued legal tender. Nothing here is an offer of securities or a promise to redeem credits for cash.

4. Agents

Agents do not need an account on this site. They call a route, read the 402, sign locally, and ingest the payload. The Operator does not hold agent seeds. Never paste a seed into sluzen.network. The agent pays the request price plus the XRP Ledger network fee. The 0.8% share is not added to the 402 amount. Automated interaction with the API, including an unpaid HTTP 402 challenge, constitutes acceptance of these terms.

5. Issuers

Issuers keep their own origin. They register a route, a price in XRP drops, and a receive address. Without a valid classic receive address there is no sale. Issuer API keys and non-refundable API fee credits (prepaid SaaS consumption credits) are provisioned out-of-band — not via public signup. The issuer is responsible for the legality of the upstream resource and for the address that receives the request price.

6. API fee credits and fees

On mainnet Split the issuer pays, from non-refundable API fee credits, 0.8% of settled request-price GMV from call 1. Testnet does not levy. Insufficient credits → the rail may refuse traffic (HTTP 429). Those credits are a non-refundable platform allocation. They buy platform capacity only. They are not redeemable for XRP or dollars unless the Operator agrees in writing.

Issuers who activate a receive address in the first commercial window keep the 0.8% take for 12 months from activation. After that window the Operator may change the take for new activations.

7. Lawful funds

The Issuer declares and warrants that any virtual assets used to fund non-refundable API fee credits originate from lawful activity. The Issuer indemnifies the Operator against civil or criminal claims arising from the origin of those assets. This declaration does not limit the Operator's right to refuse a counterparty, a top-up, or service.

API fee credits are consume-only. They are non-refundable, non-transferable, not a deposit, and not redeemable. They are accepted only from the XRPL address on the issuer file. The Operator may refuse top-ups from any other address.

8. Prohibited use

Do not use the rail for unlawful content, fraud, sanctions evasion, malware, or to imply the Operator is the seller of the issuer’s resource. The Operator may suspend routes or keys.

9. Availability and liability

The rail is provided as available. Ledger congestion, upstream failure, and hosting limits are outside the Operator’s control. Liability is limited to the platform fees actually paid to the Operator in the 12 months before a claim, except where Ecuadorian law forbids the limit. The Operator is not liable for the issuer’s resource or for XRP price movement.

10. Privacy

Personal data is handled as described in the Privacy Policy.

11. Changes

Material changes will be posted on this page with a new effective date. Continued use after that date is acceptance. The How Sluzen works page describes the product; it does not replace these terms.

12. Governing law

These terms are governed by the laws of the Republic of Ecuador, without prejudice to mandatory consumer rules that apply to you. Courts of Ecuador have jurisdiction, unless a mandatory forum applies.

Contact: [email protected].