Connected-account payment terms
Agreements, privacy information and disclosures for payment processing through an enabled connected account.
Payment services: terms and disclosures
Find the documents for your payment method and provider. Your accepted product terms and onboarding identify which documents apply. A provider reference in this directory does not mean every service is available to every customer.
RT is software, not a bank. Merchant payment acceptance, issued cards, virtual accounts, wallets and stablecoin services have different agreements and eligibility requirements. No generic RT merchant acceptance replaces a required provider or cardholder agreement.
Which agreements apply?
| Service | Documents before activation | Scope |
|---|---|---|
| Merchant payment acceptance | Correct RT online MSA, separate private Schedule A, relevant schedules and actual processing-provider agreement. | Merchant legal entity, establishment, customer territories and approved payment model. |
| Connected-account processing | Full-service or recipient agreement, privacy and applicable acquirer disclosure. | Actual country and account agreement type, including Custom accounts. Recipient-only terms do not authorize full processing. |
| Personal or business issued cards | Final program-specific cardholder, authorized-user, fee, privacy and electronic-communications documents. | Actual issuer, country, card category and approved program. Business documents do not replace personal terms. |
| Stablecoin accounts and custody | Correct end-user or business agreement, privacy and applicable risk disclosures. | Actual direct-account, custodial or transactional model. Program-level supply agreements do not enroll every end user. |
| Bank transfers or virtual account identifiers | Actual account/payment terms, rail disclosures and any separate debit mandate. | Provider, bank if applicable, rail, country, currency and account ownership. An IBAN or routing number alone is not proof of a deposit account. |
| NFT or USDC checkout | Checkout disclosure and actual provider terms, asset/issuer terms and risk disclosures. | Actual seller, collection provider, asset, network, token rights and payout route. |
Only the documents presented for your enabled product apply; this directory does not enroll you in all listed services. If a required final agreement or approval is unavailable, the affected service cannot be activated. RT is software, not a bank.
Card-program legal documents
Program-specific cardholder agreements, electronic communications, privacy information and applicable financial-service disclosures.
Stablecoin account and service documents
Account agreements, eligibility, privacy information and disclosures for enabled stablecoin services.
USDC checkout and settlement disclosures
USDC payment acceptance or settlement requires an enabled provider or approved direct-wallet flow, a supported network and the correct token contract.
NFT checkout disclosures
The checkout must clearly identify the merchant, the purchased product or service, any NFT or digital entitlement, the price, charges, delivery and refund terms.
Bank-transfer and payment-authorization notice
Bank transfers are available only through the provider, account type, country and rail enabled for the user.
Digital-asset risk disclosure
Read this disclosure before using an enabled digital-asset service through RT.
RT agreements, privacy and complaints
Merchant agreements and schedules A–K, Q, R, S and Z · Platform terms · Privacy Policy · Support and complaints
Contact support@rt.app for operational assistance, legal@rt.app for contractual notices, security@rt.app for a security incident, and privacy@rt.app for a privacy request. Provider and regulatory complaint channels remain available.