Names, prices, billing periods, and bullet lists below are loaded from your catalog—adjust them in admin when offerings change. Upgrades typically run through Stripe checkout when billing is enabled.
Resume generations: 3 / month (from plan)
Resume generations: 4 / month (from plan)
Paid upgrades use secure checkout when Stripe is configured.
Resume generations: 25 / month (from plan)
Paid upgrades use secure checkout when Stripe is configured.
If your catalog includes annual Stripe prices, they appear at checkout—this page always reflects the monthly figures stored in the database unless you add separate annual cards in admin.
Practical answers for how billing usually works with JD Match—confirm details in admin or Stripe for your deployment.
Plan changes are handled through your account billing flow (Stripe customer portal or checkout, when enabled). Effective dates and proration follow Stripe’s rules for the price you selected.
Trials depend on how each paid price is configured in Stripe and on your pricing_plans rows.
The Free tier is available without a card; paid tiers start checkout when you choose to upgrade.
Stripe Checkout typically supports major cards and wallets your Dashboard allows. Invoicing or purchase orders are not implied here—enable what you need in Stripe if you sell to teams.
Traffic should be served over HTTPS in production. Card data is collected by Stripe; JD Match stores customer and subscription references your app is built to persist.
Refunds and guarantees are a business policy you control in Stripe and in how you support customers—not something this page can promise globally. Publish your real policy on Contact or legal pages when you finalize it.
Create an account to use the Free limits, then return here or to in-app billing when you need more generations.