Warranty against duplicate charges.

How payments would be protected

• Only one attempt with the payment provider at a time for each payment.
• Each attempt carries a stable reference, so a repeated request can’t create a new charge.
• Payment provider notices, status checks, and file and bank records settle a payment’s result in a fixed order of priority.
• A late or repeated notice for the same payment can’t create a second charge record or a second success.
• Every correction to money is a reversal plus a replacement, never a rewrite of history.

If PerionPayments causes a confirmed duplicate

Once payment provider or bank records confirm both charges, and the duplicate is shown to be caused by the PerionPayments platform, the proposed remedy is to reverse the duplicate amount and cover the duplicate-processing fees those records show. Timing, exclusions, the claim window and the governing terms still need legal sign-off.

We still look into these cases, but don’t treat them as a PerionPayments duplicate from the start: a customer paying twice themselves, a second payment created by the merchant, a duplicate made only on the provider’s side outside PerionPayments’ records, or an unverified screenshot of a statement.

How a claim would be decided

1. Find both payments’ references and the matching payment provider or bank references.
2. Compare the payment, each attempt and their histories.
3. Rebuild the records to show whether one charge or two really happened.
4. Publish the outcome and apply the approved remedy, never based only on what a browser showed.