For more information about this gateway, please refer to
- Gateway type code:
cyber_source_direct
- Production API endpoint: https://ics2wsa.ic3.com/commerce/1.x/transactionProcessor
- Sandbox API endpoint: https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor
- Supported payment types: Credit Card, Gateway payment method token
- Supported operations: Authorization, Capture, Charge, Void, Refund
To add a CyberSource Direct gateway, use the following settings:
{
"merchant_id" : "(required) Merchant ID provided by CyberSource",
"username" : "(required) The Cybersource Merchant ID also goes in the Username field.",
"transaction_key" : "(required) In the codebase this is referred to as the Transaction Key. In the Cybersource admin portal it is the SOAP Toolkit key",
"subsequent_auth_transactionid" : "(optional) Configuration field to be sent with each transaction (AuthTransactionId)",
"ignoreAvsResult" : true ((optional) Boolean. Ignore avs result indicator. Default = false),
"ignoreCvvResult" : true ((optional) Boolean. Ignore cvv result indicator. Default = false)
}
Gateway Specific Fields
"gatewaySpecificFields":{
"cyber_source_direct": {
"order_id": "Defines the value sent to CyberSource in the merchantReferenceCode field (if not provided, the value from the merchantTransactionId field is used)",
"subsequentAuthTransactionId": "will override the configuration value. This allows to customize what is sent in the field (AuthTransactionId) for each transaction"
}
}
Gateway Specific Response Fields
A response from Cyber Source Direct gateway may contain the following fields: requestedAmount
, availableAmount
Which you can find in the gateway_specific_response_fields
. For example, a transaction could have something like this:
"gatewaySpecificResponseFields": {
"cyber_source_direct": {
"requestedAmount": "Amount requested by an Auth transaction",
"availableAmount": "Response from CyberSource about the amount available for authrization"
}
}