[skip ci] Updates

Author: concur-docs-machine

api-reference/detokenizer/v5.detokenizer-get-started.html

@@ -1295,14 +1295,15 @@
 
         <h1 id="detokenizer-v5">Detokenizer v5</h1>
 
-<p>The Detokenizer API allows clients to retrieve the user’s credit card number from Concur Expense in a secure way. It returns the user’s credit card number encrypted with a symmetric key that the client provides in the request. The client will be able to decrypt the user’s credit card number using their symmetric key. The detokenizer V5 version is FIPS compliant so that customers with IBCP card programs can benefit with credit card detokenizer functionality in CCPS environment. This API 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>The Detokenizer v5 API allows clients to retrieve the user’s credit card number from Concur Expense in a secure way. It returns the user’s credit card number encrypted with a symmetric key that the client provides in the request. The client will be able to decrypt the user’s credit card number using their symmetric key. The Detokenizer v5 API is FIPS compliant so that customers with IBCP card programs can benefit with credit card detokenizer functionality in CCPS environment. This API 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>
 
 <h2 id="authentication"><a name="authentication"></a>Authentication</h2>
+
 <p>Authentication is done via company JWT with required scope <code class="language-plaintext highlighter-rouge">creditcardaccount.read</code>. The company JWT refers to the token belonging to the company whose data is being accessed. If a company is accessing data on behalf of another company, then the calling company should invoke the detokenizer API using the JWT of the company that owns the card data. For example, if a company XYZ wants to call the detokenizer API on behalf of another company ABC, then the company XYZ should access the API using ABC’s company JWT.</p>
 
 <h2 id="overview"><a name="overview"></a>Overview</h2>
 
-<p>The detokenizer v5 API exposes the following resources and these have to be called sequentially:</p>
+<p>The Detokenizer v5 API exposes the following resources and these have to be called sequentially:</p>
 
 <table>
   <thead>
@@ -1325,9 +1326,7 @@ <h2 id="overview"><a name="overview"></a>Overview</h2>
 
 <h2 id="limitations"><a name="limitations"></a>Limitations</h2>
 
-<ul>
-  <li>Access to this documentation does not provide access to the API.</li>
-</ul>
+<p>Access to this documentation does not provide access to the API.</p>
 
 <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>
 

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>Thu, 26 Feb 2026 17:35:30 +0000</pubDate>
-    <lastBuildDate>Thu, 26 Feb 2026 17:35:30 +0000</lastBuildDate>
+    <pubDate>Thu, 26 Feb 2026 18:01:51 +0000</pubDate>
+    <lastBuildDate>Thu, 26 Feb 2026 18:01:51 +0000</lastBuildDate>
     <generator>Jekyll v4.1.1</generator>
 
   </channel>