topic Re: Is JWT now fully supported for the Unified Checkout REST implementation? in cybersource APIs

Is JWT now fully supported for the Unified Checkout REST implementation?

timfoster — Mon, 15 Jun 2026 17:10:34 GMT

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. 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.

As we're now looking to begin the production work, is anyone able to confirm whether this is now resolved? Does Cybersource now fully support the recommended REST/JWT approach in their test and production environments? If not, is there a formal timeline for this?

Appreciate any insight!

Re: Is JWT now fully supported for the Unified Checkout REST implementation?

timfoster — Tue, 16 Jun 2026 13:37:56 GMT

Thank you very much for the thoughtful response -- much appreciated! I'm just now reviewing/digesting the POC code and current production implementation (it's all still pretty new to me) but I at least wanted to make sure we're headed down the right path... I'll surely heed your advice, very very helpful!!!

Re: Is JWT now fully supported for the Unified Checkout REST implementation?

WilliamsWelsh — Thu, 16 Jul 2026 12:11:52 GMT

If Cybersource is now recommending JWT for Unified Checkout, it would be helpful if someone from the team could confirm whether it's fully supported in both the sandbox and production environments. Clear guidance on migration from the legacy HTTP Signature approach—including any known limitations or best practices—would save developers a lot of trial and error. With HTTP Signature being phased out, having confidence in the JWT implementation is becoming increasingly important.