Transaction Fetch Behavior
The 24-hour fetch window mentioned in the documentation applies to the normal transaction flow (Scenario 1), where the POS sends the transaction response back through Client.
In this scenario, the client can fetch the transaction within the supported time window (up to 24 hours).
Fallback Fetch Flow (Scenario 2)
A second scenario was introduced as a fallback mechanism, supported starting from POS version 3.0.42.
This flow is used only when the POS does not send the transaction response through client for a successful transaction.
In this case:
In Scenario 2, the transaction must be fetched before the batch is settled on the processor side.
This fallback flow works only while the batch is still open. Once the batch is closed/settled, the processor will no longer allow the transaction to be fetched, even if the request is within the 24-hour window.
So in this scenario, the client should make sure to send the fetch request as soon as possible after the transaction, and before batch settlement.
Important Notes
- Scenario 2 is triggered only when the POS response is missing.
- The 24-hour fetch rule does not always apply in the fallback scenario.
- The ability to fetch the transaction depends on switch behavior and batch status.
- This behavior is supported only in POS version 3.0.42 and later.