<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Is JWT now fully supported for the Unified Checkout REST implementation? in cybersource APIs</title>
    <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Is-JWT-now-fully-supported-for-the-Unified-Checkout-REST/m-p/95406#M4255</link>
    <description>&lt;P&gt;Earlier this year, we developed a quick proof-of-concept application to get a feel for converting our legacy Cybersource implementation to the new REST-based Unified Checkout system.&amp;nbsp; At the time of this initial effort, JWT authentication wasn't yet testable and ready to go on Cybersource's side -- so we built it out using the deprecated HTTP Signature approach.&lt;/P&gt;&lt;P&gt;As we're now looking to begin the production work, is anyone able to confirm whether this is now resolved?&amp;nbsp; &amp;nbsp;Does Cybersource now fully support the recommended REST/JWT approach in their test and production environments?&amp;nbsp; If not, is there a formal timeline for this?&lt;/P&gt;&lt;P&gt;Appreciate any insight!&lt;/P&gt;</description>
    <pubDate>Mon, 15 Jun 2026 17:10:34 GMT</pubDate>
    <dc:creator>timfoster</dc:creator>
    <dc:date>2026-06-15T17:10:34Z</dc:date>
    <item>
      <title>Is JWT now fully supported for the Unified Checkout REST implementation?</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Is-JWT-now-fully-supported-for-the-Unified-Checkout-REST/m-p/95406#M4255</link>
      <description>&lt;P&gt;Earlier this year, we developed a quick proof-of-concept application to get a feel for converting our legacy Cybersource implementation to the new REST-based Unified Checkout system.&amp;nbsp; At the time of this initial effort, JWT authentication wasn't yet testable and ready to go on Cybersource's side -- so we built it out using the deprecated HTTP Signature approach.&lt;/P&gt;&lt;P&gt;As we're now looking to begin the production work, is anyone able to confirm whether this is now resolved?&amp;nbsp; &amp;nbsp;Does Cybersource now fully support the recommended REST/JWT approach in their test and production environments?&amp;nbsp; If not, is there a formal timeline for this?&lt;/P&gt;&lt;P&gt;Appreciate any insight!&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jun 2026 17:10:34 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/Is-JWT-now-fully-supported-for-the-Unified-Checkout-REST/m-p/95406#M4255</guid>
      <dc:creator>timfoster</dc:creator>
      <dc:date>2026-06-15T17:10:34Z</dc:date>
    </item>
  </channel>
</rss>

