> ## Documentation Index
> Fetch the complete documentation index at: https://docs.shredo.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Access and crypto payment

> How to buy Shredo access in the console: native USDC on Solana, calendar-month subscriptions, invoice payment checks, renewals and payment exceptions.

Subscriptions are paid exclusively in native USDC on Solana mainnet. SOL, wrapped USDC, and payments on other networks are not accepted. Each available product supports 1, 2, 3, 6 or 12 calendar months without a prepayment discount: Raw Shreds and Pool Catalogue cost $99 per month each; Decoded Transactions costs $399 per month.

## Provisioning sequence

1. Read the product details, then continue to the customer console.
2. Register or sign in with email and password, and verify your email.
3. 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.
4. 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.
5. After sending funds, press **Check payment** on the invoice. The server verifies finalized onchain payments only when a check is requested; opening or refreshing the invoice does not scan the blockchain. If the transfer is still pending, check again after it finalizes. A payment completed before the invoice deadline can still be checked afterward; the subscription starts from its onchain payment time, not the button press.
6. After payment, open the purchased service. For Raw Shreds, save your public IPv4 address and UDP port; automatic policy and capacity checks precede relay setup. For Decoded Transactions, create a stream API key and connect your gRPC client. For Pool Catalogue, browse the inventory, verify a signed snapshot or create a catalogue-specific API key. No receiving IPv4 or UDP port is needed for the latter two products.
7. For Raw Shreds, the console marks the destination 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. For Pool Catalogue, subscription access and publisher freshness are separate: inspect the generation and publisher timestamp before using data.

## 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 and catalogue credentials, destination IPs, ports, and tenant secrets are customer-specific. Do not publish them or embed them in browser applications. Keys are product-specific; a catalogue key does not authorize a decoded stream. See each product's reference for creation, rotation, revocation and bounded authorization-lease behavior.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.