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!
06-15-2026 10:10 AM