Skip to content

Security

Report a security problem.

Noticed a security problem while using PerionPayments? Tell us privately, and stop before it affects anyone else.

This opens your email app. The same address is listed in our security.txt file.

How to report

Three steps.

  1. Report privately

    Email security@perionpayments.com, the address listed in our security.txt file.

  2. Send only what’s needed

    Include the page address, what you saw during normal use and the time (CAT or UTC). Say if you haven’t reproduced it. Leave out passwords, card details and anyone’s personal details.

  3. Hear back from us

    We aim to acknowledge your report within 1 business day, then keep you updated while we look into it.

Before you do anything else

Good-faith boundary

This page is a way to report problems. It doesn’t give permission to test our systems.

Stop and report if you

  • reach another person’s data or another merchant’s account;
  • could move money, send a payment prompt to a customer, change a record or slow the service down;
  • come across a password, key or live data. Keep only the smallest redacted proof.

Not allowed without written permission

  • Probing, automated scanning, social engineering or denial-of-service testing
  • Testing systems that belong to other companies
  • Going beyond your own normal use, or trying to get around our controls

Ask for written permission at security@perionpayments.com before doing anything beyond normal use. This guidance gives no testing permission and no legal safe harbor, and there is no paid bounty.

Response targets

When to expect a reply.

Acknowledgement
1 business day
Initial triage
3 business days
Progress update
Every 5 business days

These are targets for keeping you informed, not a promise to fix a problem by a set date. How and when a fix ships depends on how serious the problem is and how it can be deployed safely.

Document status

Reporting guidance only. Testing permission and legal safe harbor are not approved, and formal legal review is pending.

Version
1.1
In effect from
24 Sep 2026
Review due
1 Nov 2026