On This Page

API Differences

This topic outlines the key differences between Secure Acceptance and Unified Checkout APIs.

Endpoint Changes

API Endpoint Comparison
`Secure Acceptance`	`Unified Checkout`
https://secureacceptance.cybersource.com/pay	`https://api.cybersource.com`/uc/v1/sessions
https://secureacceptance.cybersource.com/token/create	`https://api.cybersource.com`/uc/v1/sessions

Request/Response Format Changes

Secure Acceptance:

Uses form-encoded data for requests.

Responses are typically in HTML or form-encoded format.

Unified Checkout:

Uses JSON for both requests and responses.

Supports more detailed response structures.

Authentication Method Changes

Secure Acceptance:

Uses a combination of profile ID, access key, and secret key.

Requires signing requests with HMAC.

Unified Checkout:

Unified Checkout uses Cybersource REST HTTP signature authentication. With REST HTTP signature authentication, requests sent to the

sessions

API and other APIs are signed using merchant REST credentials. For information configuring REST HTTP signature authentication, see Set Up an HTTP Signature Message
in the Getting Started with REST Developer Guide.

Requires obtaining an access token before making API calls.