Schedule Q | Connected-account payment processing
Version 3.0 applies only through valid acceptance of the online MSA or a valid amendment. A private commercial order and provider approvals remain separate.
Q.1 Conditional scope
These terms apply only where Schedule A selects Stripe Connect and the specific Merchant/program is approved and enabled. Stripe Connect is a distinct payment-acceptance flow from card-funded NFT checkout. Nothing here represents that Stripe has approved RT, Merchant, a country, product or transaction type. Stripe's actual onboarding and capability decisions control use of its service.
Q.2 Separate Stripe agreement
For full-service accounts, processing is supplied by Stripe under the applicable country’s Stripe Connected Account Agreement at https://stripe.com/connect-account/legal/full, including its Stripe Services Agreement. Recipient-only payouts instead use https://stripe.com/connect-account/legal/recipient. Before use, RT must present the correct agreement and obtain Merchant’s express acceptance; acceptance of this MSA without that presentation and assent is insufficient. Disclose Stripe’s Privacy Policy at https://stripe.com/privacy and, for full-service accounts, the country-specific acquirer disclosure at https://stripe.com/legal/acquirer-disclosure. Custom branding does not remove these requirements.
Q.3 Authorized activity
Merchant authorizes RT, only within the actual Connect configuration and permissions, to create or facilitate onboarding for the relevant connected account, transmit required accurate account/business information, access relevant account and transaction data, facilitate payment/refund/dispute and reconciliation instructions, communicate required information to Stripe, and collect agreed platform fees from eligible balances where supported and lawfully authorized. Payout scheduling, restrictions, reserves and loss recovery may be performed only where the program supports them and the required authority exists. These permissions do not grant control over unrelated Stripe accounts or external assets.
Q.4 Data and instructions
RT accesses and uses connected-account data for providing/supporting the selected Services, account administration, fraud/security, compliance, disputes and enforcement under Schedule G and RT's privacy notice. Merchant must keep information current and respond to Stripe and RT requirements. It must not authorize false onboarding data or misrepresent its products, beneficiary or location. Acceptance evidence and the configured permissions must be retained before production use.
Q.5 Fees and liabilities
Schedule A must state RT fees and whether Stripe/provider fees are included or separate. Merchant authorizes supported deductions only for agreed or otherwise lawfully payable amounts. Chargebacks, refunds, returns and negative balances attributable to Merchant remain Merchant's reimbursement obligations under the core Agreement, including where Stripe initially charges RT under a separate platform liability arrangement. RT cannot contract away its independent obligations to Stripe or charge Merchant twice.
Q.6 Restrictions and exit
Stripe may independently restrict capabilities, payouts or the account under its terms. Disconnection or termination does not erase existing disputes, reserves or payment liabilities. RT may stop its own Services and permitted instructions; any ongoing Stripe access or relationship is governed by Stripe and the actual account configuration. This schedule does not include Stripe Treasury, Issuing, crypto services, lending or a merchant-of-record model unless separately expressly contracted and approved.