Skip to main content

Cybersource PCI

This page provides an overview of the payments methods provided by the Cybersource PCI adapter in the IXOPAY platform. It also includes a full list of all configuration options available to you when integrating Cybersource PCI within your payments landscape, as well as an overview of the parameters required when submitting a transaction via IXOPAY's API.

Payment Methods

Payment MethodTransaction FlowsTransaction Types
CreditcardPayment Form & payment.js IntegrationRegister, Deregister, Debit, Pre-authorise, Capture, Void, Refund

Adapter Config

The following fields are required depending on the used features:

ParameterAllowed valuesDescription
Use Decision Managerrequired if Cybersource Decision Manager is used.
Enable Incremental Authorizationrequired if Incremental Authorizations are used (check with Cybersource if it's available for you)

General Transaction extraData

The following extraData fields are required or optional for ALL transactions:

ParameterAllowed valuesDescription
extraData.purchaseLevel3required if LEVEL III Data is sent
extraData.purchaseOrderNumberadditional LEVEL III Data value

Capture Transactions

The following extraData fields are required for capture transactions:

ParameterAllowed valuesDescription
extraData.captureSequenceNumberThe Capture sequence number for multiple partial captures.
extraData.totalCaptureCountThe total amount of Captures that will be done.

Recurring Transactions

The following extraData fields are required for recurring transactions:

ParameterAllowed valuesDescription
extraData.recurringEndDaterequired - YYYY-MM-DD
extraData.recurringFrequencyrequired 28 days * Month - 6 month = 168
extraData.recurringOriginalPurchaseDateYYYY-MM-DDTHH:MM:SSZ - empty = currentDate
extraData.recurringSequenceNumberThis field is mandatory for Cartes Bancaires recurring transactions on Credit Mutuel-CIC - (1st, 2, 3, ..)
extraData.recurringType(1,2,3,4) => (Registration/First transaction, Subsequent transaction, Modification, Cancellation)
extraData.recurringOccurrence01-12 - see Cybsersource documentation for description of the values
extraData.recurringAmountType1 = Fixed amount, 2 = Recurring with maximum amount
extraData.recurringMaximumAmountMaximum amount. Refer to Cybersource documentation.

Debit/Authorization/Incremental Authorization Transactions

The following extraData fields are optional for these transaction types:

ParameterAllowed valuesDescription
extraData.MITReasonMerchant initiated Transaction reason.
extraData.originalAmountOriginal amount of the preauthorize.

Decision Manager

The following extraData fields are necessary or optional for the Cybersource Decision Manager (Please refer to the Cybersource Documentation for the possible values and the requirements):

ParameterAllowed valuesDescription
extraData.useDecisionManagertrueRequired if DM is used. Send true if you want to send the decision manager data to cybersource.
extraData.dm_profileDecision manager profile name not needed if default profile is used.
extraData.dm_lastChangeDatelast change of account data
extraData.dm_creationHistoryGUEST, NEW_ACCOUNT, EXISTING_ACCOUNT
extraData.dm_createDateIF EXISTING_ACCOUNT = creation Date
extraData.dm_pwChangeDateIF PASSWORD_CHANGED_PAST = change Date
extraData.dm_firstUseOfShippingAddressIF not GUEST = true/false
extraData.dm_shippingAddressUsageDateCurrent date if not GUEST and firstUseOfShippingAddress is false
extraData.dm_accountPurchasesNumber of Purchases
extraData.dm_addCardAttemptsNumber of add card attempts in last 24 hours.
extraData.dm_suspiciousActivitiesIndicates previous suspicious activities recogniced by the merchant.
extraData.dm_paymentAccountDateIF PAYMENT_ACCOUNT_EXISTS add date
extraData.dm_transactionCountDayNumber of transactions in last 24 hours. (Success & abandoned)
extraData.dm_transactionCountYearNumber of transactions in the last year. (Success & abandoned)
extraData.dm_auxiliaryDataList of Key value pairs. E.g key1=value1&key2=value2