LOADING
DOCUMENTS, EVIDENCE AND EXPIRY
Every document a merchant, owner, product or decision depends on — filed once, hashed, versioned, and readable by whichever service is entitled to it.
Identity, corporate, banking, processing, products, compliance and underwriting. Each document links to the merchant, and where relevant to the SKU, batch and lot.
A replacement is a new version. Compliance documents are never silently replaced, because the question later is usually what was on file at the time.
Certificates, licenses, permits, insurance and identity documents all carry expiry. A lapse suspends what depends on it automatically.
For a dispute or an acquirer inquiry, the file is compiled from what already exists rather than gathered after the request arrives.
From the application, the merchant surface, or a compliance request. The origin is recorded either way.
Content is hashed on arrival. A replacement becomes a new version; the previous one stays readable.
Filed by category and linked to the merchant, and where relevant to the owner, SKU, batch or lot.
Certificates are checked against a known-laboratory registry; identity documents run authenticity and liveness checks.
Every document carries an expiry. The horizon is visible before the date, not after it.
An expired certificate suspends its SKU. Lapsed insurance opens a critical ticket. Neither waits for someone to notice.
Dispute packets and acquirer enquiry files are compiled from what already exists.
No service asks a merchant for a document another service already holds. If the Cloud has a verified owner ID from onboarding, underwriting reads that record rather than requesting it again.
Version history and expiry on every document. The expired COA is why a SKU cannot be sold — the document is upstream of the product state.
