Recommended Guidelines & Best Practices

These recommendations will further enhance system reliability and operational efficiency.

1. Utilize the Get Transaction Status API:

Recommendation: If there is any uncertainty about whether a transaction succeeded (e.g., after a timeout or ambiguous response or no response), always use the Get Transaction Status API with the original ICTC number. This is the definitive way to ascertain the transaction's actual status on the IC platform.

User Interface Integration: Consider integrating the Get Transaction Status API functionality directly into your POS interface, allowing FLAs to instantly check transaction status and resolve ambiguities without escalating to support.

2. Pre-Fetching ICTC Numbers (Optional):

Recommendation: If the partner is in this model , partner systems may pre-fetch multiple ICTC numbers from IC and store them locally.

Caution: If adopting this approach, implement robust internal mechanisms to ensure:

Strict one-time use: Each pre-fetched ICTC is used exactly once.

Accurate tracking: A reliable method for marking ICTC numbers as used, assigned to a transaction, or discarded is in place.

Error handling: Mechanisms to manage pre-fetched ICTCs that are not ultimately used (e.g., due to transaction cancellation before submission). This prevents depletion of unique ICTC numbers unnecessarily.

3. Comprehensive Reconciliation:

Recommendation: Always perform reconciliation activities using both your locally stored transaction records and the reports provided by IC on a daily basis.