Unified Checkout Capture Context Error

[ffraticelli]

We're getting this error trying to get the Unified Checkout Context.
Error: Profiles API error 400 when attempted to retrieve profile
Tested in Cybersource Unified Checkout Capture Context Test Request 

We enabled Unified Checkout in the business center and generated Rest Shared-Secret Key.

Completed the fields with our organization ID and the REST Shared - Secret Key

This is how the error appears

[RobertJoseph00]

This error often indicates an issue with the configuration or the provided credentials. A few steps to verify:

1. Organization ID and Shared Secret Key: Double-check that the Organization ID and REST Shared-Secret Key are correct and correspond to the account configured in the Cybersource Business Center. Ensure there are no extra spaces or formatting issues when copying these values.

2. API Key Settings: Verify in the Business Center that the generated REST Shared-Secret Key is active and matches the sandbox environment settings.

3. HTTP Signature Authentication: From the screenshot, it looks like you're using the "HTTP Signature" authentication type. Ensure all required fields (Organization ID, Key, and Shared Secret Key) are filled correctly.

4. Testing in the Right Environment: If testing in the sandbox, confirm that your keys are specific to the sandbox environment and not the production environment.

5. Profiles API Configuration: The error message suggests an issue with the Profiles API. Check that Unified Checkout is fully enabled and configured in the Business Center for your account.

If these steps don't resolve the issue, it may be worth contacting Cybersource support for further assistance. They can help review your account and configuration in more detail.

[DrewAnderson]

It seems like you're facing a "Profiles API error 400" when retrieving the Unified Checkout Context. This usually points to an issue with the request format or authentication. Double-check that your organization ID and REST Shared-Secret Key are correct. Also, ensure the API endpoint URL is accurate. If the issue continues, try regenerating the Shared-Secret Key and reviewing the API logs for more details.

[ffraticelli]

Thanks!