Company
Trust Center
Everything a procurement or compliance team asks for, in the order they ask for it. Where a fact is not confirmed yet, this page says so instead of leaving a gap.
Placeholder — not reviewed legal wording. TODO(compliance)
The entity and registration facts below are taken from the Alberta Corporate Registry and FINTRAC's public MSB registry. Certification, scheme-registration and sub-processor facts marked TODO(compliance) are not confirmed yet and are not claims: Cleared-pay does not represent itself as certified under any standard or registered with any card scheme until the document exists.
Legal entity
Who stands behind the Cleared-pay name. The same details appear on the imprint and in the footer of every page.
- Trade name
- Cleared-pay
- Legal name
- Kesheron Digital Ltd.
- Legal form
- Corporation under the Business Corporations Act (Alberta), Canada
- Incorporated
- 24 February 2026
- Registered office
- 13-4205 30 Street NW, Edmonton, Alberta T6T 2G9, Canada
- Register
- Alberta Corporate Registry
- Alberta corporate access number
- 2027926902
- Compliance contact
- legal@cleared-pay.com
- VAT identifier
- TODO(compliance)VAT identifier
See also the imprint.
Regulatory status
The registration held, who supervises it, and the regulator's own register entry, so it can be checked rather than believed.
- Registration held
- Money Services Business (MSB)
- Competent authority
- FINTRAC (Financial Transactions and Reports Analysis Centre of Canada)
- MSB registration number
- N300001079
- Registrant name in the registry
- Kesheron Holdings Ltd.
- Activities registered
- foreign exchange dealing, money transferring, dealing in virtual currencies and payment service provision
- Registered on
- 17 July 2026
- Valid until
- 28 February 2029
- Public register entry
- FINTRAC MSB registry search (search by name)
- EEA and UK authorisation
- None. Card acquiring runs through licensed acquiring partners, named on the imprint from the date each agreement takes effect.
Where Cleared-pay is not licensed
Stated explicitly, because silence on this question is worse than an answer nobody likes.
Cleared-pay is the trade name of Kesheron Digital Ltd., a corporation incorporated in Alberta, Canada, registered as a Money Services Business with FINTRAC for foreign exchange dealing, money transferring, dealing in virtual currencies and payment service provision. It holds no banking, deposit-taking, lending or investment permission and offers no service that requires one. It does not hold an authorisation as a payment institution or electronic money institution in the European Economic Area or the United Kingdom, and it does not itself acquire card payments. Card acquiring is provided through licensed acquiring partners, each named on the imprint from the date its agreement takes effect.
Certifications and scheme registrations
A certification is a document with a scope and a date on it. Until that document exists, this page shows a placeholder rather than a badge.
- PCI DSS validation status
- TODO(compliance)status, assessor and validation date
- Attestation of compliance
- TODO(compliance)document and date
- ISO/IEC 27001
- TODO(compliance)certificate, scope and date
- Visa third-party agent registration
- TODO(compliance)registration status
- Mastercard registration programme
- TODO(compliance)registration status
Safeguarding of client funds
How money in flight is held, and what that protection does not extend to.
A balance held for a merchant is not a bank deposit and is not covered by a deposit guarantee scheme. The accounts used, the institutions holding them and the method applied are disclosed here and in the safeguarding statement once confirmed.
TODO(compliance)safeguarding method, accounts and institutionsSee also safeguarding of funds.
Data protection and sub-processors
Where data is processed, who processes it on our behalf, and the agreement that governs it.
- Data residency
- TODO(compliance)processing regions
- Data protection contact
- TODO(compliance)contact address
- Data processing agreement
- TODO(compliance)document to download
- Transfer mechanism
- TODO(compliance)mechanism for any transfer outside the EEA
| Purpose | Sub-processor | Processing location |
|---|---|---|
| Cloud hosting and compute | TODO(compliance)provider | TODO(compliance)region |
| Managed database | TODO(compliance)provider | TODO(compliance)region |
| Transactional email | TODO(compliance)provider | TODO(compliance)region |
| Error monitoring | TODO(compliance)provider | TODO(compliance)region |
| Customer support desk | TODO(compliance)provider | TODO(compliance)region |
See also the privacy policy.
Security practices
What the platform does today, and the assurances that are not in place yet.
- Card data never reaches a merchant server or ours in storable form: hosted fields and the hosted payment page tokenise it, and only brand, last four digits, issuing range, expiry, issuer country and a fingerprint are kept.
- Secrets are stored as hashes with a pepper and shown exactly once. A rolled key keeps working for a stated grace window so a rotation causes no failed requests.
- Webhook payloads are signed, and the signature is verified over the raw body; the reference implementation is published in the documentation.
- Two-factor authentication with a time-based code is required on the merchant portal and the internal backoffice, with an idle timeout on every session.
- Every write produces an audit entry, and every payment state change produces an event row in the same transaction as the change itself.
- Requests carry a per-response content security policy with a nonce, and the hosted payment page runs a documented script inventory for PCI DSS 6.4.3.
- Encryption at rest
- TODO(compliance)key management and rotation policy
- Penetration testing
- TODO(compliance)cadence, scope and latest test date
- Business continuity
- TODO(compliance)recovery objectives
- Personnel screening
- TODO(compliance)background-check policy
Vulnerability disclosure
If you have found something, we would rather hear it from you than from an attacker.
Report a vulnerability
Send the detail, the impact and the steps to reproduce. You get an acknowledgement, a triage decision and updates until it is fixed.
security@cleared-pay.comTODO(compliance)mailbox not live yet
Availability
Uptime is a measurement, not a promise, so it lives on a status page rather than in a headline.
- Historical uptime
- TODO(compliance)measured figure once there is traffic
- Incident history
- TODO(compliance)public incident log
Running a vendor review?
Ask for what is missing from this page. If it exists, you get the document; if it does not, you get a date.