Skip to content

Trust

Security

How Cycle is built so that the most sensitive data never reaches it.

4 min readUpdated 12 November 2026Draft

The short version

  • Card data goes only to the bank
  • Cycle never holds funds
  • Keys are encrypted
  • Two-factor sign-in for every team

This text is a draft and has not yet been reviewed by a lawyer.

1. Where card data goes

Customers type their card on the acquiring bank's page. The bank returns a token; Cycle stores only that token. This keeps merchants in the lightest PCI DSS scope (SAQ A).

2. How money flows

Charges are made by your bank and settle straight into your account. Cycle never holds or moves funds.

3. Credentials and keys

Bank credentials and API secrets are encrypted at rest. Secret API keys are shown once and stored only as hashes. Test and live keys are separated.

4. Account security

Two-factor sign-in and passkeys, session management, roles per team member and a full activity log.

5. Integration security

Webhooks are signed so you can verify they came from Cycle. API writes are idempotent so retries never double-charge.

6. Not done yet

An external penetration test and SOC 2 report are planned but not completed. SSO (SAML) is on the roadmap.

7. Reporting a vulnerability

Email hello@cycle.am with the details. We reply within two working days and will not take action against good-faith research.