Automatic Payment Authorization

Title: Automatic Payment Authorization Document ID: automatic-payment-authorization Version: 1.0.3 Review status: local-review Prepared for local review: 2026-10-04 Effective date: [[WEB4U_LEGAL_EFFECTIVE_DATE]] (pending approval; snapshot effectiveDate: null) Legal entity: [[WEB4U_LEGAL_ENTITY_NAME]] Mailing/business address: [[WEB4U_LEGAL_MAILING_ADDRESS]] Support email: [[WEB4U_LEGAL_SUPPORT_EMAIL]] Privacy email: [[WEB4U_LEGAL_PRIVACY_EMAIL]] Governing law: [[WEB4U_LEGAL_GOVERNING_LAW]] Dispute process: [[WEB4U_LEGAL_DISPUTE_PROCESS]] Automatic payment is optional and separate from accepting a Service Contract, enabling auto-renew for one Site, or saving a payment method for provider use. Viewing this public copy does not authorize a payment. The current Payment Account may give one Account-wide authorization for Sites that the Account holder separately enables for auto-renew. Each Site keeps its own on/off setting. The current standard monthly, quarterly, and annual USD service-fee schedule is shown for review at the time of authorization; it does not set or promise future prices. Each automatic renewal charge still requires the current Payment Account, an approved Account-to-Site relationship, the exact current accepted Service Contract, and a selected-term fee equal to the current configured fee for that term. Setup fees are not charged again on renewal. This local-review draft does not decide whether future fee or authorization-text changes require new consent. Renewal charges use that Payment Account’s current default payment method; changing the default does not by itself revoke the Account-wide authorization. The authorization does not transfer to a different Payment Account. Turning off auto-renew for a Site stops future automatically initiated renewal charges for that Site; it does not clear the Account-wide authorization or change another Site’s setting. It does not shorten an already-paid Service term or promise cancellation of a payment already initiated. Grace-period, retry, and reminder timing depend on configuration and are not fixed in this draft.