Schedule E | Payment Acceptance and Network Requirements
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.
E.1 Applicable methods
Accept only the payment methods and transaction types explicitly approved for the account, sales channel and territory. Comply with current method, acquirer and network rules and binding provider instructions. Keep descriptors, merchant category, URLs and beneficiary details accurate. Approval for one method is not permission for another or for an unapproved regulated product.
E.2 Authorization and fraud controls
Obtain the payer's required authorization and method approval before capture. Use mandated authentication, risk and verification controls. Do not split charges, conceal a decline, bypass a risk block, misstate a transaction or retry beyond provider rules. For ambiguous outcomes, check authoritative status and use idempotency rather than charging again. Authorization, 3-D Secure or token minting does not guarantee settlement or defeat every dispute.
E.3 PCI and data handling
Use provider-hosted capture or an expressly approved integration. Maintain the validation and safeguards applicable to actual card-data handling. Never retain CVV/CVC, PIN/PIN block or full track data after authorization. Do not send full payment credentials to RT through ordinary email, chat, logs or legal forms. Any storage of account data requires the appropriate authorization, necessity and PCI safeguards; a generic contract does not certify compliance.
E.4 Sales and prohibited processing
Submit genuine approved sales of Merchant's own business. No card testing, transaction laundering, fictitious/self-funding transactions, undisclosed third-party sales, duplicate charges, unauthorized cash advances or hidden financial products. Recurring, installment, card-present, mail/telephone, advance-sale and marketplace models require specific approval and their mandated disclosures and consents.
E.5 Fees and refunds
Buyer-facing surcharges or convenience fees need RT approval and must satisfy current law and method rules, including debit/prepaid restrictions, registration, caps and disclosure. Return refunds through the original method where required; exceptions need provider approval and lawful verification. Preserve mandatory buyer and dispute rights. Coordinate a refund already subject to chargeback to avoid double payment.
E.6 Evidence and monitoring
Monitor dispute contacts daily on Business Days, provide complete relevant evidence by the notified deadline and implement lawful remedial controls when fraud/return/dispute levels rise. Network program thresholds and charges are the actual applicable requirements, not generic hard-coded figures. Merchant bears attributable payable assessments and transaction liabilities subject to the core Agreement's causation, accounting and legal limits.