payments

Payments

Installs a small billing facade behind a @callback so the app charges users through one swappable provider implementation. The first available provider is Stripe Subscription checkout: it creates hosted Stripe Checkout sessions over Req, with no extra HTTP client dependency. You call MyApp.Billing.checkout_url/2 from your own checkout route.

When to use

• The app needs paid plans — subscriptions or one-time purchases — and you want a provider-agnostic seam rather than Stripe calls scattered through controllers.
• You want hosted Checkout (Stripe redirects, collects card details) instead of building a payment form yourself.
• Don't reach for this if billing is free, or if you only need a static "contact sales" page with no charge flow.

Dependencies

• Requires: authentication — billing is keyed to a user.
• Recommended: None.

Install

mix saaskit.feature.install payments

The installer asks one decision:

• Which payment provider? (provider) — required. The only current option is stripe_subscription, which installs the Stripe hosted-Checkout subscription implementation behind the facade.

mix saaskit.feature.install payments --decision provider=stripe_subscription

What it generates

• lib/my_app/billing.ex — the billing facade. Defines the create_checkout_session/2 @callback, the public checkout_url/2 entry point, and a private provider/0 that resolves the configured implementation.

Configuration

The facade resolves its provider from application config:

# config/config.exs
config :my_app, :billing,
  provider: MyApp.Billing.StripeSubscription

Secrets come from the environment, not config files:

• STRIPE_SECRET_KEY — your Stripe API secret.
• STRIPE_SUBSCRIPTION_PRICE_ID — the price the subscription Checkout charges.

For production, set both in the deployed environment and switch to your live Stripe keys.

Tweaking for your app

Call the facade from an authenticated checkout action and redirect to the hosted session: