CyberSource

Contents of this Topic: ShowHide

Overview

• This topic describes the fields pertinent to a CyberSource payment account.

• SEOM supports the Simple Order API, not the SOAP API at the present time.

• You must be logged into the program with an administrator User ID to create or edit payment accounts.

• CyberSource can be used for Internet, Manual, or Point-of-Sale orders.

• If you are using CyberSource for Internet or Manual Orders, please review the CyberSource documentation to be sure that your account is prepared for Internet transactions before attempting to use it with SEOM and the Monsoon Commerce Payment Module (PM).

• For Internet orders it is necessary to have a MO/TO (Mail Order/Telephone Order) account or 'Card Not Present' account. The account must also be set up as "Terminal Batch Capture". The transactions are authorized and then settled. Settlements are batched and sent to the processor at the end of the day, so it is not possible to issue a credit against an order until the batch has been processed (up to 24 hrs later). Additional information about CyberSource can be found here.

• CyberSource does not support debit transactions.

• CyberSource settles transactions immediately, rather than in a batch mode.

• You must download and install the latest release of the Simple order API Client for ASP on all platforms (in the c:StoneEdge directory), which can be obtained from the Developer Download section of the CyberSource website. As of this writing, the most current version is 5.0.0. If you have a previous version installed, you must uninstall it and install a minimum of V5.0.0 in order to be PCI Payment Card Industry compliant. Older versions of this control may create a hidden system log file called "cybs.log" in the root directory of the C:\ drive on any workstation that processed credit card transactions through CyberSource. These logs contain full card account numbers and must be forensically removed in order to be PCI compliant. If system parameter UseLog is set to TRUE, the credit card numbers are masked with X's in V5.0.0 or higher.  

• For internet orders, check the settings of the main and/or cart-based system parameter WebTransactionType to make sure it agrees with your workflow. The choices are Pre-Authorize, Sale or Token. If payments are captured via SEOM, it should be set to Pre-Authorize. If payment is captured at the web store, it should be set to Sale. To pre-authorize or charge new transactions on import, WebTransactionType must be set to TOKEN.

CyberSource Access Credentials

• The Name column contains the fields that are applicable to CyberSource payment accounts.
• The Value column is where you enter or select to "left-click" the mouse on an object, usually a row in a table, in the context of Monsoon OMS documentation a setting for those fields.
• When a field is selected, a comment or description of the field's purpose is displayed at the bottom of the list. The descriptions are also listed here.

APIAccessKey

• enter the Merchant ID obtained from CyberSource for Payment API access

APISecurityKey

• enter the path and file name of the security key (.p12) file received from CyberSource

NamespaceURI

• this parameter should be left blank, unless instructed by CyberSource to temporarily switch to a secondary URI if the primary URI becomes unavailable

ProcessorName

• select the payment processor CyberSource uses to process payments with your acquirer

ProxyPassword

• if your company uses a proxy server for internet access, enter the password for Proxy Server access.

ProxyServer

• only for use if your company uses a proxy server for internet access. Only one proxy server can be designated for this CyberSource account

ProxyUserName

• if your company uses a proxy server for internet access, enter the user name for Proxy Server access

ServerURL

• this parameter should be left blank unless instructed by CyberSource to temporarily switch to another server, should the primary server URL be unavailable

TestMode

• if TRUE, transactions sent to CyberSource are treated as "test" data
• if FALSE, transactions sent to CyberSource are treated as "live" data

UseAutoAuthReversal

• when capturing an amount less than the authorized amount, if your CyberSource account is configured to automatically reverse the uncaptured funds, set this parameter to YES to prevent secondary capture attempts

Use Log

• default setting is NO
• Set to YES to have the CyberSource Client output a transaction log for troubleshooting purposes. SHOULD ONLY BE USED FOR TEST TRANSACTIONS!

UseWindowsProxySetting

• default settings is NO
• Only for use if your company uses a proxy server for internet access. Set to YES to have CyberSource Client use the Proxy Server settings defined for the Windows OS (WinHTTP).

Additional Information

How to Create a Payment Account

Created: 11/15/12

Revised: 12/23/14

Published: 04/14/16