No guessing about payments
When a payment’s result is unclear, it stays “still confirming” until the payment provider answers. We don’t mark it failed, and we never send a second charge on our own.
Security
How we protect payments.
What PerionPayments does to keep your payments, your records and your customers’ details safe, and how to tell us about a security problem.
Six safeguards
Ask us about any of these.
Records that stay honest
Payments, refunds and settlements keep separate histories. Mistakes are fixed with new entries, never by editing old ones.
Access by role
Every merchant and staff action is checked against the person’s role and account. Sensitive actions are recorded with who did them and why, and most need a second person’s approval.
Where customers enter payment details
Card details go only to the card acquirer’s secure page; EcoCash approvals happen on the customer’s own phone. Never send card numbers, passwords or one-time codes by email, including to us.
Problems get noticed
Monitoring flags payments and settlements that need a closer look, so our team can look into them quickly.
We know what we release
Every release is versioned and checked before it goes live, so we always know what’s running.
Found a security problem?
Tell us privately.
Email security@perionpayments.com. Stop before you reach anyone else’s data, move money or slow the service down.
Document status
This page describes how we work today. It isn’t a certification: our design and internal tests don’t replace PCI certification, regulatory approval or an independent penetration test. Ask us for the current review scope before you rely on an assurance claim.
- Where it applies
- Live payments (EcoCash, Visa & Mastercard and ZimSwitch) are currently limited to approved internal pilot merchants. Card details are entered only on the card acquirer’s own secure page. External live processing has not opened.
- Security reporting
- Covered by the security reporting guidance, version 1.1.