How Paysasa Keeps Your Money Safe: Security Controls Explained

Trust is the most important feature of any payments platform. If people do not feel safe, nothing else matters. Paysasa was built to make digital payments safer and easier, with controls you can explain to a customer and to an auditor.

This deep dive explains the main security controls on Paysasa and what you can do to stay safe.

Account protection

PINs

Sending, withdrawing, converting and other money moves usually require your wallet PIN. Even if someone gains access to your logged-in device, they still need the PIN to move money.

Device checks and sessions

Paysasa uses device checks, and you can review active sessions and devices in your settings and log out of any you do not recognise.

Two-factor authentication on payouts

Payouts can require two-factor authentication, adding an extra step before money leaves the platform.

Extra verification on sensitive actions

Sensitive actions can require additional verification, while event logging and audit trails support compliance and incident investigations.

Verification and trust

• KYC and business verification are required before checkout and withdrawals.
• Gold and Platinum badges are granted after review for trusted brands.
• Escrow and buyer protection let buyers pay strangers without handing money over directly.

How payments stay accounted for

The Paysasa security page describes several controls that keep payments in the right place.

PCI DSS-compliant card partners

Card data is handled through PCI DSS-compliant payment partners, so merchants do not handle raw card details.

Signed requests

Business API calls use a tenant signature header, so a captured request cannot be replayed from another host.

Wallet holds

Recent top-ups stay on hold before withdrawal or M-Pesa send. This makes "top up with stolen funds, then cash out quickly" fraud much harder. In-app transfers between wallets are not held.

Checkout settlement

Paid sales settle to the business wallet chosen for that checkout, not a personal fallback. Money from customers goes where the business intends.

Access control

Business staff see only the permissions they are given. Closed or suspended businesses cannot change settings.

Fraud review

Unmatched Paybill deposits stay unmatched until a person matches them. They are not credited automatically, which prevents money landing in the wrong account.

Developer security

• API keys are scoped to a single business and can be revoked at any time.
• Webhooks are signed with HMAC-SHA256 so your server can verify they came from Paysasa.
• Idempotency keys prevent duplicate charges and payouts when requests are retried.

Practical scenarios

A cashier's phone is stolen. Without the PIN, money cannot be sent from the account, and the owner can remove the cashier's device session and adjust permissions from the dashboard.

A customer enters the wrong till. The deposit does not land in a random business wallet; it stays unmatched until a person reviews it.

Someone tops up with suspicious funds and tries to withdraw immediately. The hold on recent top-ups gives time for problems to surface before money leaves the platform.

A developer's server retries a payout after a timeout. The idempotency key ensures the recipient is paid once, not twice.

These scenarios are illustrative, but they show how layered controls work together: no single control has to be perfect, because each one backs up the others.

Your part in staying safe

Platform controls work best alongside good habits:

1. Never share your PIN or one-time codes — Paysasa will never ask for them.
2. Use a strong, unique password.
3. Review devices and sessions regularly.
4. Confirm payments in your dashboard, not from SMS screenshots.
5. Give staff only the access they need, and remove access promptly when people leave.
6. Use escrow when trading with people you do not know.
7. Report anything suspicious to Paysasa support straight away.

Security checklist for businesses

• Turn on every available verification step for payouts.
• Separate duties: the person who prepares payouts should not be the only one who approves them.
• Review the audit trail and transaction history weekly.
• Keep API keys in environment variables and rotate them if you suspect exposure.
• Verify every webhook signature before acting on it.

If something goes wrong

• Open Disputes in your dashboard if a payment looks wrong.
• Change your PIN and password and log out of other devices if you suspect compromise.
• Contact support through paysasa.com/contact.

Conclusion

Security on Paysasa is layered: account protection, verification, holds, signed requests, careful settlement rules, access control and human review. Combined with your own good habits, these controls help keep every payment accounted for.

Want to learn more? Read the Paysasa security page or create your account and set up your PIN and devices today.