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?

hunzafatimaa — Tue, 16 Jun 2026 10:17:33 GMT

Yes, JWT authentication is now supported for Cybersource's REST APIs, including Unified Checkout, and is the recommended authentication method going forward.

If your proof of concept was built earlier using HTTP Signature because JWT support wasn't fully available, it's worth revisiting the implementation. Cybersource has been moving customers toward JWT/OAuth-based authentication for REST integrations, while HTTP Signature remains primarily for backward compatibility with existing implementations.

A few points to verify before starting production work:

* Confirm that your specific Unified Checkout APIs support JWT in both the sandbox and production environments for your merchant configuration.
* Ensure you have the necessary JWT/OAuth credentials provisioned in the Cybersource Business Center.
* Review the latest authentication documentation, as some services may have slightly different requirements depending on the API family.
* Test token generation, expiration handling, and refresh workflows in the sandbox before migrating away from HTTP Signature.

As for a formal timeline, Cybersource typically publishes authentication and deprecation updates through its official documentation and support channels. If you're planning a production rollout, I'd recommend opening a support ticket with Cybersource to confirm the current status for your account and whether there are any remaining limitations for Unified Checkout specifically.

In general, for new development, JWT is the preferred approach and should be the direction you target unless Cybersource support advises otherwise for your particular integration.

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