Embed Widgets: Coming Soon

Why we published the shells#

Four of the eight planned widgets ship as shells in v0.1.x — they render an accessible loading placeholder while their bodies are being built. Their public API (props + events) is locked by the SDK contract test, so dropping in the real body later requires no code changes on your side.

PaymentMethod (planned)#

Saved payment methods table with add/remove flow. Card masking (last 4 + brand icon), primary-card indicator, add-new-card iframe (Stripe Elements / Razorpay Drop-in), delete confirmation dialog.

<AforoPaymentMethod
  tenantSlug="acme"
  embedKey="embk_live_…"
  bridgeToken={token}
  showAll={true}            // (planned) — list all saved methods (default: only primary)
  allowAdd={true}           // (planned)
  allowDelete={true}        // (planned)
/>

When will these ship?#

Each widget ships as a dedicated minor release. The schedule is driven by customer signal — the widget with the most pre-launch demand ships first. The public API stays locked across minors, so a future 0.x release ships a real PaymentMethod body without changing your prop interface.

After the remaining two bodies ship, the SDK promotes to 1.0.0 with a frozen v1 public surface and a 90-day deprecation period for any future breaking changes. See the Versioning guide for the full policy.