The Tuum CMS offers two distinct modes for managing unmatched clearings, which are configured by a system property named PROCESS_NON_MATCH_CLEARINGS. This property determines whether unmatched clearing transactions are completed automatically or require manual processing.
The configuration can be defined using system property settings. To do this, follow these steps:
Go to Administration > Settings > System properties.
From the content menu, choose Card to open the System property (card-api) page.
On the card-api page, find the setting Process non-match clearings automatically and click Edit.
The Update system property modal opens with prefilled parameters.
You can select Yes (to enable) or No (to disable) from the drop-down list to configure automatic processing of non-match clearings in the Card API.
The two configurable values and their descriptions are as follows:
PROCESS_NON_MATCH_CLEARINGS
true
A clearing transaction is automatically completed even when an authorisation match is not found.
PROCESS_NON_MATCH_CLEARINGS
false
A clearing transaction is not completed automatically if an authorisation match is not found.
Click Save to apply your changes.
When the system is configured with PROCESS_NON_MATCH_CLEARINGS = false, unmatched clearings must be manually reviewed and completed.
If no authorisation match is found, the clearing transaction status is set to Processed (PROCESSED). It will not be completed automatically and remains in this state awaiting manual intervention. Once the transaction is manually completed, its status is updated to Completed (C), the related account transaction is created, and the reservation, if exists, is released. This action creates a formal link between the authorisation and clearing records within the system, ensuring data integrity for audit and dispute resolution purposes.
While automatic processing is faster, some situations call for manual review:
Better control: Manual checks help catch errors, especially for big or sensitive transactions.
Clear audit trail: Having a human review creates a record that’s useful for compliance and audits.
Handling exceptions: Some transactions don’t fit standard rules and need a closer look.
Avoiding disputes: Manual matching helps prevent mistakes that could upset customers and resolves existing issues more easily.
When the system is configured with PROCESS_NON_MATCH_CLEARINGS = true, it operates in automated mode for unmatched clearings.
If a clearing transaction cannot be matched to an authorisation using the card number and approval code, it is still processed automatically. An account transaction is created, the clearing transaction's status is marked as Completed (C). No manual processing is needed, and this logic also supports processing of offline transactions where needed.
However, if a reservation exists for the unmatched authorisation, it is not released automatically unless further configuration is applied. By default, such reservations remain in place indefinitely.
To address this, the system provides an option to automatically release reservations after a defined number of days. This period, known as the reservation tolerance period, can be configured within the CMS as needed for each specific scheme and product class. The exact property name and default value may vary depending on your Tuum system setup. If configured, unmatched reservations will be released automatically after the specified time. The expiry period should be set based on typical transaction timelines and business risk considerations.
In addition to automated handling, the CMS supports manual linking of a clearing transaction to its original authorisation. When this is done, the system updates the database to bind the two records. This action also triggers the immediate release of the associated reservation, completing the reconciliation process.