Autlantic Billing Portal is live. Configure USDC subscriptions, then ship with the SDK.

When we published the Autlantic Payments SDK, builders could finally inspect the recurring billing engine: subscriptions, invoices, webhooks, and USDC on Base.

The missing piece was a place to run that stack without wiring everything by hand. That piece is live now.

The Autlantic Billing Portal gives merchants a dashboard for products, prices, customers, invoices, API keys, and webhooks. The SDK and hosted API stay the integration path your product uses in production.

Think of the portal as the control plane and the SDK as the code path. You configure catalog and credentials in the portal. Your app calls the hosted API with those credentials and sends customers to hosted checkout.

• Products and prices in USDC (month, year, or one-time)
• Customers, subscriptions, and invoices with PDF receipts
• API keys for Test and Live
• Webhook endpoints with per-endpoint signing secrets
• Team invites for your merchant org
• Overview analytics for revenue and subscription health

The portal has a Test / Live toggle. Each mode is its own data plane: products, coupons, keys, webhooks, customers, and invoices do not mix.

Your integration follows the API key, not a runtime guess.

• abk_test_ keys create Test sessions on Base Sepolia
• abk_live_ keys create Live sessions on Base mainnet
• Hosted checkout shows Test or Live from the session the key created
• Use the same env var names in every deploy. Change the values, not the names

A common path looks like this.

• Open the portal in Test mode and create a product plus price
• Create a test API key and a Test webhook endpoint
• Put AUTLANTIC_BILLING_API_KEY and AUTLANTIC_BILLING_WEBHOOK_SECRET in staging
• Call createSubscription with a priceId, then send the customer to checkoutUrl
• Verify x-autlantic-signature with the endpoint secret before trusting events
• Repeat in Live for production with abk_live_ and the Live endpoint secret

The npm client is unchanged in spirit: AutlanticBilling.fromEnv() for hosted API, or AutlanticBilling.sandbox() for in-process demos.

Install: npm install @autlantic/payments-recurring

Docs: https://docs.autlantic.com

GitHub: https://github.com/autlantic/payments-sdk

We updated the public guides so Test and Live keys, Sepolia vs mainnet, and per-endpoint webhook secrets match how the portal and API actually behave.

Autlantic Billing settles recurring USDC to the merchant payout wallet you configure. Autlantic does not custody member subscription revenue as a cut of every sale.

That is the same principle creators already use on Autlantic storefronts, now available as a merchant billing stack you can configure in a portal and call from your own product.

If you already cloned the SDK, keep building. If you need a dashboard, open the portal and create your Test catalog first.

• Billing Portal: https://portal.autlantic.com
• Docs: https://docs.autlantic.com
• SDK on GitHub: https://github.com/autlantic/payments-sdk
• npm: @autlantic/payments-recurring
• Earlier announcement: /blog/open-source-payments-sdk

Open source answered the trust question for code. The portal answers the day-to-day question for operations.

Configure in Test. Ship with a test key. Graduate to Live when you are ready. Recurring USDC on Base, inspectable SDK, merchant dashboard included.

• What kinds of projects can integrate the Autlantic Billing SDK?

  July 28, 2026 · 8 min read

• Why Autlantic Billing instead of Stripe (and other card platforms)

  July 28, 2026 · 9 min read

• We open-sourced the Autlantic Payments SDK. Trust should be inspectable.

  July 23, 2026 · 9 min read

• Accept USDC payments without platform custody

  May 12, 2026 · 6 min read

Browse the Autlantic blog, explore creator guides, or launch your store.