Subscriptions are paid exclusively in native USDC on Solana mainnet. SOL, wrapped USDC, and payments on other networks are not accepted. Raw Shreds checkout supports 1, 2, 3, 6 or 12 calendar months at $99 per month, without a prepayment discount.
Provisioning sequence
- Read the product details, then continue to the customer console.
- Register or sign in with email and password, and verify your email.
- Choose the month count and create an invoice. The server prepares a unique receiving wallet and its USDC token account before displaying the payment address.
- Send the exact quoted USDC amount on Solana. The sender pays the transfer fee; Shredo funds the receiving token-account setup. Never pay an address obtained outside your authenticated invoice.
- The server checks finalized onchain payments automatically. The check-payment button requests a fresh check; keeping the page open is not required.
- After payment, open the Raw Shreds service and save your public IPv4 address and UDP port. The backend automatically checks the address, active access, duplicate destination, change limits and current relay capacity. No operator approval or server verification command is required.
- The console shows the selected destination immediately and marks it applied only after the relay confirms installation. This is not proof that packets reached your server: run a UDP receiver and allow incoming traffic in your firewall. You are responsible for permission to receive traffic at the destination; Shredo does not verify ownership of the address.
Subscription dates
The paid period starts at the onchain time of the finalized payment that completes the invoice, not at service activation. Setup time does not postpone the subscription start. Dates are calculated in UTC calendar months, not 30-day intervals. A January 31 anniversary is clipped in February and restored in March while the subscription remains continuous.
An early renewal extends the existing paid period. A renewal at or after expiry starts a new period from its payment time. The console shows the resulting paid-until timestamp after payment is confirmed.
Renewal reuses the selected destination automatically, subject to service availability. Saving an address or paying again never cancels an operator safety stop or account/service block. If an old pending destination says to resubmit, save it again through the current automatic checks.
Payment exceptions
Partial transfers accumulate against the same invoice. An overpayment is recorded and visible, but does not silently buy extra months. A payment completed after the invoice deadline requires operator review; contact support and do not create a replacement invoice to resolve funds already sent. Receiving addresses are never reassigned to another invoice or customer.
Only use a live invoice in the console. Preview mode never provides a payment address or marks a simulated payment as paid. Production purchasing requires validated receiver capacity and operational readiness.
No card is stored and no automatic card renewal is performed. Payment never overrides technical readiness: an unavailable product is not activated merely because funds were sent.
Credentials
Stream credentials, destination IPs, ports, and tenant secrets are customer-specific. Do not publish them or embed them in client applications. Rotation and revocation behavior will be documented in the production onboarding contract for each product.