COVU OS Lite Payment Authorization
This Payment Authorization (this "Authorization") is a distinct artifact from the COVU OS Lite Terms of Service (the "Terms") and from any Additional Module Order or Service Order the Agency has accepted. Accepting the Terms does not authorize any charge. Accepting a Module Order or Service Order sets the module, rate-card version, price, cap, and term — it does not by itself store a payment method or authorize an automatic charge. Only this Authorization, completed with a stored payment method through COVU's payment processor, does that.
This Authorization becomes effective only when a current agency owner, administrator, or an owner/administrator-designated billing authority accepts it for the Agency identified at acceptance, and only after the processor's own hosted card-entry flow separately confirms a payment method. Two acts are required, not one: the click-accept below, and the processor's own mandate confirmation. Neither substitutes for the other.
1. Who may accept
Only a current agency owner, administrator, or a person the agency's owner or administrator has designated as the agency's billing authority may accept this Authorization or manage the resulting payment method. A billing authority does not need to be the agency owner — COVU records exactly which person accepted, separately from who owns the agency.
2. What is authorized
By accepting this Authorization, the Agency:
- authorizes COVU, Inc. and its payment processor to store the business payment credential the Agency submits through the processor's own hosted card-entry flow — COVU's servers never receive, process, log, or store the card number, expiration date, or security code;
- authorizes automatic charges, calculated under an accepted Module Order or Service Order, up to the displayed spending cap for that Order, on the billing cadence stated in that Order;
- confirms that the accepting person may bind the Agency and authorize a payment method on the Agency's behalf;
- accepts the displayed merchant name, billing descriptor, charge timing, retry terms, revocation method, and receipt delivery; and
- understands that replacing or revoking the payment method does not cancel amounts already earned under an accepted Order.
This Authorization does not by itself unlock a module, set a price, or create a spending cap — those come only from an accepted Module Order or Service Order. This Authorization only authorizes the charge mechanism for amounts an accepted Order already defines.
3. Auto-reload is a separate election, off by default
Automatic reload of a prepaid credit balance is not part of this Authorization and is never enabled by accepting it. Auto-reload is its own distinct election, presented separately, defaulting to off, and requiring its own explicit acceptance showing the reload amount, threshold, and maximum frequency before it can be turned on. Accepting this Authorization alone never turns auto-reload on.
4. This mandate is specific to COVU, Inc.
This Authorization and the resulting stored payment mandate are made to COVU, Inc., the entity identified above. If COVU assigns its agreements to a controlled affiliate or successor (as the Terms and the Service Network Services Agreement permit in a reorganization, merger, financing, conversion, or sale), a payment mandate made to COVU, Inc. does not automatically carry over to the new entity. COVU will identify affected agencies and request a refreshed Authorization before charging the new entity. An Agency's existing mandate remains valid for charges by COVU, Inc. until COVU gives notice of an assignment and requests a refresh.
5. Revocation and failed payments
The Agency may revoke this Authorization and remove the stored payment method in OS Lite at any time. Revocation stops future automatic charges but does not cancel amounts already earned under an accepted Order. If a charge fails, COVU may retry only as permitted by the payment processor, card network, and applicable law, and will not retry a revoked or returned-as-unauthorized charge without a fresh authorization.
6. Acceptance
By selecting Authorize payment method, I confirm that I am a current owner, administrator, or designated billing authority for the Agency named at acceptance, and I authorize COVU, Inc. and its payment processor as described above. I understand that auto-reload remains off unless I separately elect it, and that this Authorization is specific to COVU, Inc.
COVU will preserve the exact document version and SHA-256, the displayed statement, the accepter's identity and role, the entity this Authorization names, the timestamp, and the processor's own confirmation reference in the agreement ledger, and will provide a downloadable copy on request.