[skip ci] Updates

Author: concur-docs-machine

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

@@ -1302,10 +1302,10 @@
 
 <h1 id="detokenizer-v5">Detokenizer v5</h1>
 
-<p>The Detokenizer service allows clients to retrieve the user’s credit card number from Concur Expense in a secure way. The Detokenizer service 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. V5 version of detokenizer service is FIPS compliant so that customers with IBCP card programs, can benefit with credit card detokenizer functionality in CCPS environment. The Detokenizer 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 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 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>
 
 <h2 id="authentication"><a name="authentication"></a>Authentication</h2>
-<p>Authentication is done via company JWT with required scope creditcardaccount.read. The company JWT refers to the token belonging to the company whose data is being accessed. &lt;/br&gt;&lt;/br&gt; 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. <br /><br /> Ex: If a company XYZ wants to call detokenizer api on behalf of another company ABC, then the company XYZ should access the api using ABC’s company jwt.</p>
+<p>Authentication is done via company JWT with required scope ‘creditcardaccount.read’. 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>
 
@@ -1332,7 +1332,7 @@ <h2 id="overview"><a name="overview"></a>Overview</h2>
 
 <h2 id="limitations"><a name="limitations"></a>Limitations</h2>
 
-<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). Access to this documentation does not provide access to the API.&lt;/br&gt;&lt;/br&gt;
+<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). Access to this documentation does not provide access to the API.<br /><br />
 These APIs are available only in CCPS environment currently. Later, it will be available for other commercial environments also.</p>
 <h2 id="process-flow"><a name="process-flow"></a>Process Flow</h2>
 
@@ -1374,7 +1374,7 @@ <h2 id="access-token-usage-">Access Token Usage <a name="access-token-usage"></a
 
 <h2 id="get-rsa-public-key-detail"><a name="RSAPublicKeyDetail-get"></a>Get RSA Public Key Detail</h2>
 
-<p>Endpoint to retrieve RSA public Key. Returns RSA Public key for caller to consume the other V5 api i.e. Get Credit Card Account Details. This key would be used by caller to wrap their own symmetric key which would be passed to Get Credit Card Account Details api.</p>
+<p>Endpoint to retrieve RSA public Key. Returns RSA Public key for caller to consume the other V5 API i.e. Get Credit Card Account Details. This key would be used by caller to wrap their own symmetric key which would be passed to Get Credit Card Account Details API.</p>
 
 <h3 id="scopes">Scopes</h3>
 
@@ -1474,7 +1474,7 @@ <h2 id="get-credit-card-account-details-">Get Credit Card Account Details <a nam
 <h3 id="prerequisite">Prerequisite</h3>
 
 <ul>
-  <li>Publickey endpoint needs to be called and symmetricKey needs to be wrapped using same before making request to this api.</li>
+  <li>Publickey endpoint needs to be called and symmetricKey needs to be wrapped using same before making request to this API.</li>
 </ul>
 
 <h3 id="scopes-1">Scopes</h3>

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>Fri, 13 Jun 2025 20:36:25 +0000</pubDate>
-    <lastBuildDate>Fri, 13 Jun 2025 20:36:25 +0000</lastBuildDate>
+    <pubDate>Mon, 16 Jun 2025 16:25:50 +0000</pubDate>
+    <lastBuildDate>Mon, 16 Jun 2025 16:25:50 +0000</lastBuildDate>
     <generator>Jekyll v4.1.1</generator>
 
   </channel>