From dae2249a7413ffa2035b10ea0fe38b6170fba4ee Mon Sep 17 00:00:00 2001
From: Fabien Peter <fabien.peter@six-group.com>
Date: Fri, 12 Jan 2024 12:47:28 +0100
Subject: [PATCH] update v1.38

---
 texts/ChapterPaymentPage.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/texts/ChapterPaymentPage.md b/texts/ChapterPaymentPage.md
index bc426b7..218a430 100644
--- a/texts/ChapterPaymentPage.md
+++ b/texts/ChapterPaymentPage.md
@@ -481,7 +481,7 @@ Call this function to safely check the status of the transaction from your serve
 <p><strong>Important:</strong></p>
 <ul>
 <li>Depending on the payment provider, the resulting transaction may either be an authorization or may already be captured (meaning the financial flow was already triggered). This will be visible in the status of the transaction container returned in the response.</li>
-<li>This function can be called up to 24 hours after the transaction was initialized.</li>
+<li>This function can be called up to 24 hours after the transaction was initialized. For pending transaction the token expiration is increased to 96 hours.</li>
 <li>If the transaction failed (the payer was redirected to the Fail url or he manipulated the return url), an error response with an http status code 400 or higher containing an error message will be returned providing some information on the transaction failure.</li>
 </ul>
 </div>