Payment Security Policy
Effective 16 August 2026 · Version 2026-08-16.1
This Payment Security Policy explains how Cite Worthy handles invoices, payment evidence, settlement review and billing access. It is designed to prevent a browser return, screenshot or unverified message from changing a customer's entitlement.
1. Current payment route
Cite Worthy currently uses administrator-reviewed payment arrangements. OnePay hosted checkout, Card on File, automatic charging and provider refunds remain disabled until their exact merchant, currency, callback, status, refund and settlement capabilities are certified and explicitly enabled. The public website does not collect raw card details.
2. Immutable invoices
Every issued invoice locks the customer snapshot, catalogue version, plan allowances, amount, currency, term and payment route. Sri Lankan residents receive LKR invoices. USD requires current reviewed non-resident evidence. We do not silently convert or rewrite an issued invoice.
3. Manual evidence
If a customer pays by bank transfer, any uploaded receipt or reference is treated only as evidence for review. It is stored privately and access is restricted. An authorised administrator must verify actual settlement, the bound invoice, exact amount and exact currency before access can activate. A browser page, email or uploaded image cannot approve payment.
4. Reconciliation and exceptions
Ambiguous attempts remain pending and block unsafe replacement or route switching. A duplicate, late, partial, excess or mismatched payment opens a reconciliation or overpayment review. It never grants a second entitlement. Refunds, credits and corrections use compensating records so the historical invoice and payment trail remains intact.
5. Administrative safeguards
Sensitive payment approval, rejection, refund, dispute, settlement and residency actions require an explicit administrator ability, recent authentication, a reason, expected state, idempotency controls, consequence review and audit evidence. Support mode is time-limited, reasoned and read-only and does not expose full sensitive evidence.
6. Storage and retention
Payment evidence is kept in private application storage, not the public web folder. Signed access is short-lived where used. Temporary objects are normally removed within 24 hours. Billing, transaction, settlement, refund, dispute and audit records are retained only as long as legally or operationally required or while a documented hold applies. Backups are encrypted and follow the stated retention cycle.
7. Customer safety
Use only payment instructions tied to an authentic Cite Worthy invoice. Verify unexpected requests with [email protected] before paying. Never send online-banking passwords, one-time codes, full card details or unrestricted account access. Report a suspected fraudulent instruction or account compromise immediately.
8. Provider activation
If OnePay or another payment provider is enabled later, the service will bind each attempt to a server-created transaction reference and reconcile authoritative provider status against the exact transaction, amount and currency. A callback or browser return will remain a notification only, never approval by itself. The related policy will be updated before customer use. Payment and security contact: [email protected]
Questions: [email protected] · Codezela Technologies (Pvt) Ltd