Recipient Terms

1. Who these terms apply to

These Recipient Terms apply when you use ATM to receive payments as a creator, organizer, seller, project, app, or other payment recipient. They supplement the ATM Terms of Service, Privacy Policy, the Ticket Terms if you sell tickets, and any payment processor terms that apply to your payment account.

If you receive payments for a business, event, organization, project, or app, you confirm that you are authorized to use ATM and receive payments for that entity.

These Recipient Terms are ATM's platform provider agreement for recipient-facing services, including payout setup, connected-account management, application-fee collection, app revenue-share administration, checkout enablement, dashboards, support, refunds, disputes, records, webhooks, and app integrations.

2. Payment account onboarding

To receive payments, you may need to complete payment-account onboarding through Stripe Connect or another processor. If Stripe is used, your Stripe connected account is also governed by the Stripe Connected Account Agreement, the Stripe Services Agreement, and any other Stripe terms that apply to your account, country, payment methods, or services.

The processor may request legal name, business details, tax information, beneficial owner information, bank account details, identity documents, and other information required for compliance, risk, payouts, tax, or payment-method eligibility.

You agree to provide accurate and current information and to keep your payment account in good standing. ATM may block or pause payment acceptance, payouts, ticket sales, subscriptions, products, or application-fee processing if requirements are incomplete, overdue, rejected, or unavailable.

You authorize ATM to create or help configure a connected account; access and use connected-account data for ATM services; share required information and instructions with Stripe; show embedded processor components; retrieve processor account, capability, balance, payment, refund, dispute, subscription, and payout status; submit settings; collect disclosed application fees; and instruct the processor to perform activity reasonably needed to provide checkout, reconciliation, refunds, disputes, subscriptions, support, and compliance. ATM will not perform activity outside the authority you grant or after that authority is withdrawn, except as needed to wind down prior transactions or meet legal obligations.

By accepting these Recipient Terms and using a Stripe connected account, you also agree to be bound by the applicable Stripe Connected Account Agreement and Stripe Services Agreement. You authorize ATM to share accurate business, identity, account, and transaction information with Stripe as needed to provide and administer the connected account and payment services. Stripe processes that information under its Privacy Policy. You must also complete any acceptance or verification step Stripe requires before using processor services.

If a processor dashboard is unavailable for your connected account type, contact ATM for payment-account support. ATM may retain evidence of your acceptance of these Recipient Terms and related processor onboarding.

3. Merchant and seller responsibilities

For direct charges, you are the merchant of record and recipient/seller for the payment. You must be clearly identified to the customer in the offer, checkout context, receipt, statement descriptor, and support information. You are responsible for the goods, services, events, tickets, subscriptions, fulfillment, customer support, refunds, cancellations, taxes, compliance, and legal obligations related to what you sell or receive money for.

ATM provides payment infrastructure and proof systems. ATM does not become the merchant of record for your products, services, events, tickets, subscriptions, or donations unless ATM expressly states otherwise in a separate written agreement or product notice.

4. Apps and app-originated payments

Your payments may originate inside third-party or ATM-owned apps, including Supper and other AT Protocol apps. If an app originates a payment to you, ATM may share app-scoped payment and order information with that app so the app can provide checkout, fulfillment, customer support, fraud/risk handling, refunds, reporting, webhooks, and proof status.

ATM does not give originating apps unrestricted access to your payment processor account. Apps should not receive your KYC data, bank account details, payout balances, Stripe connected-account ID, or payments you received through other apps merely because they originated one payment flow.

You are responsible for choosing apps you trust to originate payments, products, tickets, subscriptions, or fulfillment flows for you. ATM may disable app-originated checkout if the app, product, event, or payment flow creates legal, processor, fraud, security, privacy, or operational risk.

5. ATM application fees and other fees

ATM charges an application fee on payments you receive. The application fee is ATM's own fee for the ATM platform services used on that payment, and ATM is the party that collects it. Its rate depends on the app that originated the payment: the app posts a rate for its role, you accept that rate for that app, and ATM charges you the accepted rate. ATM pays an independent originating app the contractual revenue share described in its App Terms out of ATM's collected fee. For an ATM-owned app, ATM retains the fee internally because there is no separate revenue-share payee. What an app posts is the rate ATM will charge you; it is not a separate charge by that app to you, and you owe the app nothing under it. Where ATM has enabled corridor-aware fee suppression, ATM charges the application fee for an app's role only where ATM can pay that app its revenue share; where no supported transfer route exists for the app's account, ATM charges you nothing for that app's role.

