Duplicate Transactions – FAQ

What is considered a duplicate transaction?

A transaction is flagged as a duplicate if it's submitted within the same time frame and matches the details of a recent transaction—whether through the Paynote UI or API. This helps prevent accidental double charges or repeated submissions..

How does Paynote prevent duplicate transactions?

Paynote uses two layers of protection:

1. UI-Level: Double-Click Protection
   To prevent accidental duplicates from double-clicking "Pay," Paynote checks if the transaction has the same:
   • Amount
   • Sender Email
   • Receiver Email
   • Sender Name
   • Recipient Name
   • Description

...was submitted within the last 30 seconds.

If yes, users will see this message:

       |_Please wait 30 seconds and try again.”_

2. UX-Server-Side: Backend Duplicate Detection
   If the UI check doesn’t catch it, the backend performs a second check using:
   • Sender Email
   • Amount
   • Description
   • Status (only “Pending” or “Processing” count)

Detection Timeframes:

• API Transactions: Flagged if submitted again within 3 minutes.
• UI Transactions Flagged if submitted again within 30 seconds.

What happens if a transaction is flagged as a duplicate?

It will be:

• Blocked from processing
• Marked with a “Duplicate” label in your transaction history.

This helps you quickly identify and avoid repeat payments.

Can I override or bypass the duplicate check?

No — to maintain security and accuracy, duplicate protection is enforced system-wide. If you believe a transaction was incorrectly flagged, please contact [email protected] for assistance.