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

For weeks, builders asked us the same things in DMs, Discord, and product conversations.

Where is the SDK code? Why is it not open source? How can we trust a recurring billing stack we cannot inspect?

Those are fair questions. If you are wiring USDC subscriptions into a product, trust cannot be a slogan. It has to be something you can read, fork, and test.

We never planned to keep Autlantic Billing closed forever. The SDK, packages, docs, and GitHub layout were already being prepared for a public release.

That moment is now. The Autlantic Payments SDK is public.

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

Docs: https://docs.autlantic.com

Install: npm install @autlantic/payments-recurring

The public SDK repo is the same recurring billing engine that powers Autlantic creator memberships: subscriptions, invoices, webhooks, sandbox flows, and USDC settlement on Base.

Most integrators start with one package. The monorepo also exposes the supporting libraries so you can see how the pieces fit together.

• @autlantic/payments-recurring: merchant client for subscriptions, invoices, refunds, and webhooks
• @autlantic/payments-recurring-core: shared types, intervals, and retry policy
• @autlantic/chain-evm: Base, USDC, and vault helpers
• @autlantic/billing-engine: subscription and invoice engine

Card platforms ask for trust because the rails are familiar. Crypto billing asks for a higher bar, because money moves on-chain and mistakes are hard to reverse.

Open source does not mean you abandon a product. It means the critical path is inspectable. You can review how mandates, renewals, webhook signatures, and settlement addresses are handled before you go live.

That is the trust model we want: verify first, then integrate.

The TypeScript client is designed to feel familiar if you have used other billing SDKs. You create a subscription with a merchant reference, customer wallet, payout address, amount, and interval. Then you activate it to complete the mandate and charge the first open invoice.

In sandbox mode you can walk that path without mainnet funds. When you move to production, the same shapes map to the hosted API and signed webhook events your backend can verify.

Clone the repo, read SECURITY.md, and run the sandbox. AutlanticBilling.sandbox() lets you create subscriptions and activate the first invoice without mainnet funds.

Point a Node app at the hosted billing API when you are ready for real environments. Use signed webhooks with HMAC verification so your product reacts to invoice.paid and subscription lifecycle events reliably.

Full guides live at docs.autlantic.com, including getting started, the Node API, HTTP API, and webhooks.

• Sandbox first for local demos and CI
• Hosted API for production integrations
• Idempotent writes with Idempotency-Key on POST requests
• Webhook helpers to sign, verify, and parse events

Autlantic Billing is built around direct-to-wallet economics. Recurring USDC charges settle to the merchant payout address you configure. Autlantic does not custody subscription revenue as a middleman cut of every sale.

That is the same principle creators already use on Autlantic storefronts: members pay in USDC on Base, and the money goes to the wallet you set. The platform fee is for tools, not a percentage tax on every renewal.

Publishing the SDK is one half of the developer story. The other half is the Autlantic Billing Portal.

The portal is launching soon. Merchants will configure products, prices, customers, invoices, API keys, and webhooks in one place, then wire Autlantic Billing into their own systems.

The goal is simple: configure recurring USDC billing, ship crypto payments in your product, and keep settlement transparent.

If you asked those trust questions earlier, thank you. You helped push this release forward.

Start here:

• GitHub: https://github.com/autlantic/payments-sdk
• Docs: https://docs.autlantic.com
• npm: @autlantic/payments-recurring
• Product: https://autlantic.com

Read the code. Run the sandbox. Open issues when something is unclear. Tell us what breaks.

Trust in crypto infrastructure should not depend on marketing copy. It should depend on source you can inspect.

Autlantic Payments SDK is public. The Billing Portal is coming. Recurring USDC on Base, built to be verified.

• Accept USDC payments without platform custody

  May 12, 2026 · 6 min read

• How USDC on Base checkout works for creator subscriptions

  June 10, 2026 · 7 min read

• Listed $59. Charged $76. The real math behind paid memberships

  June 27, 2026 · 10 min read

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