Where ATM supports the processing-and-settlement charge, ATM may charge you only pool-level costs of settling or converting the application fee received by ATM: multi-currency settlement and inbound application-fee conversion. These components use the processor's published rate in force for the payment and the supported settlement-currency path, are allocated once among the applicable root fee pools, and never exceed the cap you expressly accepted with each app's rate, which ATM limits to 1.5% of that root fee pool. The charge is collected inside the application fee, is never a margin, and is reconciled against the processor's recorded cost: ATM returns identified over-collection to you and bears under-collection. Cross-border transfer fees and currency-conversion costs on transfers paying apps are those apps' own costs, never yours. A component the processor has already charged remains subject to its accepted refund policy.

Where ATM records an app's posted rate and your acceptance as AT Protocol records, the accepted rate, the app, its role, the payment types it covers, and the settlement-cost cap are published as a record in your own repository, and the app's posted rate is published in the app's repository. ATM executes these records as instructions about the application fee ATM charges you and the revenue share ATM owes the app; they do not create a payment obligation between you and the app. Where ATM supports delegated allocations and one app allocates part of its revenue share to another app for a referral or checkout role, ATM retains a published network tariff from that amount, ATM pays the other app directly, and your accepted rate is unchanged.

Some optional modules also carry a separately disclosed ATM platform fee—for example, paid ATM Tickets may include a per-ticket platform fee that is passed to the buyer or deducted from organizer proceeds according to the configured ticket flow. Payment processor fees, refund costs, dispute costs, payout fees, taxes, and other charges may also apply, and are separate from the application fee.

For direct charges, Stripe collects its processing fees directly from your connected account under your Stripe agreements and manages chargeback and negative-balance recovery on that account. ATM does not set or receive those processing fees. ATM collects the configured application fee and any separately disclosed ATM module fee that applies to the transaction.

You are responsible for reviewing the fee information displayed in ATM, an originating app, or processor surfaces before accepting payments. Fees may vary by payment method, country, currency, app, product, subscription, ticket, processor capability, and account configuration.

ATM may instruct the processor to deduct ATM application fees, refund amounts, dispute amounts, chargeback fees, or other applicable charges from your connected account balance where supported by the processor and permitted by law.

6. Refunds, disputes, and chargebacks

Refunds, disputes, chargebacks, reversals, failed payments, and processor adjustments may reduce your balance or delay payouts. If a refund or dispute affects a payment, ATM may update payment status, app webhooks, tickets, entitlements, subscriptions, and public or private proof records.

ATM, an originating app, or a processor may help process refunds or cancellations, but you remain responsible for your refund policies and customer obligations unless a specific product flow says otherwise. Some app modules, such as tickets, may require ATM-native refund flows so inventory, tickets, proof records, and webhooks stay aligned.

If you refund a payment from your own processor dashboard rather than through ATM, the processor does not return ATM's application fee automatically. Where ATM supports automatic application-fee recovery for a refund initiated from your processor dashboard, ATM may return the refundable fee-pool portion after observing the exact refund and reconcile the corresponding revenue share; any separately disclosed non-refundable settlement-cost component the processor has already charged remains subject to its accepted policy.

7. Taxes and reporting

You are responsible for determining, registering for, collecting, reporting, and remitting any taxes, duties, fees, or governmental charges related to your sales, payments, tickets, subscriptions, products, or services, except where applicable law assigns an obligation to ATM or another party. Contractual seller responsibility does not override marketplace-facilitator, deemed-seller, or other mandatory tax law.

ATM does not automatically calculate tax for every seller at launch. If ATM or Stripe offers a tax tool, you must provide accurate headquarters, registration, product-tax-code, and other tax settings and use the tool only where you are registered and legally entitled or required to collect. A zero-tax result may mean you are not configured to collect, not that no tax obligation exists. Tax tools, threshold monitoring, documents, and reports are not tax advice and do not replace filing or remittance.

ATM may restrict a product, seller, or jurisdiction; require additional tax information; collect or withhold tax; or use a different charge structure where ATM determines that law or processor rules require it.

8. Products, subscriptions, and tickets

You are responsible for ensuring that products, services, subscriptions, events, tickets, descriptions, prices, availability, inventory, and fulfillment promises are accurate and lawful. You must not sell items or services you cannot legally or practically provide.

For recurring payments, you must clearly disclose the amount, cadence, renewal terms, cancellation method, material benefits, and any trial or promotional terms before authorization. You must honor online cancellation, recurring acknowledgments and reminders, and other notices ATM sends or makes available for the relationship. ATM does not currently permit you or an app to increase the amount or change the plan of an existing subscription without a separate payer-authorized flow.

