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, push your config to the production environment:
bunx atmn push -p
Alternatively, the Deploy dialog in the dashboard can copy your sandbox plans to production for you.
Review the diff carefully — production pushes prompt for confirmation before applying changes. Use --yes only in CI where you’ve already validated the config.
3

​
Swap your API key

Replace your sandbox secret key with a live one. Create a production key from Developer Settings, and update your environment variable:
.env
AUTUMN_SECRET_KEY=am_sk_live_...
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.
MethodFail-open response
checkallowed: true
trackSucceeds silently
customers.getEmpty customer object
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:
const autumn = new Autumn({
  secretKey: process.env.AUTUMN_SECRET_KEY,
  serverURL: "https://localhost:9999", // simulate outage
});
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. This is expected — you don’t want to silently skip payment collection.
5

​
Test a real purchase

Make a real purchase using a small-amount plan or Stripe’s test clocks:
  1. Create a customer with a real email
  2. Attach a plan and complete Stripe checkout
  3. Verify the subscription appears in both Autumn and your Stripe dashboard
  4. Check that check and track calls work correctly for this customer
  5. Cancel the subscription and confirm the customer loses access
6

​
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.
7

​
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.