Billing & payments

Your members pay you.
Not us.

The model connects your own Stripe account, keeping your school as merchant of record. Staff-assisted recurring checkout is available to approved pilot schools only after the platform release gate, school-specific readiness review, Stripe charges and payouts verification, and deliberate staff checkout all pass. Proposed core software pricing is $49–$199 per month based on active-student count, with lower annual targets; final terms will be confirmed before any paid launch.
Your Stripe account
Added processing markup
Controlled pilot activation

No card is required to create a workspace. Member billing activates only with the school owner's approval, the Dojo Wizard release and readiness gates, and completed Stripe verification.

A parent paying karate tuition at the dojo front desk after class

Billing readiness

The core payment path works—with safeguards around activation.

Collection stays limited to verified schools and deliberate staff checkout. The status below does not remove the platform, school-readiness, or Stripe gates.

Passed

core sandbox checkout

Direct

connected-account charges

Tested

decline and retry

Live

verified-school collection

Direct Stripe ownership

Your payouts and customer relationships stay yours

The integration connects the Stripe account your gym owns so payouts and customer relationships stay with your business. Collection requires platform and school-specific readiness gates, a verified connected account, and an owner-approved staff checkout.

  • Your school remains merchant of record— member charges are direct charges on the school's connected Stripe account.
  • No processing-percentage markup from Dojo Wizard— Stripe's own fees still apply directly to your account.
  • Payment data stays with Stripe — Dojo Wizard never asks staff to copy full card numbers into notes, email, or spreadsheets.

What a markup actually costs

Say your school collects $20,000/mo in dues. Every 1% of processing markup is $200/mo — more than Dojo Wizard’s proposed maximum core plan. Some platforms’ published rates have added several points on top of base processing (pricing as of 2026; plans change).

The Dojo Wizard model adds no processing percentage. Verified schools in the approved pilot can use staff-assisted collection after every release gate passes; platform subscription metering remains off until the final terms and owner activation flow are published.

Stripe's rates change and vary by payment method. Confirm the current US pricing at stripe.com/pricing.

See how we compare →

Everything billing touches

Core membership billing is live; the long tail stays labeled

Checkout, declined-card retry, webhook updates, rollover rules, freeze/resume, and end-of-period cancellation are implemented. In-app refunds, disputes, and payout reconciliation remain planned; owners can manage those directly in Stripe meanwhile.

Controlled membership plans

Draft pricing privately, publish it deliberately, and synchronize approved recurring plans to the school’s connected Stripe account.

Household records

Group related people for front-desk context. Shared payer rules, discounts, and family invoices remain planned.

Lifecycle controls

Freeze, resume, and end-of-period cancellation synchronize with Stripe. Refund and dispute self-service inside Dojo Wizard remains planned.

Webhook safety work

Connected-account subscription events, retries, idempotent processing, and local subscription updates are active behind a production kill switch.

Pro shop ledger

Record products, stock, and sales in the operations workspace. Card-present payment collection is not implemented.

Recorded business signals

Operational reports summarize members, leads, quiet-member flags, and recorded pro-shop sales. Accounting-grade payment reconciliation remains planned.

Sandbox evidence

What the core validation covered

Connected a test school

Completed Standard Connect onboarding and verified submitted details, card-charge capability, payouts, and return behavior.

Synchronized plans safely

Created products, prices, customers, and subscriptions, then retried a declined payment without creating a second current membership.

Exercised the core lifecycle

Verified successful and failed invoices, active rollover allowances, and freeze/resume synchronization. The extended lifecycle remains on the release checklist.

A reviewed migration can carry supported billing history into a read-only, source-labeled member view. It does not create Stripe transactions or affect live reporting; current subscriptions, open balances, and payment methods follow a separate cutover plan. Compare platforms.

Start on your terms

Launch billing with a supervised first payment.

Create your school, connect your school-owned Stripe account, and complete the readiness checklist before the first member is charged.