Trust

What you can rely on.

How PerionPayments keeps payments safe and records honest, the documents behind the service, and where to go when something goes wrong.

How we work

Built so nobody pays twice.

We never ask a customer to pay twice while a result is unknown, and keep every money record as an addition rather than an edit. Sensitive actions are recorded with who did them and why, and most need a second person’s approval.

How we protect payments

Get help

Start with the question you have.

For customersI need help with a payment or a refund.Get payment help For businessesI have a question about using PerionPayments.Talk to us For security researchersI found a security problem.Report it privately

Service notices: if something affects payments, merchants see a notice in their dashboard. Sign in to see them (merchant dashboard)

Public documents

The documents behind the service.

Your signed merchant agreement sets the terms for your business. These public documents explain everything else.

Website termsVersion 1.0 · 1 Aug 2026
Privacy noticeVersion 1.1 · 26 Sep 2026
Cookie and storage noticeVersion 1.1 · 26 Sep 2026
Complaints procedureVersion 1.1 · 24 Sep 2026
Security reportingVersion 1.1 · 24 Sep 2026
Duplicate-charge warrantyDraft
Merchant covenantDraft

Document status

Approval and review details for each public document. A review-due date is not a completed review, and the owner and date of the last completed review are not yet published for any document.

Website terms: Version 1.0, in effect from 1 Aug 2026. The contracting entity’s details are still to be published. Review due 1 Nov 2026.
Privacy notice: Version 1.1, in effect from 26 Sep 2026. The data controller’s details and the retention schedule are still to be published. Review due 1 Nov 2026.
Cookie and storage notice: Version 1.1, in effect from 26 Sep 2026. Approval status not stated. Review due 1 Nov 2026.
Complaints procedure: Version 1.1, in effect from 24 Sep 2026. Response times are pilot targets, not a regulatory service level. Review due 1 Nov 2026.
Security reporting: Version 1.1, in effect from 24 Sep 2026. Reporting guidance only: testing permission and legal safe harbor are not approved, and formal legal review is pending. Review due 1 Nov 2026.
Duplicate-charge warranty: Draft version 0.2, not in force and with no effective date. Needs legal approval and signed pilot terms. Review due 1 Nov 2026.
Merchant covenant: Draft version 0.2, not in force and with no effective date. Needs legal and regulatory review. Review due 1 Nov 2026.