CyberSource (deprecated)

Deprecation Notice

While current integrations with this provider will continue to be maintained, no new integrations will be possible.

Note

The specifications described below are supported by our platform, but some providers may only support a subset of these features. You can check the provider’s site for full details, or contact CyberSource support.

API Version

Minimum required API version: 1.1.0

Payment Methods

Payment Method	Payment Method Type
American Express	Cards
Aura	Cards
CartaSi	Cards
Carte Blanche	Cards
Carte Bleue	Cards
Dankort	Cards
DINERS	Cards
DISCOVER	Cards
Hipercard	Cards
JAL	Cards
JCB	Cards
MAESTRO	Cards
MAESTRO UK	Cards
MASTERCARD	Cards
NICOS	Cards
ORICO	Cards
UATP	Cards
VISA	Cards

Currencies

CyberSource supports many currencies, but not all currencies are supported by all providers. Contact CyberSource support for provider-specific details.

Features

The following table provides an overview of all supported and non-supported features.

Feature	Supported
3DS 2.0 External	No
3DS 2.0 PaymentsOS-handled	No
3DS 2.0 Provider-handled	No
3DS 2.0 Self-handled	No
Installments	No
Level 2 and 3 Data	No
Multi-seller Payments	No
Network Tokens	No
Payment Facilitator	No
PayU Risk	No
Pre-authorization	No
Retrieve Supported Payment Methods	No
Retrieve Supported Plans	No
Statement Soft Descriptor	No
Stored Credentials Flag	No
Transaction Processing without CVV	No

Requests

The following table lists all supported requests for card-based transactions.

Use the bodybuilder to create a sample request body for each request type.

Request	Partial/Multiple	Mode	Notes
Authorize	Partial is supported	Synchronous
Capture	Both partial and multiple are supported	Synchronous	Support for multiple/partial capture depends on the specific provider.
Charge	Not Applicable	Synchronous
Refund	Both partial and multiple are supported	Synchronous	Support for multiple/partial refund depends on the specific provider.
Void	Not Applicable	Synchronous	Void after capture on the same day is supported (before the nightly batch).

Setup Procedures

The following table lists the setup procedures that are specific to this provider.

Configuration	Required/Optional
In the PaymentsOS Control Center, configure the following credentials: merchantID: The merchant ID or username provided by CyberSource. transactionSecurityKey: The transaction security key provided by CyberSource. See How to Generate a SOAP Toolkit API Security Key in the CyberSource documentation. sharedSecretKey: The shared secret key that you generated in your CyberSource account. publicKey: The public key that you generated in your CyberSource account. For help in generating the sharedSecretKey and publicKey, see Create a Shared Secret Key for HTTP Signature Authentication in the CyberSource documentation. To see your CyberSource credentials, login to either the CyberSource test or live environment and choose Account Management.	Required
In your CyberSource account, make sure that the CyberSource Relaxed Requirement mode setting is set to false (the default). This means that address data and expiration date fields are mandatory in requests. Contact CyberSource support for assistance. Note: Information in this guide is presented on the assumption that the Relaxed Requirement mode setting is set to false (if you need to operate with the Relaxed Requirement mode setting set to true, then contact PaymentsOS Support).	Required
In your CyberSource account, enable Partial Authorization if desired. Contact CyberSource support for assistance. Note: If Partial Authorization is enabled, then the `authorization.amount` can be different to the `payment.amount`.	Optional
In your CyberSource account, add specific external providers. Contact CyberSource support for assistance.	Optional

Optional Transaction Reconciliation fields

This is a summary of the optional fields that can be used for transaction reconciliation, in the authorization, capture, charge, refund, and void requests.

Attribute Name	Description	Usage	CyberSource Field Name
reconciliation_id	A unique ID that can be sent in a `post` authorization, charge, capture, or refund request. Not all providers support this field. Providers who do use it, will return it in response to an authorization, capture, charge, refund, or void request.	It can be used for transaction reconciliation.	Merchant Reference Number or Transaction Reference Number
provider_data.transaction_id	The ID of the transaction in the provider's system. It may be returned by the provider in response to an authorization, capture, charge, refund, or void request. Some providers set this field to the `reconciliation_id` value that was sent in the request. For other providers, CyberSource may generate the value for this field.	It can be used for reconciliation with the bank.	Transaction Reference Number
provider_data.external_id	The ID of the authorization or charge request in the provider's system. It may be returned by the provider in response to an authorization, capture, charge, refund, or void request.	It can be used to connect to the CyberSource Business Center.	Request ID

Testing

Use the test cards in the Testing Credit Card Services page to test authorization and capture requests.

You can simulate test responses as described in the CyberSource Testing page.

Last modified June 27, 2024