FAQ

Revenue Linter FAQ.

Use this page for common trust, stack-fit, preview, and evidence questions. N7X stays available for specific billing-drift questions that are not already answered here.

Search docs

Find the answer before asking N7X.

FAQ

N7X and Free Check

What is N7X?

N7X is Revenue Linter's public, no-secret diagnostic assistant. It can answer from approved RevLint docs, explain billing/access drift concepts, and route complex questions to Ghost Audit Review.

Should I paste API keys or customer exports into N7X?

No. N7X is a public no-secret assistant. Do not paste API keys, webhook secrets, database URLs, customer exports, card data, or private credentials.

What is the free billing/access check?

The free check is the no-secret intake flow. It asks about billing state, app access, failed payments, cancellations, evidence comfort, and desired outcome before recommending the safest next evidence path.

Trust Boundary

Is Revenue Linter read-only?

Yes. Revenue Linter is zero-write by design. It does not issue refunds, cancel subscriptions, delete customers, lock accounts, change Shopify orders, mutate production databases, or deploy patches.

Do I need to connect Stripe immediately?

No. You can start with the no-secret free check, local tools, or manual workflows. Stripe audit-only billing preview is available only when you choose it.

What kind of Stripe key does Revenue Linter accept?

The primary Stripe path is the audit-only connection. Restricted keys are an Advanced fallback in authenticated onboarding. Revenue Linter rejects unrestricted sk_ keys, publishable pk_ keys, webhook secrets, and non-restricted key formats.

Supported Systems

Do you support Stripe, Clerk, Supabase, Prisma, and Next.js?

Stripe is the primary live diagnostic path. Clerk, Supabase, Prisma, Next.js, entitlement tables, user.plan, user.tier, and app-state snapshots are app-context signals used to reason about access drift.

Do you support PayPal?

PayPal is supported as an observation and manual-review path. Revenue Linter can reason about PayPal status-change coverage, CSV reconciliation, refunds, reversals, disputes, and lifecycle ambiguity.

Do you support Paddle, Chargebee, Lemon Squeezy, Braintree, or custom billing?

Those systems are not supported for direct public live sync yet. N7X should answer the buyer problem first: Revenue Linter can still help review whether billing state and app access agree. Technical UDS detail belongs in a For your engineer follow-up.

Preview, Evidence, and Plans

What does the free preview show?

The free preview can show high-level risk category, estimated exposure, severity, affected count, confidence level, masked examples, status-change coverage warnings, and app-state confirmation prompts.

What stays locked behind Core?

Core unlocks deeper evidence review: redacted affected-account references, billing/access mismatch detail, engineer handoff guidance, evidence packet exports, and repeated restricted scans.

Does Revenue Linter automatically fix billing problems?

No. Revenue Linter provides evidence, risk explanations, recommended next steps, exports, and monitoring signals. Your team stays in control of production changes.

When does Ghost Audit Review make sense?

Ghost Audit Review is for unsupported stacks, custom billing logic, agency or client SaaS accounts, meaningful MRR, production ambiguity, migration risk, or questions that require human interpretation after the finding, impact, and recommended next step are clear.