Security

Your account and data, protected by design.

From hashed passwords and one-time API secrets to role-based access and masked bank details, security is built into how ZOZOPAY works. Here is exactly what we do today, and what we are still adding.

Hashed credentials Role-based access Revocable API keys

Layers

Security at every layer

Sign-in

Passwords are stored as hashes and sessions expire.

Access

Roles limit what each person can see and do.

API keys

Secrets are shown once and can be revoked any time.

Data

Bank numbers are masked and documents are access-controlled.

What protects you today

Sign up now

Hashed passwords

Passwords are never stored in readable form. Only a salted hash is kept.

One-time API secrets

An API secret is displayed once when created and stored only as a hash, so we cannot show it to you again.

Instant revocation

Revoke a key from your dashboard the moment you suspect it is exposed.

Role-based access

Team members are Owner, Admin, Developer or Viewer, and only the right roles can create payments or manage keys.

Masked bank details

Your account number appears as its last four digits across the dashboard.

Secure headers

Our API sets standard security headers on every response.

Who it protects

Built for teams with real money at stake

Growing teams

Give each person only the access their job needs.

Developers

Rotate and revoke keys without touching production.

Finance

Bank details stay masked in everyday use.

Founders

Payouts go only to verified accounts.

Compliance

Reviewer decisions record who acted and why.

Operations

Separate admin access for our own staff.

Details

How we handle sensitive data

KYC documents

Uploaded to your account only and served through authenticated requests to you and authorised reviewers. Only PDF, JPG and PNG files up to 5 MB are accepted.

Recorded decisions

KYC, bank and dispute decisions record the reviewer's name and any reason given.

Separate staff roles

Our own team uses separate admin roles for support, finance and administration.

Session handling

Sessions use short-lived access tokens that are refreshed rather than kept alive indefinitely.

Coming next

What we're adding to security

These are on our roadmap and not available yet.

Two-factor authenticationSoon

An extra step when signing in.

Activity logSoon

A viewable history of who did what in your account.

IP allowlistsSoon

Restrict API access to your servers.

FAQ

Frequently asked questions

How are passwords stored?

As salted hashes. We never store your password in readable form.

How are API secrets protected?

A secret is shown only once when the key is created and is stored only as a hash. If you lose it, create a new key and revoke the old one.

What if a key is exposed?

Revoke it from your dashboard right away. A revoked key stops working.

Who on my team can create payments or manage keys?

Owners, Admins and Developers can create payments. Viewers can look but not change things.

Do you support two-factor authentication?

Not yet. It is on our roadmap.

Are you PCI DSS or ISO certified?

We do not claim any certification on this page. If you need details for a security review, contact us and we will answer plainly.

Is my data encrypted?

We have not published details about encryption in transit or at rest yet, and we will not claim what we have not documented. Contact us if you need this for a security review.

How do I report a security concern?

Contact us through the contact page and mark the topic as Other. We will respond as quickly as we can.

Build on a platform you can trust

Sign up and see the access controls and API key tools for yourself.