image
Bank-grade mindset · signed events

Trust Center

Security built for creator finance

Bank details, GST, contracts, and payout events deserve more than a generic SaaS checklist. Here’s how CreatorPay locks them down.

Hashed passwords
Account-scoped data
CSRF on dashboards
Signed settlement events
CreatorPay security layers

Account security

Password hashing, expiring sessions, and admin suspend controls keep rogue access out.

Data isolation

Brands, invoices, documents, and payouts are scoped to your creator ID — never mixed.

Sensitive fields

PAN, GST, UPI, and bank details power invoices & Kreatorio — never sold for ads.

Event integrity

Settlement events verify signatures before status changes hit your ledger.

Kreatorio trust

Settlement without exposing secrets

Payment credentials stay server-side. Creators see payout status and UTR — not infrastructure keys. Document uploads for verification are tied to your account vault.

  • Server-only settlement credentials
  • Idempotent payout status updates
  • Profile bank/UPI edited in one place
01BrowserAuth session · CSRF tokens
02AppAccount scoping · rate limits
03SettlementsSigned events · server keys
04StorageIsolated docs · hashed secrets
Ready when you are

Questions about security?

We’ll walk through data handling, Kreatorio verification, and event integrity with your team.