CyberSource

CyberSource has some special integration requirements. Follow the standard PaymentsOS integration procedure, and then apply the relevant extra specifications described below.

Note

The features 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.

Specifications for Card-based Transactions

The following table lists the integration specifications for CyberSource.

SpecificationsDetails
Minimum PaymentsOS API Version1.0.0
Requests
  • Authorize (including partial)
  • Capture (including multiple/partial)
  • Charge
  • Refund (including multiple/partial)
  • Void. Void after capture on the same day is supported (before the nightly batch).
Limitations:
  • Support for multiple/partial Capture depends on the specific provider.
  • Support for multiple/partial Refund depends on the specific provider.
CurrenciesCyberSource supports many currencies, but not all currencies are supported by all providers. Contact CyberSource support for provider-specific currency details.
Payment MethodsContact CyberSource support for provider-specific details.
3DS RedirectionNot supported

Configurations

The following table lists the configurations that are specific to CyberSource.

ConfigurationRequired/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.
  • reportingUserName: User name of the CyberSource Business Center user with a 'Report download' role.
  • reportingUserPassword: Password of the CyberSource Business Center user with a 'Report download' role.
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

Sample Requests

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

Summary of the 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.

results matching ""

    No results matching ""