Docs

ATM developer docs

Build payments, products, subscriptions, and app callbacks for AT Protocol apps with Atmosphere Money.

Closed beta@atmosphere-money/app-nodeSDK beta: 0.0.0-beta.0ATM API beta: 2026-0642 lexicons

Compatible with the closed-beta ATM app APIs and versioned ATM event headers. Check atm-api-version on every webhook or XRPC receiver event.

Start with payments

Atmosphere Money, or ATM, lets AT Protocol apps add payments while keeping app-specific product, event, social, and fulfillment UX in the app. ATM handles hosted checkout, payment state, app-scoped events, app dashboards, and attested.network proof coordination.

Quickstart

Register an app, configure test mode, start checkout, and fulfill from ATM events.

Open guideHappy path tutorial

The canonical end-to-end flow from app setup to payment.completed.

Open guideBeta developer packet

A concise handoff for invited app developers integrating in test mode.

Open guideServer SDK

Use the beta Node package for app checkout, status, webhooks, and tickets from any trusted backend.

Open guideArchitecture

See how apps, ATM, AT Protocol records, and payment rails fit together.

Open guideAgent integration

Give a coding agent the safe contract for adding ATM checkout, webhooks, and tests.

Open guideCheckout

Understand hosted checkout, private envelopes, and browser return behavior.

Open guideSupper creator buttons

If you just want support on your own site, use Supper instead of becoming an ATM app.

Open external

Add products

Use ATM catalog records when the product identity should be portable across apps. Keep app-specific fulfillment, inventory, downloads, messages, and order workflows in your app.

Catalog and products

Product, price, discount, discount-code, archive, and app fulfillment links.

Open guidePayment lifecycle

How a checkout becomes a settled payment row and app event.

Open guideSubscriptions

Recurring relationships, renewals, amount changes, and app policy.

Open guideSubscription lifecycle

How subscription state maps to payments and app-visible updates.

Open guide

Handle webhooks

Fulfillment should come from verified ATM events, not from browser redirects. HTTP webhooks are the default callback path. XRPC receivers are optional for AT Protocol-native apps that already expose a service surface.

Webhooks and XRPC

Event delivery, signatures, receivers, and idempotency.

Open guideEvent payload examples

Copyable payment, subscription, product, and ticket event envelopes.

Open guideService-auth cookbook

Concrete app service-auth, buyer assertion, and receiver recipes.

Open guideWebhook test console

Generate test webhook and XRPC receiver commands.

Open guide

Use Tickets

ATM docs cover how ticket purchases fit into payments, app auth, app dashboards, and webhooks. Ticket-specific docs live on atmosphere.tickets because tickets add scarce inventory, holds, issuance, QR/pass tokens, scanner flows, and check-in.

Tickets overview

The ATM payment and auth boundary for the Tickets module.

Open guideTickets docs

Open the dedicated Tickets integration docs.

Open external

Go live

Start in the app test environment. Move one flow at a time to live after webhook verification, delivery redrive, refunds, subscription changes, and disabled recipient states are tested.

Testing and environments

Test/live app config, sandbox expectations, and access notes.

Open guideLaunch checklist

Pre-live app, checkout, webhook, and operational readiness.

Open guideApp dashboard guide

Configure modules, webhooks, environments, fee settings, and developer tools.

Open guide

Reference paths

Dashboardhttps://atmosphere.money/dashboard
Broker XRPChttps://checkout.atmosphere.money/xrpc
AppView XRPChttps://appview.atmosphere.money/xrpc
Local apphttp://localhost:3001
API reference

Durable XRPC methods, auth, request, response, errors, retry, and idempotency notes.

Open guideGenerated reference

Generated field-level contract reference from the local lexicon set.

Open guideError codes

Stable error codes, retry behavior, and developer actions.

Open guideSecurity model

Threat model, private data boundaries, and replay controls.

Open guide

How to use these docs

The docs are intentionally detailed, but you should not need to read every page. Use the tutorial pages for the path through ATM, the guides for implementation decisions, and the generated reference only when you need exact field shapes.

First readQuickstart and Happy path tutorial. These should answer the end-to-end integration flow.
When buildingApp onboarding, Checkout, Webhooks and XRPC, App Node SDK, and Testing and environments.
When debuggingError codes, Troubleshooting, Event payload examples, and Webhook test console.
When configuring ATMApp dashboard guide maps every developer control to the matching docs section.
When going liveLaunch checklist plus the app dashboard Moving to live section before changing live environment settings.
When checking fieldsGenerated reference and API reference. Do not start there unless you already know the flow.
App onboarding

Register an app role and configure test mode.

Open guideHappy path tutorial

Register, configure, create checkout, receive payment.completed, and fulfill.

Open guideWebhooks and XRPC

Receive the event that should drive fulfillment.

Open guideTesting and environments

Keep local, test, and live behavior separate.

Open guideLaunch checklist

Go-live checks for apps, checkout, webhooks, and operations.

Open guide
Docs - Atmosphere Money