If an app offers pledges before you can accept payments, a pledge is not a completed sale, payment, or guaranteed future subscription. ATM rechecks your payment readiness, the app's approval and configuration, the payer's saved consent terms, and duplicate-subscription protections before conversion. You must not treat an unconverted pledge as paid, fulfilled, or publicly attested, and you must not ask an app to bypass ATM's grace, cancellation, eligibility, or retry controls.

For ticketed events, scarce inventory must use ATM's hold and issuance logic or another approved ticketing flow. Public AT Protocol records, appviews, and firehose ordering must not be treated as the final authority for scarce ticket inventory.

9. Prohibited and restricted activity

You may not use ATM to receive payments for illegal, fraudulent, deceptive, unsafe, sanctioned, infringing, abusive, or prohibited activity, or for activity restricted by ATM, Stripe, another processor, card network rules, payment-method rules, or applicable law. This includes ATM's Acceptable Use Policy and, for Stripe-processed payments, Stripe's Prohibited and Restricted Businesses requirements.

ATM may review, suspend, remove, refund, cancel, block, rate-limit, or report activity where ATM believes doing so is needed for legal, safety, processor, risk, fraud, network, or ecosystem reasons.

If your business or use case may be restricted, you must contact ATM before accepting payments. Approval by an app, creator community, or event organizer does not mean Stripe, another processor, or ATM has approved the activity.

10. Public records and privacy

Public products, prices, discounts, application-fee agreement records, ATM settlement records, payment records, and proofs may be written to AT Protocol. When a live checkout identifies public attestation as enabled, ATM may publish a broker-anchored payment record showing the recipient DID, final amount and currency, payment type or cadence, transaction identifier, timestamps, public product or entitlement references, and proof references or status. The broker record does not by itself identify a signed-in payer.

Where ATM supports agreement records during beta, the offers and acceptances for both direct and delegated relationships are public. Your acceptance, authored after its publication disclosure, identifies you and the app by DID and carries the role, accepted rate, payment types, and settlement-cost cap. ATM writes it under the permissions you grant. ATM publishes corresponding settlement records showing the commissionable basis, allocations, delegated amounts, tariffs, normalized cost deductions and returns, and the full history of later corrections, including refund or dispute adjustments. These facts can reveal commercial information beyond the payment receipt. The public beta does not offer a separate private-terms or commitment-only settlement option. A lower rate requires a new acceptance; an old private approval is never published retroactively. Settlement details are public during beta; future payments may support private settlement records. ATM keeps the allocation amounts, applicable terms and correction history available to the parties entitled to them so they can check ATM's settlement calculations. Only after Spaces becomes generally available and ATM completes a reviewed integration may new payments and renewal cycles use private settlement records accessible to the appropriate parties. Corrections to earlier public settlement records remain public. Later private placement cannot make public beta records or copies already held by others private.

A proof is written to your own atmosphere account only when you manually sync it or have separately enabled automatic sync and ATM has a valid grant. Once public, your repository identifies you as its owner, and third parties may copy or index the record. A refund or dispute may invalidate the proof without erasing the historical payment record or third-party copies.

Card and bank details, credentials, identity-verification information, raw processor evidence and identifiers, buyer contact details, fulfillment secrets, and operational ledger state stay off protocol, including any future permissioned Spaces.

You agree not to place sensitive personal information in public protocol records and to handle any payer, customer, attendee, or supporter information you receive through ATM or apps in compliance with applicable privacy and data protection laws.

11. Changes and termination

ATM may update these Recipient Terms or change recipient onboarding, payment-account requirements, ATM application-fee rules, ticketing contracts, payment methods, or dashboard features as ATM and processor requirements evolve.

ATM may suspend or terminate recipient features if you violate these terms, fail processor requirements, create risk, receive excessive disputes, engage in prohibited activity, or if ATM can no longer support your account, country, business type, app, product, ticket, or payment flow.

12. Indemnity

You will defend, indemnify, and hold harmless Atmosphere Money Inc. and its directors, officers, employees, and agents from third-party claims, damages, penalties, losses, and reasonable legal fees arising from your products, services, events, content, fulfillment, taxes, privacy practices, infringement, unlawful conduct, breach of these Recipient Terms, or processor activity ATM performs within the authority you granted. This obligation does not apply to the extent a claim results from ATM's own breach, fraud, willful misconduct, or gross negligence.