Docs

Flow diagrams

Visual implementation diagrams for checkout, app events, proof writing, tickets, free claims, and QR check-in.

Closed beta@atmosphere-money/app-nodeSDK beta: 0.0.0-beta.3ATM API beta: 2026-0672 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.

ATM checkout

  1. 01

    App checks payability

    Recipient must be payable before purchase buttons are enabled.

  2. 02

    App creates order

    Private app order and fulfillment context stay in the app.

  3. 03

    ATM starts checkout

    App sends strict initiate with an ATM checkout envelope.

  4. 04

    Buyer pays

    ATM hosted checkout owns processor and wallet lifecycle.

  5. 05

    ATM emits event

    App fulfills from payment.completed, not the redirect.

Webhook and XRPC delivery

  1. 01

    ATM creates event

    Event includes id, delivery id, environment, app DID, type, and data.

  2. 02

    HTTP path

    ATM signs the raw body with the app environment secret.

  3. 03

    XRPC path

    ATM calls the app-hosted receiver with service-auth.

  4. 04

    App verifies

    The app verifies auth before parsing or side effects.

  5. 05

    App deduplicates

    Delivery id is stored before fulfillment.

Proof writing

  1. 01

    Payment settles

    ATM records the private payment ledger row.

  2. 02

    Broker proof

    ATM writes the ATM rail/broker proof.

  3. 03

    Payer slot

    App or ATM writes payer record when a grant or delegated path exists.

  4. 04

    Creator slot

    ATM writes creator proof when the creator explicitly syncs from the dashboard.

  5. 05

    Proof outbox

    Missing, waiting, or blocked slots remain observable and retryable.

Ticket hold to issuance

  1. 01

    Read availability

    Derived from private capacity, holds, and issued tickets.

  2. 02

    Create hold

    Tickets locks capacity transactionally.

  3. 03

    ATM checkout

    Paid tickets redirect to hosted ATM checkout.

  4. 04

    Payment confirmed

    ATM notifies Tickets after settlement.

  5. 05

    Tickets issued

    Tickets emits tickets.issued to the originating app.

Free limited ticket

  1. 01

    Buyer clicks get ticket

    No checkout redirect is needed.

  2. 02

    App asserts buyer

    Buyer DID plus short-lived buyer assertion proves user presence.

  3. 03

    Tickets locks capacity

    Same no-oversell transaction as paid holds.

  4. 04

    Ticket issued

    Issued immediately and delivered to the app.

QR check-in

  1. 01

    Pass contains opaque token

    No DID, email, ticket id, or processor id in the QR payload.

  2. 02

    Scanner verifies

    Optional verify call reads current state.

  3. 03

    Scanner checks in

    checkInTicket records the mutating entry action.

  4. 04

    Repeat scan

    Returns existing checked-in state without duplicate entry.

Flow diagrams - Atmosphere Money Docs