diff --git a/.github/workflows/create-gh-pages.yml b/.github/workflows/create-gh-pages.yml
index fd586d0..3200662 100644
--- a/.github/workflows/create-gh-pages.yml
+++ b/.github/workflows/create-gh-pages.yml
@@ -10,10 +10,16 @@ jobs:
       - name: Check out repository code
         uses: actions/checkout@v4
 
-      - name: build pages
+      - name: Check out old gh pages
+        uses: actions/checkout@v4
+        with:
+            ref: gh-pages
+            path: _gh_pages
+
+      - name: build new version page
         run: libs/GitHubPagesGenerator.exe -i "${{ github.workspace }}" -s "${{ github.workspace }}/Sitemap.json" -c "${{ github.workspace }}" -o _gh_pages -t "JSON API Spec-Version 1.38"
       
-      - name: push
+      - name: push updated gh pages
         uses: s0/git-publish-subdir-action@develop
         env:
           REPO: self
diff --git a/.travis.yml b/.travis.yml
deleted file mode 100644
index bfaf8cc..0000000
--- a/.travis.yml
+++ /dev/null
@@ -1,24 +0,0 @@
-branches:
-    only:
-    - master
-language: csharp
-script: |
-    cd "$TRAVIS_BUILD_DIR"
-    #
-    # clone + update
-    #
-    git clone -b gh-pages "https://github.com/saferpay/jsonapi.git" _gh_pages
-    cp -r assets/* _gh_pages/assets
-    mono libs/GitHubPagesGenerator.exe -i "$TRAVIS_BUILD_DIR" -s "$TRAVIS_BUILD_DIR/Sitemap.json" -c "$TRAVIS_BUILD_DIR" -o _gh_pages -t "JSON API Spec-Version 1.38"  || travis_terminate 1
-    cd _gh_pages
-    #
-    # show result
-    #
-    ls
-    #
-    # commit + push changes
-    #
-    git add -v --all .
-    git -c user.name='Saferpay-DevOps' -c user.email='travis' commit -m "Updated Github pages"
-    git push -f -q https://Saferpay-DevOps:${GITHUB_API_KEY}@github.com/saferpay/jsonapi.git gh-pages || travis_terminate 1
-    cd "$TRAVIS_BUILD_DIR"
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>