Skip to main content
Once you’ve tested your integration in sandbox, follow this checklist to go live with real payments.
1

​
Connect your live Stripe account

In the Autumn dashboard, open the Deploy to Production dialog from the sidebar. Connect your live Stripe account via OAuth — this links Autumn to your real Stripe environment.
Your sandbox uses a shared Stripe test account by default. Production requires your own Stripe account.
2

​
Push your plans to production

If you’re using the CLI, add -p to target production. It uses AUTUMN_PROD_SECRET_KEY. push -p only previews the change. Add --yes to apply it:
atmn login writes AUTUMN_PROD_SECRET_KEY next to your sandbox key, so you can use both.Alternatively, the Deploy dialog in the dashboard can copy your sandbox plans to production for you.
3

​
Swap your API key

Point your server-side code at a live secret key. Create a production key from Developer Settings, and set it in your production environment:
.env
Only set the live key in your production environment. Keep your local AUTUMN_SECRET_KEY as the sandbox key. CLI commands with -p read AUTUMN_PROD_SECRET_KEY, so you never need to overwrite it.
Double check that:
  • Your server-side code uses the live secret key (am_sk_live_*)
  • If you’re using a publishable key client-side, it’s the live one (am_pk_live_*)
The key prefix determines the environment automatically — _test_ routes to sandbox, _live_ routes to production. There’s no separate “environment” config to flip.
4

​
Verify fail-open behavior

Autumn’s SDK is fail-open by default — if Autumn is unreachable, check, track, and customer fetches return safe dummy responses instead of throwing errors. This means Autumn can never take your app down.You should verify this before going live. The easiest way is to point the SDK at a non-existent URL and exercise your app’s core flows:
With this in place:
  1. Trigger actions that call check — they should return allowed: true
  2. Trigger actions that call track — they should not crash
  3. Confirm your core user flows work as normal
  4. Remove the serverURL override when done
While the SDK gracefully handles outages for read-path calls, write operations like attach (which initiate checkout or subscription changes) will still fail when Autumn is unreachable.
5

​
Set up webhooks (if applicable)

If you’re listening for Autumn webhook events (e.g. customer.products.updated), make sure your production webhook endpoint is configured in the dashboard. Verify you can receive a test event.
6

​
Monitor your first users

After deploying, keep an eye on the Customers page in the Autumn dashboard. Verify that:
  • New customers are created correctly
  • Subscriptions are attached as expected
  • Usage is being tracked
  • Invoices are generated in Stripe
Once you’ve completed this checklist, you’re live. Your sandbox environment remains available for testing new plans and pricing changes before pushing them to production.