Introduction

Modern payment systems often handle massive volumes of transaction requests. Among those requests, there may be duplicates or multiple submissions triggered by user interface glitches, network issues, or user impatience—leading customers to click the same button multiple times. Such redundancies can result in incorrect or excessive charges, accounting discrepancies, and a host of related problems.

Our Antispam system is designed specifically to identify and minimize the impact of duplicate transaction requests. By preventing the processing of repetitive or invalid submissions, Antispam ensures efficient traffic handling and mitigates the negative effects caused by redundant or improper data. This functionality is crucial in payment intake scenarios, where operational accuracy and conversion rates need to be maintained at all times.

Why payment systems need Antispam services

• Prevent fraud and disputes: Duplicate or incorrect submissions can lead to unauthorized or accidental transactions, resulting in disputes or chargebacks. Antispam helps filter out these problematic requests so that only valid payments proceed.
• Maintain data integrity: When multiple transactions are processed for the same payment details, it can distort revenue, hamper financial reconciliation, and complicate bookkeeping. Antispam enforces consistency and prevents these inaccuracies.
• Optimize system resources: Duplicate requests can unnecessarily consume server bandwidth and processing power. By stopping redundant transactions at the source, you reduce overhead and enable your system to handle genuine traffic more efficiently.
• Improve user experience: Errors and confusions stemming from repeated payments can frustrate end users. An Antispam mechanism ensures that each legitimate payment is processed promptly and accurately, leading to higher user satisfaction.

Problems Antispam solves

• Excessive or multiple charges: Without proper safeguards, customers might be charged multiple times if they unknowingly submit several identical payment requests.
• Revenue loss from cancellations: Multiple open transactions for the same item or service can lead to cancellations and refunds, creating an administrative burden and possible revenue leakage.
• Operational inefficiency: Teams may spend valuable time dealing with duplicate orders, verifying the authenticity of transactions, and reconciling financial inconsistencies instead of focusing on core business operations.
• Erosion of trust: A rash of duplicate payments can damage a platform’s reputation, making customers less willing to transact. Antispam supports a trustworthy environment by minimizing errors and fraudulent activity.

How Antispam works

The Antispam system identifies spam requests based on the following criteria:

• A clientId is included in the transaction request.
• There is an existing active request with the same clientId and amount that is not in a final status.

When such duplicate requests are detected:

1. They are grouped into a chain of related requests.
2. Older requests in the chain are automatically closed and marked as canceled.
3. The latest request in the chain retains the same account details as the previous requests.

Integration best practices

• Unique identifiers: Use a unique clientId for each client. This could be an anonymized string, such as a hash of the client’s email or login ID.
• Avoiding incorrect IDs: Providing an incorrect or non-unique clientId can result in multiple clients receiving the same account details, leading to disputes.
• Widget integration: If you cannot provide a clientId, use our widget for integration. The widget applies automatic client tagging based on external attributes to prevent spam submissions.