ZyndPaySecurity and trust
ZyndPay moves and holds value across merchant payments, a custodial consumer wallet and P2P escrow. Identity checks, access controls and transaction reviews work together to reduce risk. Our approach and its limits are explained below.
How the platform is protected
No single check is treated as sufficient. Identity, account access, ledger integrity, compliance screening and approval decisions work together, with the exact path depending on the product, account and rail.
Businesses complete KYB before live collection. Consumers progress through risk-based KYC tiers. Depending on the surface, account protection includes passkeys, authenticator-based two-factor authentication, PIN or biometric confirmation, session controls and recovery checks.
Money movements are represented in balanced double-entry records. Consumer wallet state is derived from events, and idempotency prevents the same valid instruction from being applied twice. Reconciliation keeps external rail status distinct from an internal balance update.
Selected sensitive fields and blockchain key material are encrypted at rest with authenticated AES-256-GCM controls. Passwords and API credentials are stored as one-way hashes rather than recoverable plaintext. Access is limited by role and recorded for review.
Money leaving the platform passes applicable sanctions, PEP, AML, beneficiary and blockchain-risk checks before approval. A risk-based approval layer can hold an outflow for human review; a pending or blocked decision is not broadcast as a completed payment.
Custody, without euphemisms
A balance shown in the ZyndPay consumer app is an account balance maintained in ZyndPay’s custodial system; it is not a self-custody wallet where the user holds a seed phrase. Merchant payment services follow the balance, settlement and withdrawal terms agreed for that account. ZyndPay is not a bank, these balances are not bank deposits, and they do not carry deposit insurance.
Protecting your account
Use a unique password, enroll the strongest authentication offered on your surface, protect recovery material and review active sessions. Contact support quickly after a lost device or suspected takeover.
Blockchain transfers are generally final. Use only the stablecoin-network pair and address shown for the transaction, and re-check any payout or withdrawal destination before confirming.
A redirect, screenshot or customer message is not proof of settlement. Wait for the confirmed state in ZyndPay or its corresponding signed event before delivering value.
FAQ
No financial or software system can honestly promise absolute safety. ZyndPay uses layered identity, access, encryption, ledger, screening, approval and audit controls to reduce risk. Users still face custody, stablecoin, blockchain, account-takeover and third-party rail risks.
No. ZyndPay provides custodial consumer wallets and payment services. A balance is not a bank deposit and is not protected by a bank deposit-insurance scheme.
ZyndPay controls the on-chain key operations for the custodial consumer wallet. Users authorize actions through their account rather than holding a seed phrase for that ZyndPay balance.
Not as a publicly verifiable, independently attested artifact today. Internal custody, liability and solvency controls must not be confused with an external audit. ZyndPay will only make a public proof-of-reserves claim when the evidence and its limitations can be inspected.
Applicable identity, sanctions, PEP, AML, beneficiary and blockchain-risk controls run before approval. The approval path may hold an outflow for human review. Availability and exact controls depend on the product, account, destination and enabled rail.
Funds sent on a wrong or unsupported asset-network pair may be unrecoverable. Always use the exact pair and address shown for that payment or deposit; do not reuse details from another transaction.
Email [email protected] with the affected account and a concise description. Do not send a password, PIN, recovery code, private key or seed phrase. If you can still access the account, review sessions and authentication methods immediately.
Report a concern
For a suspected takeover, unexpected money movement or security concern, contact support with the affected account and observable facts. Never email secrets or authentication codes.