PerionPayments
This document is a draft and is not in force.
Draft version 0.2 · no effective date.
Published 1 August 2026. Review due 1 November 2026. A completed review date and document owner are not published.
Legal and service owners must approve the complete wording, applicability and version history before this policy takes effect.
PerionPayments' payment machine is built so a timeout cannot authorize another debit. The engineering claim is proven internally. The contractual warranty below is not yet in force.
Publication requires named legal approval, live-rail admission, and pilot terms. Until then, this page describes the intended commitment and the evidence behind it.
After both debits are established by authoritative provider or bank evidence and the incident is attributable to PerionPayments' platform, the proposed pilot remedy is reversal of the duplicate amount and directly evidenced duplicate-processing fees. Timing, exclusions, claim window, and governing terms remain subject to legal sign-off.
A repeated payer action, merchant-created second intent, provider-only duplicate outside PerionPayments correlation, or unverified statement screenshot is investigated—but is not pre-labeled as a PerionPayments duplicate.
Locate both public payment IDs and provider/bank references.
Compare intent, attempt, idempotency, correlator, and evidence histories.
Rebuild journals and prove whether one or two authorized business events occurred.
Publish the incident outcome and apply the approved remedy—never infer it from browser state.