Silent mode is a feature designed to enhance the anti-fraud capabilities for merchants by allowing them to configure certain anti-fraud services to operate in a “silent” mode. This means that while these services still process transactions, their results are not immediately exposed to the merchant, allowing for a more streamlined transaction experience.
Warm up a new service: This enables the new service to gather data and adjust its machine learning models without impacting transaction processing.
Test a new service: Merchants can validate the performance of a new service before fully transitioning to it, ensuring it does not reject a high volume of transactions.
Configuration of silent services: Merchants can configure specific anti-fraud services as silent, enabling them to send decision requests and transaction updates without immediate visibility into the results.
Asynchronous processing: All HTTP requests to silent services are handled asynchronously, ensuring that the transaction process is not delayed by waiting for responses from these services.
Transaction history events: Although silent services do not expose their results directly, transaction history events are still created to maintain a record of the checks performed.
When a transaction is initiated, anti-fraud checks are created for both active and silent services. The primary anti-fraud service is called synchronously to get an immediate decision. For silent services, messages are enqueued to call these services asynchronously. This means that while the primary service’s decision is processed, the silent services continue to operate in the background.
If a webhook is triggered for a silent service, the system fetches the associated anti-fraud check and updates it, but takes no action on the transaction if it is not the primary check.
While the results of silent services are not displayed directly in the transaction API, the transaction history includes entries related to these checks to ensure transparency and record-keeping.
