Compliance & Security
Last updated: 31 July 2026
Payth is built for corporate merchants, and compliance and security are core to how it operates.
Merchant vetting (KYB)
Every merchant is an incorporated company, vetted and approved by Kodelyth before provisioning. There is no anonymous or self-serve access.
Anti-fraud
Veltix, our verification engine, checks each payment against the provider’s own confirmation and never counts a payment twice: a Transaction ID is recorded once, and a checkout completes only with a real payment of the right amount. It also watches for unusual payments (one number paying again and again, amounts far above the usual, guessed Transaction IDs) and flags them to us for review.
Encryption & data protection
- TLS in transit on every connection, enforced by HSTS.
- AES-256-GCM on every stored credential — provider sign-ins, API tokens and integration secrets — each under its own key, derived from a secret held outside the database.
- HMAC-signed webhooks so every callback is verifiable.
- Two-step confirmation before a settlement is sent to the bank, before a payment is refunded, and before any provider sign-in is changed.
- Status-guarded settlement to prevent double-spend and double-notification.
- Transaction records are held in an access-controlled database on private infrastructure. They are not separately encrypted at rest, and we do not claim that they are.
Certifications
Kodelyth is pursuing formal information-security certification (ISO 27001). This page will be updated when certification is issued; we do not claim certifications we do not hold.
Reporting
To report a security concern or suspected abuse, contact [email protected].
This page describes our operational posture and is not a warranty or certification. Contact us for the compliance documentation relevant to a corporate engagement.