Skip to main content
In development. Signup is open. That is a decision about access, not a claim about readiness. See maturity levels.
86d is in Public Beta, which means anyone can register and evaluate it without asking permission or joining a list. It does not mean any Feature, Integration, or Module is ready for real money. Those two things get conflated constantly. Keeping them apart is the point of this page.

​
Three separate things

Public Beta can run for a long time before a marketed launch. One capability reaching Stable makes no other capability Stable.

​
Where each surface stands

See 86d Cloud plans, Set up a payment provider, and How agents work with 86d.

​
What stays blocked, on purpose

Some paths fail closed rather than working badly. A live path is blocked while any required step can:
  • accept a provider event that is unsigned or otherwise unauthenticated
  • trust a money value that came from a Shopper’s browser
  • skip a required tax decision or Shipping quote
  • report success while a required provider is unreachable, or while the outcome is genuinely unknown
  • repeat an Order, Payment, label, notification, or ledger entry after a retry
Preview, sandbox operation, and non-binding Checkout Requests stay available where they are implemented. None of that makes anything Stable. Open signup is not permission to expose a known-unsafe money path. When a defect in that list is found, the capability goes back behind the wall until it is fixed and tested, whatever that costs.

​
Before you enable something

  1. Check its maturity and how it gets admitted.
  2. Check which providers it needs and in which mode.
  3. Read its authentication, webhook, retry, and failure behavior.
  4. Look for its test and production evidence.
  5. Have a way to recover the Store and its data.
Every first-party Module currently publishes as Experimental with no recorded evidence, so step four has one answer today. Versioning and maturity has the exact admission rules.