Payment path

Pricing and Early Access

WeAcuRe should test one hosted checkout before accounts: one cultural study product, then expand after delivery, support, privacy, and refund are ready.

Hosted checkout requiredNo account databaseNo card data stored hereSmall payment test

Review first payment path

First checkout candidate

StarterSource Notes Pack

First checkout candidate: glossary notes, source status, reading paths, and cultural chart vocabulary.

Review the Source Notes Pack Catalog

Preview delivery shape

Review acceptance matrix

Source Notes Pack product card — Source Notes Pack: glossary paths and source-status labels.

Join early access for this product

Palace and star vocabulary notes.
Source status and study path labels.
Email-based delivery or hosted download after provider review.

Next offer candidates

ExportClean Chart PDF

A clean export for the local study chart, selected vocabulary, and use boundaries.

Second checkout candidate

Join early access

AccessExpanded Glossary

More palace, star, stem-branch, and source-aware explanations for cultural study.

Third checkout candidate

Join early access

RoadmapVersioned updates

Later updates should expand the same study pack only after support signals are clear.

Not a launch checkout

Review delivery

Advertising review boundary

Ads should send visitors to learning pages, regional study pages, or Early Access. This page becomes a checkout destination only after price, support, refund, privacy, and delivery are ready. Copy stays within cultural education, calendar labels, glossary notes, and source-aware study tools, with no outcome promises.

Trust before checkout

PaymentHosted provider only

Checkout should open on a reviewed provider page, not inside WeAcuRe.

SupportDomain email first

Refund, access, unsubscribe, deletion, and export requests need a public route.

DataSeparated records

Payment and email records stay separate from local chart input.

Purchase readiness path

PreviewInspect catalog and sample first

Review the catalog, then the sample, before any checkout is connected.

Open catalog

SupportKnow the help route

Contact, refund, delivery, and data request pages must be ready before paid traffic.

Review support

BoundaryRead the use terms

Privacy, refund, and terms keep the product framed as cultural study material.

Review terms

How the first commerce test should work

Step 1Pick one product

Use Source Notes Pack to keep the promise narrow.

Step 2Prepare checkout

Choose one hosted provider, currency, support route, and delivery model.

Step 3Measure payment

Send warm visitors to checkout after policy and support pages are ready.

Checkout setup

Production should use hosted checkout links configured outside GitHub through deployment environment variables. Start with one provider link, product, currency, support route, and delivery model. Review Payment Readiness and Checkout Intent Boundary before sending paid traffic.

A hosted checkout switch turns the payment button path on after provider review.
A provider-hosted product link connects the first source notes product.
Additional product links are reserved for later stages after the first product is stable.

Retention boundary

Email and optional SMS updates require clear consent. Birth data and chart output stay separate from marketing contact data unless a later account feature asks clearly. Review Membership Readiness before enabling login or saved access.

The waitlist stays disabled until support email and hosted form provider are configured. Review Experiment Readiness and Cost Readiness before changing pricing-interest tests.

Review Early Access, Checkout, Payment, Email Consent, Data, Support, Policy Review, Delivery, Cost, Experiment, Membership, Refund, Privacy, Terms, and Contact.