[skip ci] Updates

Author: concur-docs-machine

feed.xml

@@ -5,8 +5,8 @@
     <description>Concur docs provides comprehensive information on working with the Concur platform</description>
     <link>https://preview.developer.concur.com/</link>
     <atom:link href="https://preview.developer.concur.com/feed.xml" rel="self" type="application/rss+xml" />
-    <pubDate>Wed, 25 Feb 2026 20:57:24 +0000</pubDate>
-    <lastBuildDate>Wed, 25 Feb 2026 20:57:24 +0000</lastBuildDate>
+    <pubDate>Wed, 25 Feb 2026 22:03:04 +0000</pubDate>
+    <lastBuildDate>Wed, 25 Feb 2026 22:03:04 +0000</lastBuildDate>
     <generator>Jekyll v4.1.1</generator>
 
   </channel>

tools-support/release-notes/api/2026-02-04.html

@@ -428,11 +428,13 @@ <h2 id="new-this-month">New This Month</h2>
 <h3 id="now-available-detokenizer-dtk-v5">Now Available: Detokenizer (DTK) v5</h3>
 <p>The FIPS Compliant v5 Credit Card Detokenization API will be set to launch within the CCPS environment for IBCP customers. This compliance-driven initiative aligns with the Federal Information Processor Standards (FIPS) to ensure robust protection of sensitive data, per U.S. federal requirements. For customers with entities in CCPS and IBCP card programs, the Detokenizer (DTK) functionality will be integral to the payment file process.</p>
 
-<p><strong>Overview</strong>
-The Detokenizer service ensures secure transmission of sensitive data (card number) to customers as part of the remittance file creation process running at caller applications like ICS and CWS, in which the full, unmasked credit card number is required for the correct application of payments.</p>
+<p><strong>Overview</strong></p>
 
-<p><strong>API Details</strong>
-The Detokenizer v5 API exposes the following resources and these must be called sequentially:</p>
+<p>The Detokenizer service ensures secure transmission of sensitive data (card number) to customers as part of the remittance file creation process running at caller applications like ICS and CWS, in which the full, unmasked credit card number is required for the correct application of payments.</p>
+
+<p><strong>API Details</strong></p>
+
+<p>The Detokenizer v5 API exposes the following resources and these must be called sequentially:</p>
 
 <table>
   <thead>
@@ -453,7 +455,15 @@ <h3 id="now-available-detokenizer-dtk-v5">Now Available: Detokenizer (DTK) v5</h
   </tbody>
 </table>
 
-<p>The first DTK v5 API will return the RSA public key and version of the RSA public key. The caller needs to wrap their symmetric key using this public key and this wrapped symmetric key needs to be passed to the second DTK v5 API along with the version earlier mentioned, and the mandatory credit card GUID received from client request to provide encrypted credit card account number.</p>
+<p>The first resource “RSAPublicKey” will return the RSA public key and version for the RSA public key. The caller needs to encrypt their symmetric key using this public key. This encrypted symmetric key and version needs to be passed to the “Credit Card Account Details” resource, along with the mandatory Credit Card GUID parameter to retrieve the encrypted credit card account number. The Credit Card GUID parameter can be retrieved from “cardAccountID” value available in the Financial Integration Service (FIS) payload.</p>
+
+<p><strong>Limitations</strong></p>
+
+<ul>
+  <li>Access to this documentation does not provide access to the API.</li>
+</ul>
+
+<p>This API is only for public use to support various SAP integration features or to the SAP Concur customer that has established corporate credit card accounts involved in the data (the “Customer Corporate Card Holder”). Such use must be in compliance with regulations and other industry standards, including but not limited to Payment Card Industry Data Security Standards (PCI DSS).</p>
 
 <h3 id="important-upcoming-shutdown-of-request-v1-v3-and-v31">Important! Upcoming Shutdown of Request V1, V3, and V3.1</h3>
 
@@ -513,8 +523,9 @@ <h3 id="preview-removal-of-concurprofile-and-concurapp-fields-from-access-tokens
   <li>Removal from Production environments — week of April 6</li>
 </ul>
 
-<p><strong>Required Action</strong>
-If your integration consumes either the <code class="language-plaintext highlighter-rouge">concur.profile</code> or <code class="language-plaintext highlighter-rouge">concur.app</code> fields from a JWT, update your implementation to remove this dependency by forming the necessary URL directly in your code.</p>
+<p><strong>Required Action</strong></p>
+
+<p>If your integration consumes either the <code class="language-plaintext highlighter-rouge">concur.profile</code> or <code class="language-plaintext highlighter-rouge">concur.app</code> fields from a JWT, update your implementation to remove this dependency by forming the necessary URL directly in your code.</p>
 
 <h2 id="previews">Previews</h2>