Security
Last changed
In short
CIC Pay holds no security certification of its own, so this page says that first. It then describes today’s controls: where a card number goes, sign-in, key storage and the record of payments. It is a description, not an audit report or a contractual promise.
What we don’t claim
CIC Pay holds no independent certification. There is no PCI DSS, SOC 2 or ISO 27001 certificate in CIC Pay’s name, and nothing on this site should be taken to suggest one.
Card payments are processed by the providers connected to your account, and each of them is responsible for its own card-security obligations. Their certificates belong to them. We do not borrow them or present them as ours.
If CIC Pay is ever certified, this page will name the certificate, what it covers and its date. CIC Pay is not a bank, and no application is approved in advance.
The path a card number takes
- Typed into CIC Pay’s own card fields. They run as a separate page under a strict content policy that lets one known script run and nothing else. Your site and your systems never see the number.
- Sent to one place. Over an encrypted connection, for that attempt only, the number travels to the provider handling the payment. No one else receives it.
- Not kept. CIC Pay stores a masked version of the card and the reference the provider gave it, which is enough to find the payment again and nothing more.
- Your customer knows whom they are paying. Your business name, the sum due and your support contact stay in view above the card fields throughout.
Sign-in and access
- Sign-in is by email and password, verified in-house by CIC Pay. Passwords are stored hashed, never in readable form.
- Nobody can open an account on their own. Each one begins with an invitation: after an application is approved, from a broker, or from the CIC Pay team.
- Every person has a role and sees what that role allows. Each merchant’s records are separated from every other’s.
- Sign-ins, privileged actions and changes to configuration are recorded, and sessions expire and can be ended.
Keys and secrets
- Your API keys are stored only as hashes. You see each one once, when you create it. A key works in one environment, test or live, and you can revoke it whenever you choose.
- The credentials CIC Pay holds for its providers are encrypted, and only the part of the service that talks to a given provider can open that provider’s credentials.
- No secret is ever sent to a browser.
How payments are recorded
- Test and live never mix: separate keys, separate settings, and no route by which a test payment moves real money.
- Every payment-creating request carries a key that makes it safe to repeat. Repeat it and you get the original payment back, not a second charge.
- Webhooks are signed and time-stamped. Check both before acting on one, then confirm the payment’s state through the API, which has the final word.
- Reaching your order-complete page is not proof of payment. A payment is real only once the provider confirms it, and open payments are checked again until they have an answer.
- Money is written to an append-only ledger: a mistake is put right by a further entry, and the earlier one remains.
This website
This site sets no cookies of its own. When analytics is switched on, it uses Cloudflare Web Analytics, which counts visits without cookies, and it is not part of the hosted payment page. Every page is served over HTTPS under a strict content policy. The cookie page has the detail.
Reporting a problem
Email sales@cryptoiscoming.com with the subject line “Security report”. It helps us act quickly if you include:
- the page, address or component involved;
- the steps that show the problem;
- what someone might achieve with it;
- a safe way to reach you.
Test only as far as you need to show the issue. Leave other people’s data alone and do nothing that disrupts the service. We do not run a paid reward scheme for reports.
Something unclear on this page? Write to sales@cryptoiscoming.com.
