rt.app

RT ยท Legal documents

Schedule D | Provider Roles, Funds Flows and Risk Controls

Online edition v3.0 | Issued 20 October 2026 | Effective on valid acceptance

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.

D.1 Approved configuration

Before production use identify the actual provider/program, Merchant legal entity, charge model, collection recipient, conversion provider if any, asset/network, payout beneficiary, fee flow, reserve holder and RT permissions in Schedule A or the authenticated activation record. RT supplies the enabled software and transmits permitted instructions. A card-funded purchase, direct card acceptance, bank payment and direct digital-asset transfer must be represented as their actual distinct flows.

D.2 Payment and discharge

Only an authorized collection recipient for the approved flow receives payment for Merchant. Receipt by that recipient discharges the buyer for the amount received, subject to applicable reversals and refunds; Merchant must not collect it again. A limited collection-agency appointment applies only to the role actually performed and only where supported by applicable law and the provider program. This schedule gives no blanket agent-of-payee, payment-processor or money-transmission exemption opinion.

D.3 Provider custody and permissions

The provider's terms govern accounts, custody, regulated processing, conversion and settlement it supplies. The actual structure determines legal title, commingling, segregation, insurance and control. RT does not promise that every reserve is held in a segregated merchant-titled account, that a wallet is self-custodial, or that any balance is deposit-insured. RT's instruction rights are limited to the provider permissions and lawful authority actually granted.

D.4 Payouts

Eligible cleared proceeds are paid to the verified Merchant destination under Schedule A, net of agreed fees, valid adjustments and justified reserves. Provider cut-offs, holidays, incomplete verification, compliance reviews, disputes, returns and technical conditions may delay a payout. A displayed amount or schedule estimate is not a guarantee of available funds. RT must account for deductions and may not treat a hold alone as revenue.

D.5 Reserves and review

Core Sections 8-9 govern protective measures, including reserves up to 100% of affected eligible proceeds where reasonably necessary, prompt notice where lawful, documented exposure calculations, review at least every 30 days, partial release when justified and a continuing basis for any extension. No automatic 180-day release is promised where a real exposure or binding restriction continues. A restriction does not transfer ownership to RT or authorize indefinite retention without justification.

D.6 Setoff and security

Recovery must be for a properly payable obligation from eligible Merchant assets within the lawful mandate, with accounting and no double recovery. The security grant is limited to the Merchant's described settlement/reserve rights and proceeds; perfection, priority and enforcement require applicable legal steps. A bank debit, personal guarantee, cross-company recovery or new custody arrangement needs its own valid basis. RT cannot recall or freeze an external wallet merely by writing that power into a contract.

D.7 Regulatory or provider change

RT may restrict or discontinue a flow that loses legal or provider support and require a compliant reconfiguration before further activity. A substitute provider requires appropriate diligence, disclosures, agreements and permissions. Mandatory law and lawful third-party restrictions prevail; Merchant cannot direct RT to evade them.