This desk keeps billing, delivery, and support tied together until access settles.
Member access
Receipts, access, and delivery in one desk.
Current member console for receipts, access recovery, billing status, and founder delivery routes while the paid product stays intentionally light.
Open with session_id for direct recoveryArchive unlock waits for active billingSupport target: within 2 business daysSource of truth: Support thread
Current route
One desk for receipts, current access routes, and founder delivery questions.
Until heavier member auth is worth building, FLUENTREACT keeps the post-purchase path for the paid React judgment service simple: one billing email, one access desk, one support inbox, and one clear route when something needs attention.
Bring the session id when possible so the receipt trail stays attached to the same recovery path.
One inbox stays responsible for billing, delivery, and access questions.
Load a checkout session first so the billing, webhook, and access trail can be recovered from one source of truth.
Starter pack
These are the live surfaces a new founder buyer should touch first.
The member desk works best when it acts like a calm launchpad into archive reading, billing proof, and delivery context instead of a vague post-purchase dead end.
Preview while checkout settles
Start with the Dispatch archive
Use the archive overview to confirm what unlocks after payment finishes, including the public issue and the founder preview sequence.
Open routeProof surface
Use the sample issue as the style baseline
If you want to calibrate tone and density fast, the public sample is still the cleanest benchmark for what the paid issues are tightening around.
Open routeCheckpoint path
Review the live Index direction
The Index route shows the direction of the wider product so the buyer can verify scope before checkout completes.
Open routeDelivery map
Keep the delivery guide nearby
Use the delivery guide when you want the plain-English map of what the first 30 days include and what still stays intentionally manual.
Open routeSupport fallback
Use one support thread for gaps
If anything feels off after billing turns active, keep support in the same billing trail so fulfillment context does not split across multiple emails.
Open routeSession-aware recovery
Bring your billing state back into view.
Paste the checkout session id from your status link. This desk only shows masked billing details and keeps polling until the billing state settles.
No session is loaded yet. Start from the checkout status link or paste the session id above to recover the exact billing trail.
If the link is gone
Recover the session first, then decide whether the blocker is billing or delivery.
- Open this desk with the same
session_idfrom your checkout status link whenever possible. - If checkout completed but the subscription is not active yet, give the webhook path a few minutes before escalating.
- If the status is past due, canceled, or error, use the same billing email thread so support can keep the receipt trail intact.
Start here
These are the four steps that keep billing and access from drifting apart.
Keep one billing email
Use the same address for Paddle, support, and any founder follow-up so receipt and access confirmation stay tied together.
Save the status link
If you paid through Paddle, keep the checkout status page or reopen this desk with the same session_id until the subscription shows as active and the webhook proof lands.
Use this desk as the hub
The member access desk is the cleanest place to recover the exact billing session, then find the public proof surfaces, delivery route, and support expectations.
Reply in the same thread
If something is missing, reply in the same email trail instead of starting a new one. That keeps billing and fulfillment context intact.
Current access map
Use the live routes below instead of hunting through old emails.
This desk is not trying to replace future member auth. It is the cleanest current map of where the proof, billing status, and paid reading routes already live.
Public archive
Dispatch archive overview
Use this to review the growing Dispatch archive, including the sample issue and the founder preview routes.
Open routePublic proof
Dispatch sample issue
This remains the cleanest proof of tone, density, and the verdict-first reading style buyers are paying for.
Open routeLive pulse
Index bank preview
The Index page now shows the free pulse plus the wider bank shape that founder buyers are helping tighten.
Open routeBilling proof
Checkout status desk
Use this after Paddle checkout to verify the session, transaction, and subscription state instead of trusting a generic success page.
Open routeBuyer guide
Delivery guide
This is the plain-English map of what the first 30 days include, what is manual on purpose, and what is not being sold yet.
Open routeSupport path
Contact and policy pages
Questions about billing, refunds, or access should go through the support inbox with the same purchase email.
Open routeIf you paid through Paddle
- Keep the same billing email you used for checkout.
- Use the checkout status desk until the subscription shows as active.
- Reply from the same email if you need receipt, refund, or access help.
If you joined before full automation
- The delivery promise is still the same founder bundle shown on the public site.
- Questions stay in one support trail so manual fulfillment does not become confusing.
- When the member surface gets heavier later, it should replace this desk cleanly, not contradict it.
Current boundary
No separate member login yet. Paid reading access currently follows the billing session.
That is deliberate. The business is still proving whether Founding Access deserves a heavier authenticated product. Until then, the cleanest route is one receipt trail, one access desk, and one site-first reading path.
- No daily content treadmill, Slack community promise, or heavy member dashboard is part of the current paid promise.
- The value is the quality of the judgment lane: monthly Dispatch, early Index checkpoints, and direct founder replies.
- Until member auth becomes commercially worth building, the receipt email and support inbox remain the canonical access trail.
Support target: within 2 business days through support@fluentreact.com.