Independent

Software
Vendors

User Guide
Cybersource Contact Information
For general information about our company, products, and services, go to https://www.cybersource.com.

For sales questions about any Cybersource service, email [email protected] or call 650-432-7350 or 888-330-2300 (toll free in
the United States).

For support information about any Cybersource service, visit the Support Center: https://www.cybersource.com/support

Copyright
© 2020. Cybersource Corporation. All rights reserved. Cybersource Corporation (“Cybersource”) furnishes this document and the
software described in this document under the applicable agreement between the reader of this document (“You”) and Cybersource
(“Agreement”). You may use this document and/or software only in accordance with the terms of the Agreement. Except as expressly
set forth in the Agreement, the information contained in this document is subject to change without notice and therefore should not
be interpreted in any way as a guarantee or warranty by Cybersource. Cybersource assumes no responsibility or liability for any errors
that may appear in this document. The copyrighted software that accompanies this document is licensed to You for use only in strict
accordance with the Agreement. You should read the Agreement carefully before using the software. Except as permitted by the
Agreement, You may not reproduce any part of this document, store this document in a retrieval system, or transmit this document, in
any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written consent of Cybersource.

Restricted Rights Legends

For Government or defense agencies:Use,duplication, or disclosure by the Government or defense agencies is subject to restrictions
as set forth the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and in similar clauses in the FAR and
NASA FAR Supplement.

For civilian agencies: Use, reproduction, or disclosure is subject to restrictions set forth in suparagraphs (a) through (d) of the
Commercial Computer Software Restricted Rights clause at 52.227-19 and the limitations set forth in Cybersource Corporation's
standard commercial agreement for this software. Unpublished rights reserved under the copyright laws of the United States.

Trademarks
Authorize.Net, eCheck.Net, and The Power of Payment are registered trademarks of Cybersource Corporation. Cybersource,
Cybersource Payment Manager, Cybersource Risk Manager, Cybersource Decision Manager, and Cybersource Connect are trademarks
and/or service marks of Cybersource Corporation. Visa, Visa International, Cybersource, the Visa logo, and the Cybersource logo
are the registered trademarks of Visa International in the United States and other countries. All other trademarks, service marks,
registered marks, or registered service marks are the property of their respective owners.

Condentiality Notice
This document is furnished to you solely in your capacity as a client of Cybersource and as a participant in the Visa payments system.

By accepting this document, you acknowledge that the information contained herein (the “Information”) is condential and subject
to the condentiality restrictions contained in Visa's operating regulations and/or other condentiality agreements, which limity our
use of the Information. You agree to keep the Information condential and not to use the Information for any purpose other than its
intended purpose and in your capacity as a customer of Cybersource or as a participant in the Visa payments system. The Information
may only be disseminated within your organization on a need-to-know basis to enable your participation in the Visa payments system.
Please be advised that the Information may constitute material non-public information under U.S. federal securities laws and that
purchasing or selling securities of Visa Inc. while being aware of material non-public information would constitute a violation of
applicable U.S. federal securities laws.

Revision
Version: 24.03
Contents

Contents

Recent Revisions to This Document............................................................................................... 6

VISA Platform Connect: Specications and Conditions for Resellers/Partners..................... 7
About the Integrated Solutions...................................................................................................... 8
Built by Us............................................................................................................................................9
Adobe Commerce Cloud......................................................................................................... 9
Release Notes................................................................................................................ 12
Updating the Adobe Commerce Cloud..................................................................... 14
Conguring the Adobe Commerce Cloud.................................................................14
Conguring Security Credentials...............................................................................15
Conguring Additional Backend Settings.................................................................15
Support............................................................................................................................31
OpenCart................................................................................................................................. 32
Release Information..................................................................................................... 33
Installation......................................................................................................................33
Conguration Overview.............................................................................................. 33
Enable Basic Conguration........................................................................................ 34
Enable Unied Checkout.............................................................................................36
Enable Tokenization......................................................................................................36
Enable Fraud Management..........................................................................................37
Enable 3-D Secure (Payer Auth)................................................................................38
Enable eCheck.............................................................................................................. 39
Enable Reporting.......................................................................................................... 39
Enforcing Strong Customer Authentication............................................................ 41
Scheduling Report Generation.................................................................................. 42
Using the Plugin............................................................................................................ 44
Testing.............................................................................................................................52
Upgrading....................................................................................................................... 53
Troubleshooting Assistance....................................................................................... 53
Oracle NetSuite......................................................................................................................54
Processor Support.......................................................................................................55
Release Notes............................................................................................................... 55
SuiteApp Installation and Update..............................................................................60

Cybersource Contents 3
Contents

Conguring SuiteApp................................................................................................... 61
Conguring Payment Methods...................................................................................62
Mapping Payment Methods.........................................................................................66
Mapping Check for Card Types..................................................................................67
Conguring Payment Processing Proles................................................................ 67
Conguring Reports.....................................................................................................72
Conguring Invoicing................................................................................................... 74
Enabling Payment Instrument Support.....................................................................80
Enabling a Payment Facilitator...................................................................................80
Enabling Network Tokenization...................................................................................81
Oracle NetSuite Merchant-Initiated Transactions.................................................83
Reference Information................................................................................................ 84
PrestaShop.............................................................................................................................. 88
Release Information..................................................................................................... 89
Installation..................................................................................................................... 90
Conguration................................................................................................................ 90
Using the Plugin........................................................................................................... 101
Testing...........................................................................................................................109
Upgrading...................................................................................................................... 110
Troubleshooting........................................................................................................... 110
Shopify..................................................................................................................................... 112
Conguring Security Credentials............................................................................. 113
Installing the Cybersource App on Shopify.............................................................113
Conguring Shopify.....................................................................................................113
Reference Information................................................................................................ 114
Built by Our Partners...................................................................................................................... 116
BigCommerce......................................................................................................................... 116
Release Information..................................................................................................... 117
Requirements and Prerequisites............................................................................... 117
Supported Features.................................................................................................... 117
Conguring BigCommerce......................................................................................... 118
Upgrade..........................................................................................................................121
Becoming a Partner........................................................................................................................122
Key Information..................................................................................................................... 123
Tech Partner Requirements................................................................................................ 123
Create a Sandbox Account....................................................................................... 123
Obtain a Partner Solution ID..................................................................................... 124
Example: Sending a Partner Solution ID.................................................................. 124
How to Validate the Account in the Business Center.......................................... 125
Develop Your Integration.....................................................................................................126
Getting Started........................................................................................................... 126
Best Practices............................................................................................................. 126
SDKs and Github..........................................................................................................126
Developer Center and API Libraries........................................................................ 126
Developer Center Forum........................................................................................... 127
Partner Blog and Newsletter.....................................................................................127

Cybersource Contents 4
Contents

The Partner Directory.......................................................................................................... 127

Prerequisites................................................................................................................ 127
Sign-Up Steps.............................................................................................................. 127
Populating the Directory Prole...............................................................................128
Frequently Asked Questions................................................................................................131
Contact Information..............................................................................................................131

Cybersource Contents 5
Recent Revisions to This Document

Recent Revisions to This

Document

24.04
Shopify Added Shopify guide. See Shopify.

24.03
Revisions throughout the guide contain only editorial changes and no technical updates.

24.02
Adobe Commerce Cloud Added Adobe Commerce guide. See Adobe
Commerce Cloud.
Revisions throughout the guide contain only editorial changes and no technical updates.

24.01
Initial release.

Cybersource Recent Revisions to This Document 6

VISA Platform Connect: Specications and Conditions for Resellers/Partners

VISA Platform Connect:

Specications and
Conditions for Resellers/
Partners

The following are specications and conditions that apply to a Reseller/Partner enabling
its merchants through Cybersource for Visa Platform Connect (“VPC”) processing. Failure
to meet any of the specications and conditions below is subject to the liability provisions
and indemnication obligations under Reseller/Partner’s contract with Visa/Cybersource.
1. Before boarding merchants for payment processing on a VPC acquirer’s connection,
Reseller/Partner and the VPC acquirer must have a contract or other legal agreement
that permits Reseller/Partner to enable its merchants to process payments with the
acquirer through the dedicated VPC connection and/or traditional connection with
such VPC acquirer.
2. Reseller/Partner is responsible for boarding and enabling its merchants in accordance
with the terms of the contract or other legal agreement with the relevant VPC acquirer.
3. Reseller/Partner acknowledges and agrees that all considerations and fees associated
with chargebacks, interchange downgrades, settlement issues, funding delays, and
other processing related activities are strictly between Reseller and the relevant VPC
acquirer.
4. Reseller/Partner acknowledges and agrees that the relevant VPC acquirer is
responsible for payment processing issues, including but not limited to, transaction
declines by network/issuer, decline rates, and interchange qualication, as may be
agreed to or outlined in the contract or other legal agreement between Reseller/
Partner and such VPC acquirer.
DISCLAIMER: NEITHER VISA NOR CYBERSOURCE WILL BE RESPONSIBLE OR LIABLE
FOR ANY ERRORS OR OMISSIONS BY THE VISA PLATFORM CONNECT ACQUIRER IN
PROCESSING TRANSACTIONS. NEITHER VISA NOR CYBERSOURCE WILL BE RESPONSIBLE
OR LIABLE FOR RESELLER/PARTNER BOARDING MERCHANTS OR ENABLING MERCHANT
PROCESSING IN VIOLATION OF THE TERMS AND CONDITIONS IMPOSED BY THE RELEVANT
VISA PLATFORM CONNECT ACQUIRER.

Cybersource VISA Platform Connect: Specications and Conditions for Resellers/Partners 7

About the Integrated Solutions

About the Integrated

Solutions

Cybersource offers integrated solutions to enhance payment acceptance, fraud

management, recurring billing, reconciliation, and reporting processes. Our integrated
solutions provide signicant and vast use cases for product managers to developers and
business professionals. Reduce your operational costs through streamlined payment
integrations and improve customer satisfaction through exible and secure payment
options. Our solutions can easily scale to your growing business needs, help increase sales
and conversion rates, and provide a clear value proposition to distinguish your business
from competitors.
The solutions detailed in this document are:
• Adobe Commerce Cloud
• BigCommerce
• OpenCart
• Oracle NetSuite
• PrestaShop
• Shopify
For information on how to become a partner, see Becoming a Partner.
See these additional resources for more information about the ISV Plugins documented in
this guide:
• Adobe Commerce Cloud Cybersource Payment Platform
• Connecting with Cybersource
• Getting Started with OpenCart
• Oracle NetSuite
• PrestaShop

Cybersource About the Integrated Solutions 8

Built by Us

Built by Us

Welcome to Cybersource's suite of solutions built by Cybersource, for you. These

solutions offer potential use cases that improve operational efciency, enhance
security, and provide comprehensive reporting and invoicing. Reduce the risk of errors,
protect against fraudulent transactions, and ensure accurate nancial records through
streamlined reconciliation processes. Our solutions are ideal for various industries
including nancial services, healthcare, manufacturing, and distribution. For example, in
healthcare, our solutions can manage payment operations efciently, ensuring secure
and accurate processing of payments for services rendered, and support timely invoicing
actions.
These guides are built by Cybersource:
• Adobe Commerce Cloud
• OpenCart
• Oracle NetSuite
• PrestaShop
• Shopify

Adobe Commerce Cloud

You can integrate Cybersource with the Adobe Commerce Cloud platform to process
payments using Magento checkout. The Cybersource Adobe Commerce Cloud extension
supports popular payment methods, safeguards payment data, minimizes fraud, and
mitigates risks. This section describes the payment management capabilities offered by
Cybersource through the Adobe Commerce Cloud integration.
This guide also applies to installing this extension in a Magento Open Source environment.

Fraud Management
Fraud Management prevents fraud losses and gives you the exibility to control business
practices and policies in real time. Fraud Management can help you accurately identify and
review potentially risky transactions while minimizing the rejection of valid orders. Fraud
Management comprises these capabilities:

Cybersource Built by Us 9
Built by Us

• Real-time fraud screening performed only during authorization

• Device ngerprinting
• On-demand Conversion Detail Report for changes in order status

Account Takeover Protection

Cybersource Account Takeover Protection defends customers and merchants from
fraudulent use of online accounts. It monitors suspicious account changes and helps
identify high risk users at account creation and login. These capabilities comprise Account
Takeover Protection:
• Real-time event screening of account creation, login, and changes
• Device ngerprinting

Payer Authentication
Cybersource Payer Authentication enables you to add support to your web store for
card authentication services offered by Visa, Mastercard, and other card brands. These
programs verify the cardholder’s identity directly with the card-issuing bank in real time
to increase payment security and reduce the risk of fraud. However, Payer Authentication
is not a fraud management service, and Cybersource recommends that you congure a
comprehensive fraud management program such as Decision Manager in addition to Payer
Authentication services. These services comprise Payer Authentication:
• Veried by Visa
• Mastercard Identity Check
• American Express SafeKey
• Discover ProtectBuy
• JCB
• Diners
• Maestro International
To comply with the recent mandates for French local processors that support Payer
Authentication, CMCIC, Atos and BNP processors no longer supports these combinations.

PayPal
The Adobe Commerce Cloud integration includes the PayPal payment method. Processing
your PayPal transactions through Cybersource allows you to consolidate all payment types
under a single gateway account, simplify integration efforts, screen PayPal transactions
for fraud with Decision Manager, and streamline reporting. These services comprise
PayPal:
• Sessions
• Check Status
• Order
• Authorization
• Authorization Reversal
• Capture

Cybersource Built by Us 10
Built by Us

• Sale
• Refund
• PayPal Credit
• Billing Agreements

PayPal Credit
PayPal Credit is a payment method that allows merchants to accept a PayPal transaction
when the customer chooses to nance their purchase through PayPal.

Electronic Check (eCheck Service)

The eCheck Service a form of digital payment that serves the same function as a physical
check. When a merchant accepts an electronic check payment, the funds are pulled
directly from the customer’s checking or savings account. These are the eChecks include
both debit and credit services.
eCheck Service process refunds with the credit payment service.

Online Bank Transfers

Online banking services enable customers to pay for goods by sending money from their
bank account to the merchant.
The Cybersource Adobe Commerce Cloud extension supports the following payment
methods and corresponding online bank transfer services:
• Bancontact
• Sale
• Check Status
• Refund
• Country: Belgium
• iDEAL
• Options
• Sale
• Check Status
• Refund
• Country: Netherlands

Tax Calculation
The Tax Calculation service provides real-time tax calculation during order checkout for
orders placed worldwide with your business.

Delivery Address Verication

The Delivery Address Verication service veries the entered address and suggests the
recommended address for city, state, and zip code combinations in real time.

Cybersource Built by Us 11
Built by Us

If this feature is enabled in the Adobe Commerce Cloud console, the Cybersource Adobe
Commerce Cloud extension veries the delivery address on shipping information updated
by the user.

Klarna
Klarna credit provides a seamless user experience for online customer nancing to
merchants of all sizes, which helps in increasing customer choice, loyalty and growth in
sales.

Google Pay
Google Pay is a digital wallet that allows customers to pay with any payment method saved
to their Google account.

Release Notes
This section provides information about functionality, bug xes, and enhancements for the
Adobe Commerce Cloud Cybersource integration.

June 2024
Adobe Commerce Cloud Cybersource • Fixed Logger and CSP issue for Magento
Version 3.5.8 is compatible with Adobe v2.4.7.
Commerce Cloud: 2.4.6 p3, 2.4.6 p2, 2.4.6 p1, • PHP support added for v8.3.
2.4.6, 2.4.5 p5, 2.4.4 p6 and PHP 8.2, 8.1
• Removed unused class in Apple Pay.
• Added required eld for Merchant ID in
Back Store.
• Fixed issue for admin order redirecting to
blank page.
• Made Payer Authentication common for
both Secure Acceptance (Stored Card)
and Soap Toolkit API.
• Fixed Visa Checkout error "No such cart
entity id with cartid".

March 2024
Adobe Commerce Cloud Cybersource • Removed zend dependency and replaced
Version 3.5.7 is compatible with Adobe with laminas.
Commerce Cloud: 2.4.6 p3, 2.4.6 p2, 2.4.6 p1, • Removed Payer Authentication Cardinal
2.4.6, 2.4.5 p5, 2.4.4 p6 and PHP 8.2, 8.1 key dependency from Back Store
Conguration.
• Google Pay and Apple Pay refund issue
xed for multiple websites.

Cybersource Built by Us 12
Built by Us

• Apple Pay customer billing address xes

for downloadable and virtual products.
• The issue has been xed for JSON error
message in the 3-D Secure pop-up.
• Fixed invalid card type message that
appeared in credit card Flex Microform.
• Added error message for Apple Pay
session failure.
• Fixed Device Fingerprint raw parameter
for Secure Acceptance.
• Fixed Payer Authentication failure
scenario.

October 2023
Adobe Commerce Cloud Cybersource • Implemented Cardinal Cruise Direct
Version 3.5.6 is compatible with Adobe Connection API Payer Authentication.
Commerce Cloud: 2.4.6 p2, 2.4.6 p1, 2.4.6, • Removed dependency on
2.4.5 p4, 2.4.4 p5, and PHP 8.2, 8.1
sales_order_grid table for Google Pay
and Secure Acceptance.
• Apple Pay order cancel xes.
• PayPal billing address line 2 issue xes.
• Removed parenthesis for http signature
request-target in core and eCheck
module.
• Upgraded version for the lcobucci/jwt
from 3.4.2 to 3.4.6.

May 2023
Adobe Commerce Cloud Cybersource 3.5.5 • PHP support added for v 8.2.
is compatible with Adobe Commerce Cloud: • Compatibility with Adobe Commerce
2.4.6, 2.4.5 p2, 2.4.5p1, 2.4.4 and PHP 8.2, 8.1 Cloud v2.4.6 – Changed few components
of zend framework to laminas as per the
latest Adobe Commerce Cloud changes.
• Fixed bugs related to supported card
types and sandbox/production issue in
Apple Pay.
• Fixed jQuery deprecated functions.

Cybersource Built by Us 13
Built by Us

February 2023
Adobe Commerce Cloud Cybersource 3.5.4 • New implementation for eCheck cron –
is compatible with Adobe Commerce Cloud: EventStatus.
2.4.5 p2, 2.4.5 p1, 2.4.x, 2.3.x
• Fixed bug related to Strong Customer
Authentication.
• Removed required validation from
reCAPTCHA elds.
• Updated Klarna library from credit to
payments.
• Added PaymentFlowMode as inline and
PaymentMethodName as pay_now in Klarna
app session request.
• Updated WSDL version to latest V1.206.
• Add new payment reject status as
AUTHORIZED_RISK_DECLINED for Decision
Manager reject.

Updating the Adobe Commerce Cloud

You must have a Cybersource Business Center account to update Adobe Commerce
Cloud.
If you do not have an account, go to the Business Center Registration website to create
an account. Follow the email instructions that you received to activate your merchant
account, and then log in to the Business Center to complete the registration process.
Follow these steps to update the Cybersource bundle to the latest version:
1. In your directory, navigate to Adobe Commerce Cloud root directory / composer.json
le.
2. In the composer.json le, under require eld, change the version to the plugin with the
latest version.
3. After you change the version in require eld of composer.json, run the composer
update command.

Conguring the Adobe Commerce Cloud

Customer payments can be managed through the Adobe Commerce Cloud or the
Cybersource Business Center. This section describes the settings you must congure
in the Business Center as well as some general use cases that will be typical in the day-
to-day management of your Adobe Commerce Cloud store. Contact Cybersource for
information about product availability and enablement.
You must complete all of the conguration tasks in order to use the features offered in
the Adobe Commerce Cloud Cybersource integration.

Cybersource Built by Us 14
Built by Us

Conguring Security Credentials

The Cybersource module uses connection methods to access Cybersource services that
require their own security credentials for authentication.
You must create and congure the SOAP toolkit key and REST API key for the Adobe
Commerce Cloud to function properly.
If you do not have a Business Center account, go to the Business Center Registration
website to create an account. Follow the email instructions that you received to
activate your merchant account, and then log in to the Business Center to complete the
registration process. Store your merchant key ID for later use.

Creating a SOAP Toolkit Key

The Cybersource Adobe Commerce Cloud integration uses the SOAP Toolkit API to access
several Cybersource services.
From your Business Center account, you must generate the SOAP toolkit key. For steps
on how to create a SOAP toolkit key, see Creating a SOAP Toolkit Key . Store your SOAP
toolkit key for later use.

Creating a REST API Key

The Cybersource Adobe Commerce Cloud integration requires REST API key creation to
use some services like Flex Microform and the Fraud Management report.
From your Business Center account, you also need your merchant key ID and shared
secret key to enable the integration with Adobe Commerce Cloud. For steps on how to
generate a shared secret key, see Creating a Shared Secret Key Pair. Store your key ID
and shared secret key for later use.

Conguring Additional Backend Settings

Certain Cybersource services supported on the Adobe Commerce Cloud require
additional backend setup on your Business Center account. Contact your Cybersource
account representative to enable any of these services:
• Payment Tokenization: required by the module for credit card processing
• Decision Manager
• Payer Authentication
• PayPal Express Checkout
• eCheck Service
• Online Bank Transfers
• Tax Calculation
• Klarna
• Click to Pay: Enabled in the Business Center
• Apple Pay: Enabled in the Business Center

Conguring Backend Settings

Follow these steps to access the conguration settings in the administration
section of your Adobe Commerce Cloud console:

Cybersource Built by Us 15
Built by Us

1. Go to the Adobe Commerce Cloud administration console.

2. On the left navigation, click Stores.
3. Under Settings, click Conguration.
4. On the Conguration page, click Sales to expand the menu.
5. Click Payment Methods.
6. Choose OTHER PAYMENT METHODS > Cybersource.
Complete all of the required elds in the sections and subsections of the Cybersource
settings to congure the Cybersource payment module and other payment methods.
Expand each section to complete the elds.

Conguring General Settings

The settings under the General section apply to all payment methods. Follow these steps
to complete this section:
1. From the Cybersource setting, click the arrow to expand the General section.
2. From the Debug Mode drop-down list, choose Yes to troubleshoot using the Adobe
Commerce Cloud Cybersource logs (cybs.log). Diagnostic information is stored in log
les on the Adobe Commerce Cloud web server.
3. From the Sort Order drop-down list, change the default module sort order.
4. In the Show Exact Rejection or Error Message to Users option, set to No when you
want the general error message displays according to Adobe Commerce Cloud in all
rejection and error cases. Set to Yes when you want the general error message displays
according to the responses from Cybersource in all rejection and error cases.
5. In the Override Payment Error Route Path eld, enter the error page route path. When
no path is entered, the checkout/cart route is used when you leave the default Use
system value box checked.
Conguring WebService

The WebService conguration includes the default Adobe Commerce Cloud merchant ID
(applies to all the payment methods), the REST shared key, and the SOAP key detail. Follow
these steps to complete the conguration:
1. Click WebService Conguration to expand the section.
2. In the Merchant ID eld, enter your Cybersource merchant ID.
3. From the Test Mode drop-down list, choose Yes when you are using the Business
Center testing environment, or No when you are using the production Business Center.
4. This eld is optional. In the Developer ID eld, enter the developer ID. It must not be
longer than eight characters. You can request Cybersource to assign you a developer
ID.
5. In the SOAP Key Detail eld, enter the key you generated from the SOAP toolkit API. If
you have not generated a key, see Creating a SOAP Toolkit Key for instructions.
6. In the REST API Key Detail eld, enter the REST key you generated from the Business
Center. If you have not generated a REST Shared Secret Key Pair, see Creating a
Shared Secret Key Pair for instructions.

Cybersource Built by Us 16
Built by Us

Proper conguration of the SOAP WebService is required for the functioning of other
services including Tax Calculation, Secure Acceptance, PayPal, Account Takeover
Protection, and Apple Pay. If you experience issues with these modules, ensure that the
SOAP WebService options are congured correctly. The SOAP API Key Detail should
have the correct value and the Test Mode option should match the correct environment
for the Cybersource Business Center is set to the testing environment.
7. In the REST API Shared Secret Key eld, enter the Shared Secret key you generated
from the Business Center. If you have not generated a REST Shared Secret Key Pair, see
Creating a Shared Secret Key Pair for instructions.
Proper conguration of the REST Web Service is required for other services including
Flex Microform, Decision Manager, and the Account Updater. If you experience issues
with these modules, ensure that the REST Web Service options are congured properly.
The API Key Detail and API Shared Secret Key should have the correct value, and the
Test Mode option should match the correct environment for the Cybersource Business
Center.
Conguring Device Fingerprinting

Device Fingerprinting is used with Decision Manager for all relevant payment methods. If
you are not using Decision Manager, you must disable this module. Follow these steps to
congure device ngerprinting:
1. Click Device Fingerprint to expand the section.
2. In the Active eld, choose Yes to activate it or No to deactivate it if you are not using
Decision Manager.
3. In the Org ID eld, enter the value provided to you by Cybersource. To obtain this value
either for test or production, contact your Cybersource representative.
Conguring the Delivery Address Verication Service
The Delivery Address Verication Service acts as an additional layer of address
verication and normalization on the shipping page. Follow these steps to congure this
section:
1. Click Delivery Address Verication Service to expand the section.
2. From the Address verication drop-down list, choose Yes to enable this service or No
to disable this service.
3. From the Address Force Normalization drop-down list, choose Yes to require the use
of suggested address alternatives or No to make the suggested address alternatives
optional.

Conguring Credit Card Payments

Follow these steps to congure Adobe Commerce Cloud credit card
payments:
1. From the Enabled drop-down list, choose Yes to activate or No to deactivate the credit
card payment method.
2. In the Title eld, enter the text you want to display as the name for credit card payment
method. This name will be used for Web Mobile, Flex Microform, and Silent Order Post.

Cybersource Built by Us 17
Built by Us

3. In the Payment API drop-down list, choose Payment API to have an authorization
performed and post card data to Cybersource. Choose SOAP Toolkit API to have
the card information tokenized through Cybersource. The SOAP service separately
requests authorizations.
4. In the Checkout Flow Type drop-down list, choose a desired checkout type.
Cybersource recommends you choose Flex Microform. Flex Microform is a REST-based
Microform Integration to access new enhancements, easier conguration, and updated
technology. You will use all of the benets from the Hosted Checkout and Checkout API.
The customer never leaves your checkout page and is a potential SAQ A qualication.
For more information about Microform Integration, see Microform Integration.
5. In the CSRF Token Expiration Time (Seconds) eld, enter the expiration time in seconds.
This is the lifetime of the SOP security token used to prevent card testing attacks.
Leave blank for the default of 600 seconds.
Conguring Strong Customer Authentication

When payer authentication is enabled and a transaction is declined with reason code
478 (Strong Customer Authentication required), another request is sent from the Adobe
Commerce Cloud Cybersource module for the same order. The customer must complete a
3-D Secure challenge.
To congure this setting, click Strong Customer Authentication to expand the section. In
the Enforce Strong Customer Authentication when saving a card drop-down list, choose
Yes to have the cardholder complete a 3-D Secure challenge while saving a card.
Conguring Credit Card Settings

Follow these steps to complete the Credit Card Settings section:

1. Click Credit Card Settings to expand the section.
2. From the Payment Action drop-down list, choose Authorize Only or Authorize and
Capture. Authorize Only reserves funds during checkout and captures when making
an invoice. The Authorize and Capture payment action authorizes and captures funds
during the customer checkout.
3. From the Auth Indicator drop-down list, choose the purpose of the authorization.
4. From the New Order Status eld drop-down list, choose the order status assigned to
the order when successfully paid, or leave the default Use system value box checked for
Processing order status.
5. From the Ignore AVS drop-down list, choose Yes to have the results of AVS verication
ignored.
6. In the Ignore CVN eld, choose Yes to have the results of CVN verication ignored.
7. In the Skip Fraud Management for Tokenization eld, choose No to have Skip Decision
Manager eld set to false for Secure Acceptance tokenization requests and set to true
otherwise.
8. In the Skip Pre-Authorization Check for Tokenization eld, choose to No to have the
skip preauthorization eld set to false for Secure Acceptance tokenization requests
and set to true otherwise.

Cybersource Built by Us 18
Built by Us

9. In the Pass expiration date for tokenized card via SOAP eld, specify the card expiration
date with SOAP Toolkit Authorization Calls for card tokenization.
10.In the Credit Card Types eld box, choose which card types you want to accept. This
only applies to Checkout API and Flex Microform conguration. This option is not used
for Hosted Checkout.
11. In the Payment from Applicable Countries eld, leave the default Use system value box
checked to accept credit card payments from the countries choose, or uncheck the
Use system value box to specify countries in the next eld.
12.To specify the countries from which to accept credit card payments, in Payment from
Specic Countries box choose the countries.
13.From the Override secure acceptance locale drop-down list, leave the default Use
system value box checked to use the store locale language.
Conguring Payer Authentication

The Payer Authentication (3-D Secure) protocol reduces fraud and security to online
payments. 3-D Secure adds frictionless authentication and improves the user experience.
You must have the SOAP Toolkit congured to use this service.
Follow these steps to congure the Payer Authentication section:
1. Click Payer Authentication to expand the section.
2. From the Enabled drop-down list, choose Yes to activate the Payer Authentication
Module or No to deactivate it.
3. From the Credit Card Types eld box, choose the card types to be enabled for Payer
Authentication.
Conguring Save Card for Later Service

Follow these steps to congure Save Card for Later Service settings:
1. Click Save Card for Later Service to expand the section.
2. From the Enabled drop-down list, choose Yes to enable the customer to save their
credit card information securely for later use.
3. In the Saved Card Section Title eld, enter the name of the saved cards payment
method.
4. From the Save Card for Later for Admin orders drop-down list, choose Yes to enable
storing card details for orders placed in the admin area.
5. From the Use CVV for Saved Credit Cards drop-down list, choose Yes to enable the
customer to enter the Card Security Code when paying with a stored card.
6. From the Use CVV for Saved Credit Cards in Admin drop-down list, choose Yes to allow
the merchant to enter the customer’s Card Security Code when the customer is paying
with a stored card.
7. Click Save Cong.
Conguring reCAPTCHA
The Adobe Commerce Cloud SOAP Toolkit API provides an option to use reCAPTCHA. This
feature is essential in protecting the merchant's store from brute force attacks. Most of

Cybersource Built by Us 19
Built by Us

the time, the reCAPTCHA is invisible to normal users, but it will provide a visible challenge
when necessary. The module providing reCAPTCHA is an optional package.

Installing reCAPTCHA
To install reCAPTCHA, run the following command for composer installation:
composer require Cybersource/module-recaptcha

Creating reCAPTCHA
Follow these steps to generate Google reCAPTCHA Site Key and Secret Key:
1. Visit the Google reCAPTCHA website: https://www.google.com/recaptcha/about/.
2. Log in to the reCAPTCHA Admin Console.
3. Click the Create icon.
4. Fill in the required details.
5. After you submit the details, the reCAPTCHA site key and secret key are generated. Use
these keys to congure the module in Back Store.

Conguring reCAPTCHA in Adobe Commerce Cloud

1. Go the Adobe Commerce Cloud console.
2. On the Payment Methods page, under the Cybersource settings, click reCaptcha to
expand the section.
3. From the Enabled drop-down list, choose Yes to activate, or No to deactivate
reCAPTCHA.
4. In the Website API Key eld, enter your site key obtained from reCAPTCHA Admin
Console.
5. In the Secret API Key eld, enter your secret key obtained from reCAPTCHA Admin
Console.
6. From the reCAPTCHA type drop-down list, choose the reCAPTCHA type that you
choose for your API keys.
7. In the Badge position eld, choose the reCAPTCHA badge position.
8. In the reCAPTCHA language eld, choose a language code for reCAPTCHA or leave the
Auto option selected.
9. Click Save Cong.
10.Clear the Adobe Commerce Cloud cache.

Conguring the eCheck Payment Module

The Cybersource eCheck module allows customers to make purchases using a routing
number and an account number. During checkout, an eCheck transaction request is sent
to Cybersource. If successful, the transaction is sent to the Automated Clearing House
(ACH).
the Adobe Commerce Cloud queries Cybersource periodically to check on the status
of each pending eCheck transaction. In response, Cybersource provides an updated
transaction status, known as a Payment Event Type. Various outcomes can occur during
ACH processing. For each pending transaction included in the Cybersource response, the

Cybersource Built by Us 20
Built by Us

Adobe Commerce Cloud determines whether a transaction remains pending, settles, or is

rejected.
These are the eCheck payment event types you can congure:
• Pending Event Type: No change is made to the transaction or order status. The order
remains in Payment Pending state.
• Reject Event Type: The order is cancelled.
• Accept Event Type: An invoice is prepared for that order, and the order status changes
to processing.
Testing eCheck Payment Settings

You can test the eCheck Payment Event Types using two the Adobe Commerce Cloud
settings that simulate possible event types during the processing of the requested
report. While the status request goes to Cybersource, the Adobe Commerce Cloud
ignores the returned Payment Event Type in the response and uses the Test Event Type
instead.
Follow these steps to test the eCheck Payment Event Types:
1. Click eCheck to expand the section.
2. From the Enabled drop-down list, choose Yes to enable the eCheck payment method.
3. From the Title eld, enter the text that is displayed to customers as the name of this
payment method.
4. In the Accept Event Type box, choose which payment statuses to accept, which signify
the receipt of funds and the order status moved to processing.
5. In the Pending Event Type box, choose which payment statuses to consider for pending.
6. In the Reject Event Type box, choose which payment statuses to reject which were
initially accepted during checkout, but rejected after processed by ACH.
7. In the Payment From Applicable Countries eld, leave the Use system value box checked
to accept the eCheck payment method, or uncheck the Use system value box to specify
countries in the next eld.
8. In the Payment From Specic Countries box, choose the countries from which to
accept the eCheck payment method.
9. From the Enabled Drivers License Number drop-down list, choose Yes or No to require
customers to enter a drivers license number. For TeleCheck, contact a representative
to see if this eld is required.
10.From the Enabled Check Number drop-down list, choose Yes or No to require the
customer to enter the check number. These processors have specied whether it is
required or optional:
• Chase Paymentech Solutions: Optional
• Cybersource ACH Service: Not used
• RBS WorldPay Atlanta: Optional on debits, and required on credits
• TeleCheck: Strongly recommended on debit requests, and optional on credits
11. From the Agreement Required drop-down list, choose Yes or No to indicate whether
you want to require an agreement at the checkout page.

Cybersource Built by Us 21
Built by Us

12.From the SEC code drop-down list, choose a code that species the authorization
method for the transaction.
13.In the Sort Order eld, enter the number of entries to be sorted on a page.
14.Click Save Cong.

Conguring Fraud Management

You must congure the Adobe Commerce Cloud to work with Fraud Management to use all
of the features.
Follow these steps to congure Fraud Management in the Adobe Commerce Cloud:
1. Click Fraud Management to expand the section.
2. From the Enable Fraud Management CRON Job drop-down list, choose Yes.
3. In the Fraud Management fail email sender option, leave the Use system value box
checked.
4. In the Fraud Management fail email template option, leave the Use system value box
checked.
5. From the Settle Fraud Management accepted order automatically drop-down list,
choose Yes.
6. Expand the On-Demand Job section to see the Report Date eld.
7. Enter a date to download an accepted or rejected transactions report, and click Run.
8. Click Save Cong.

Fraud Management Orders

The Decision Manager rule setting and the response received for authorizations and sales
service determine whether the Adobe Commerce Cloud marks the orders as Pending
Review.
On the Decision Manager Case Management page, when you change an order from
REVIEW to REJECT or ACCEPT, the Adobe Commerce Cloud updates payment transaction
states periodically (by cron every two minutes) by contacting Cybersource and querying
for changes.
In the settings, nd Adobe Commerce Cloud Cron settings to congure them to trigger
an Adobe Commerce Cloud task. The task looks for Decision Manager changes in
the Cybersource Business Center and updates the Adobe Commerce Cloud Orders
accordingly.
If the module detects a change in state, it updates the order status in the Adobe
Commerce Cloud from Pending Review to one of these states:
• Processing
• Pending
• Closed
If an order is Pending Review in Decision Manager, you cannot prepare an invoice in the
Adobe Commerce Cloud until Decision Manager accepts it.

Cybersource Built by Us 22
Built by Us

Fraud Management Refunds

Decision Manager must either accept or reject an order before issuing a refund. If you
reject an order in Decision Manager, an Authorization Reversal for the order automatically
occurs as part of the Cron process that queries Cybersource for updates in Decision
Manager.

Conguring Custom Fields

Decision Manager supports custom elds known as merchant-dened data elds. You
must congure the elds inside Decision Manager in the Business Center to use them. The
Cybersource Module for the Adobe Commerce Cloud sends 10 of these elds.
Follow these steps to add custom elds provided by the Adobe Commerce Cloud:
1. Log in to the Business Center and go to Decision Manager > Shared Conguration >
Custom Fields.
2. Choose Merchant Custom Fields.
3. To add a eld, click ADD CUSTOM FIELD, enter a name, and choose an order element.
Use the list below to map the correct names and elements for each eld:
• Logged-in customer: Merchant_dened_data1
• Account creation date: Merchant_dened_data2
• Purchase History Count: Merchant_dened_data3
• Last Order Date: Merchant_dened_data4
• Member account age: Merchant_dened_data5
• Repeat customer: Merchant_dened_data6
• Coupon Code Used: Merchant_dened_data20
• Discount Amount: Merchant_dened_data21
• Gift Message: Merchant_dened_data22
• Order Source: Merchant_dened_data23
• Shipping Method Code: Merchant_dened_data31
• Shipping Method Description: Merchant_dened_data32
4. Click Save.
For detailed instructions on how to add custom elds, see the Decision Manager Guide.
In the Business Center, go to the left navigation panel, and choose Decision Manager >
Documentation > Guides.

Conguring Apple Pay

To use Apple Pay, you must meet these prerequisites:
• Have a valid Apple Developer Account.
• All pages that incorporate Apple Pay must be served over HTTPS.
• Your website must comply with the Apple Pay guidelines. For more information, see
Apple Pay on the Web Acceptable Use Guidelines.
• Your website must have HTTPS mode enabled and used at checkout. For more
information, see Setting Up Your Server.

Cybersource Built by Us 23
Built by Us

To congure Apple Pay with the Cybersource Adobe Commerce Cloud module, you must
complete these tasks:
1. Register an Apple Pay merchant ID. For instructions on how to do it, see Create Your
Apple Pay Merchant ID.
2. Create a Payment Processing certicate in the Business Center. For instructions on
how to do this, see Generating and Loading a New Certicate Signing Request.
3. Validate your store domain in Apple Pay. For instructions on how to do it, see Register a
Merchant Domain.
4. Create a Merchant Identity certicate. For instructions on how to do it, see Create a
Merchant Identity Certicate.
Conguring the Apple Pay Extension

Follow these steps to congure the Apple Pay extension:

1. Go the Adobe Commerce Cloud console, and open the Payment Methods page.
2. Under the Cybersource settings, click Apple Pay to expand the section.
3. From the Enable drop-down list, choose Yes or No to activate or deactivate Apple Pay.
4. In Title box, enter the text to display to customers on the checkout page.
5. From the Payment Action drop-down list, choose Authorize Only to reserve funds
during checkout and capture during invoice creation. Choose Authorize and Capture to
authorize and capture during customer checkout.
6. From the New Order Status drop-down list, choose the order status assigned to the
order that was successfully paid with Cybersource.
7. In the Apple Merchant ID box, enter the Apple Pay Merchant ID you previously created.
8. In the Apple Display Name box, enter the business name that will appear on a bank or
credit card statement. For example, COMPANY, INC.
9. In the Certied Domain box, enter the validated site domain on which the service is
meant to be used. Do not enter a https:// prex.
10.In the Path to Certicate box, enter the full path to the Merchant ID Certicate le.
11. In the Path to Key box, enter the full path to the Merchant ID Certicate Private key le.
12.In the Credit Card Types box, choose the types of credit cards to accept for payment.
13.In the Sort Order box, enter a number for the sort order.
Conguring Apple Pay

You must congure Apple Pay on your storefront, which is what is displayed to the
customer. Follow these steps to congure Apple Pay on your storefront:
1. While the customer is making a payment, in the Reviewing the order page, the customer
will choose Adobe Commerce Cloud Apple Pay.
2. An Apple Pay window appears, requesting ngerprint (Touch ID) authentication. Or, you
can choose a saved card.
3. After authentication is complete, an order success page appears. Verify the
transaction details in Cybersource Business Center.

Cybersource Built by Us 24
Built by Us

Conguring Google Pay

To use Google Pay on the Adobe Commerce Cloud, your site must be running through
HTTPS. Follow these steps to congure Google Pay in the Adobe Commerce Cloud:
1. Click Google Pay to expand the section.
2. From the Enable drop-down list, choose Yes or No to activate or deactivate Google Pay.
3. In the Title box, enter text to display to customers on the checkout page.
4. From the Payment Action drop-down list, choose Authorize Only to reserve funds
during checkout and capture during invoice creation. Choose Authorize and Capture to
authorize and capture funds during customer checkout.
5. In the Google Pay Merchant ID box, enter your Google Pay merchant ID.
6. In the Merchant Display Name box, dene your business name the payer will see for the
charge on a bank or credit card statement. For example, “COMPANY, INC.”
7. In the Payment From Applicable Countries eld, leave the Use system value box checked
if you want to accept payment from the default countries choose, or uncheck the Use
system value box to specify countries in the next eld.
8. In the Payment From Specic Countries box, choose the countries from where you want
to accept Google Pay.
9. In the Credit Card Types eld box, choose which card types to enabled.
10.In the Google Pay button on Product Page eld, choose Yes to show the Google Pay
button on the product page.
11. In the Google Pay button in mini cart eld, choose Yes to show the mini cart widget.
12.In the Sort Order box, enter a number to change the default module sort order.
13.Click Save Cong.

Conguring Alternate Payments

the Adobe Commerce Cloud has four types of Alternate Payments modules:
• PayPal. For more information, see Conguring PayPal on page 26.
• Klarna. For more information, see Conguring Klarna on page 25.
• Bank Transfer. For more information, see Conguring Bank Transfers on page 26.
• WeChat Pay. For more information, see Conguring WeChat Pay on page 28.
Click Alt Payments to expand the section.
Conguring Klarna

Follow these steps to congure Klarna payments.You can use the default merchant ID or
you can manually congure a new merchant ID:
1. Click Klarna to expand the section.
2. From the Enable drop-down list, choose Yes or No to activate or deactivate Klarna.
3. From Title box, enter the text to display to customers on the checkout page.
4. From the Use Default Merchant ID drop-down list, leave Yes selected to use the
Merchant ID given in Web Service Conguration under General Settings. Choose No to
enter another merchant ID and transaction key in the next two elds.

Cybersource Built by Us 25
Built by Us

5. If you choose not to use the default merchant ID, in the Merchant ID eld, enter a
merchant ID.
6. In the Transaction Key eld, enter the transaction key for the merchant ID you entered.
7. From the New Order Status drop-down list, choose the order status assigned to the
order successfully paid with Cybersource.
8. In the Payment From Applicable Countries eld, leave the Use system value box checked
to accept payment the from default countries selected, or uncheck the Use system
value box to specify countries in the next eld.
9. In the Payment From Specic Countries box, choose the countries from which you will
accept Klarna.
Conguring PayPal

Follow these steps to congure the PayPal Express Checkout, PayPal Credit, and PayPal
Billing Agreement:
1. Click PayPal to expand the section.
2. From the Enable drop-down list, choose Yes or No to activate or deactivate PayPal.
3. In Title box, enter the text to display to customers on the checkout page.
4. From the New Order Status drop-down list, choose the order status assigned to the
order successfully paid with Cybersource.
5. In the Merchant ID eld, enter your Adobe Commerce Cloud merchant ID.
6. From the PayPal Redirection Type drop-down list, choose Traditional Express Checkout
to redirect the customer PayPal Payment Page, or choose In-Context Express Checkout
for a PayPal pop-up to appear for customers to complete payment.
7. From the Payment Action drop-down list, choose Authorize Only to check the account
for validity, but not charge until the order is approved and invoiced. Choose Authorize
and Capture to charge the PayPal account at the time the order is submitted.
8. In the Payment From Applicable Countries eld, leave the Use system value box checked
to accept PayPal, or uncheck the Use system value box to specify countries in the next
eld.
9. In the Payment From Specic Countries box, choose which countries you will accept
PayPal.
10.From the Enable PayPal Credit drop-down list, choose Yes to enable nancing through
PayPal Credit.
11. In the PayPal Credit Title box, enter the text customers will see as the title of PayPal
Credit payment option.
12.From the Enable PayPal Billing Agreements drop-down list, choose Yes to allow
registered customers to create a billing agreement for faster purchases.
13.In the Sort Order box, enter a numeric value to place this payment method amongst all
the other Adobe Commerce Cloud payment methods.
Conguring Bank Transfers

Online banking services enable customers to pay for goods using direct online bank
transfers from their bank account to your Adobe Commerce merchant account.

Cybersource Built by Us 26
Built by Us

Click Bank Transfer to expand the section. In the Store Name eld, enter the name you
want customers to see on their bank transfer invoices.
Conguring iDEAL

Follow these steps to congure an iDEAL payment:

1. Click iDEAL to expand the section.
2. In the Enable drop-down list, choose Yes or No to activate or deactivate iDEAL bank
transfer.
3. In Title box, enter the text to display to customers on the checkout page.
4. In the Use Default Merchant ID eld, leave Yes selected to use the merchant ID given
in the Web Service Conguration under General Settings page. Choose No to enter
another merchant ID and transaction key in the next two elds.
5. If you choose not to use the default merchant ID, enter your Cybersource Merchant ID
in the Merchant ID eld.
6. In the Transaction Key eld, enter the transaction key for the merchant ID you entered.
7. In the Allowed Currencies box, choose the currencies with which to accept payment.
8. In the Sort Order box, change the default module sort order.
9. In the Payment From Applicable Countries eld, leave the Use system value box checked
to accept payments from the default countries select, or uncheck the Use system value
box to specify countries in the next eld.
10.To specify which countries you will to accept iDEAL from, choose the countries in the
Payment From Specic Countries box.
Conguring Bancontact

Follow these steps to congure Bancontact bank transfer payments:

1. Click Bancontact to expand the section.
2. In the Enable drop-down list, choose Yes or No to activate or deactivate Bancontact
Bank Transfer.
3. In Title box, enter the text to display to customers on the checkout page.
4. In the Use Default Merchant ID eld, leave Yes selected to use the Merchant ID given
in Web Service Conguration under General Settings. Select No to enter another
merchant ID and transaction key in the next two elds.
5. If you choose not to use the default merchant ID, enter your Cybersource merchant ID
in the Merchant ID eld.
6. In the Transaction Key eld, enter the transaction key for the merchant ID you entered.
7. In the Allowed Currencies box, choose the currencies with which to accept payment.
8. In the Sort Order box, change the default module sort order.
9. In the Payment From Applicable Countries eld, leave the Use system value box checked
to accept payments from the default countries selected, or uncheck the Use system
value box to specify countries in the next eld.
10.To specify the countries from which to accept Bancontact, choose the countries in the
Payment From Specic Countries box.

Cybersource Built by Us 27
Built by Us

Conguring WeChat Pay

WeChat Pay is a digital wallet that enable customers to make mobile payments and online
transactions. Customers who have provided bank account information can use the app to
pay bills, order goods and services, transfer money to other users, and pay in stores if the
stores have a WeChat payment option.
Follow these steps to congure WeChat Pay:
1. Click WeChat Pay to expand the section.
2. From the Enable drop-down list, choose Yes or No to activate or deactivate WeChat
Pay.
3. In the Sort Order box, change the default module sort order.
4. In Title box, enter the text to display to customers on the checkout page.
5. In the Use Default Merchant ID eld, leave Yes selected to use the Merchant ID from
the Web Service Conguration section under General Settings. Choose No to enter
another merchant ID and transaction key in the next two elds.
6. If you choose not to use the default merchant ID, enter your Cybersource merchant ID
in the Merchant ID eld.
7. In the Transaction Key eld, enter the transaction key for the merchant ID you entered.
8. In the QR Code Expiration Time eld, enter an expiration time in seconds for the
WeChat pay QR code.
9. In the Check Status Frequency eld, enter an interval in seconds between transaction
status checks.
10.In the Max Status Requests eld, enter a limit for transaction status checks.
11. In the Payment From Applicable Countries eld, leave the Use system value box checked
to accept payments from the default countries selected, or uncheck the Use system
value box to specify countries in the next eld.
12.To specify which countries from which to accept WeChat Pay, choose the countries in
the Payment From Specic Countries box.
13.In the Success/Failure Message Delay eld, enter a delay in seconds between the
transaction check and redirection to the result page.
14.In the Check Status query Simulated Response eld, choose a simulated Status Check
response code for testing.
15.Click Save Cong.

Conguring Taxes
Cybersource offers a service that calculates taxes to be charged on orders. You must
congure your settings in order to receive accurate results from Cybersource.
Contact your Cybersource representative to have this feature enabled. This feature
includes activation of sandbox capabilities as well.
Before conguring the Tax Calculation service, you must have the SOAP Web Service
congured. For more information, see Conguring Security Credentials on page 15.
To use the Tax Calculation Service, you must have the Product Tax Class codes and
Cybersource Tax Services settings congured. For more information, see Conguring

Cybersource Built by Us 28
Built by Us

Product Tax Classes on page 29 and Conguring Cybersource Tax Services Settings on
page 29.
Conguring Product Tax Classes

Each product in the Adobe Commerce Cloud has a setting for Tax Class. This setting
denes the product and how it should be taxed. Contact your Cybersource representative
for a list of available product tax class IDs and your tax consultant for advice on which IDs
you should use for products you sell.
Follow these steps to set the product tax class IDs in Adobe Commerce Cloud:
1. Go the Adobe Commerce Cloud Admin console.
2. On the left panel, click Stores, and then click Tax Classes.
3. On the Tax Classes page, click Add New to create a new tax class entry for each tax
class ID that Cybersource representative provides.
4. In the Tax Class Code eld, enter the code Cybersource provided to you.
5. From the Tax Class Type drop-down list, choose Product.
6. Click Save.
7. Complete these steps for each tax class ID.
Conguring Cybersource Tax Services Settings

Follow these steps to congure Cybersource Tax Services in the Adobe Commerce Cloud:
1. Go to the Adobe Commerce Cloud admin console.
2. On the left panel, click Stores, and then click Conguration.
3. On the Conguration page, go to Sales > Tax > Cybersource Tax Services.
4. From the Tax Calculation drop-down list, choose Yes to activate the Cybersource Tax
Services per your business requirements.
5. In the Nexus regions box, select any relevant regions your business has a physical
presence in the U.S. or Canada.
6. In the Customer countries to calculate Tax for box, choose the countries for which you
will calculate tax.
7. In the Customer Tax classes to exclude from Tax calculation box, choose the customer
tax classes to exclude from tax calculation.
8. In the Ship From elds, enter the city, postcode, country, and region from which the
orders are shipped.
9. In the Acceptance elds, enter the city, postcode, country, and region in which you will
accept or approve customers' orders.
10.In the Origin elds, enter the city, postcode, country, and region of the point of origin
from which the order is picked up.
11. In the Merchant VAT elds, enter the merchant VAT seller registration number.
12.Click Save Cong.

Cybersource Built by Us 29
Built by Us

Calculating Taxes for Shipping Rates

You might have taxes calculated for shipping rates if your site offers dynamic shipping
rates from a carrier that is presented to the customer at checkout. However, if you offer a
at-rate shipping charge, you might want to add taxes to that at rate.
Follow these steps to add taxes to at shipping rates:
1. On the Conguration page, go to Sales > Tax > Tax Classes.
2. From the Tax Class for Shipping drop-down list, select the product tax code that
references the taxes applied to shipping services.
3. Click Calculation Settings.
4. In the Shipping Prices eld, choose Excluding Tax when the shipping rates offered need
to have taxes added to them. Select Including Tax when shipping rates offered have
taxes included, and no taxes will be applied through the Cybersource tax service.
5. Click Save Cong.

Conguring Transactional Emails

When an order is agged for Decision Manager review, the customer is not informed
that their transaction was not fully accepted. If a manual review leads to a rejection of
the transaction, the customer is informed that their order is no longer active. You can
congure the email sent to the customer.
Follow these steps to congure the transactional emails be sent to the customers:
1. Go to the Adobe Commerce Cloud console.
2. On the left panel, choose Marketing.
3. Click Email Templates.
4. In the table, nd the Template column, and click the DM Fail Transaction template row.
The Template Information page opens.
5. On the Template Information page, complete the required information in the template
name, subject, and content text boxes.
6. Click Save Template.

Conguring Cron Settings

Follow these steps to congure Cron settings for Decision Manager:
1. In the Adobe Commerce Cloud console.
2. On the left panel, click Stores.
3. Go to Conguration > Advanced > System > Cron (Scheduled Tasks).
4. Scroll down and click Cron conguration options for group:dm.
5. Complete the required elds.
6. Click Save Cong. For further instructions on how to congure Cron settings, see Cron
(scheduled tasks).

Cybersource Built by Us 30
Built by Us

Conguring Tokens
When a customer is logged in and is at checkout, their card data can be store in a secured
Cybersource data center. After the card data is saved, a token is provided to you through
this module. This token represents the customer record. When a returning customer uses
your checkout, they can opt to use a previously stored card so they don't have to enter
their card data again.
When a token is used, the customer is still redirected to the Cybersource Hosted Payment
page for payment conrmation. If a customer chooses to checkout as a guest, the token
system is not used.

Saving a Card for Later Use

To save the card, log in or register a new customer account. During the checkout process,
check the Save for later use box. After the order is placed, the card information is
securely saved with Cybersource.

Managing the Adobe Commerce Cloud Tokens

Customers who are logged into can delete their tokens at any time. To do so, they must
visit the My Account section of the Adobe Commerce Cloud and choose the Stored
Payment Methods menu item. Customers can use the delete links beside any stored
tokens to remove a stored token.

Paying with Tokens

To pay the order with a stored card, the customer chooses it from the list at the top of the
Billing and review checkout page.

Multi-Shipping Feature
The plugin supports the multi-shipping feature only for the Adobe Commerce Cloud
registered users when they place orders with stored credit cards.

Node Implementation
The plugin does not support multiple-node implementation.

Support
If you require support with this software, contact [email protected]
and provide this information:
1. Summary of the issue
2. Steps to reproduce the issue
3. Magento platform version
4. Cybersource plug-in version
5. Cybersource merchant ID
6. Conguration screenshots
7. All the themes/additional extensions installed

Cybersource Built by Us 31
Built by Us

8. Log les: system.log, debug.log, cybs.log and exception.log. To generate logs, navigate
to this path in the root directory of Magneto: Magento Folder Name\var\log

OpenCart
The plugin for OpenCart provides a payment solution for merchants using OpenCart to
manage their orders. This section describes the payment methods and services the Plugin
provides.

Supported payment methods

These are the supported payment methods for OpenCart:
• Credit and debit cards
• eCheck
• Click to Pay

Supported payment services

These are the supported payment services available for OpenCart:
• Payment acceptance services
• Authorization only
• Sale (bundled authorization and capture)
• Electronic check debit (sale) for eCheck payment method
• Order management services
• Capture an authorization (not for eCheck)
• Multiple partial captures (not for eCheck)
• Standard and partial refunds
• Standard and partial void captures (not for eCheck)
• Standard and partial void refunds
• Full authorization reversal (not for eCheck)
• Token Management Service (TMS) for credit and debit cards payments:
• Create payment token along with authorization
• Update an existing token along with authorization
• Update an existing token from My Account section
• Delete an existing token from My Account section
• Create payment token for new payment methods during checkout
• Make a payment with a stored token during checkout
• Reporting services that allow you to import theses Business Center reports into
OpenCart:
• Transaction Request Report
• Payment Batch Detail Report

Cybersource Built by Us 32
Built by Us

• Conversion Detail Report

Release Information
This section provides information about the releases for the plugin.

Release Version Release Date Support End Date

Version 22.1.0 October 25, 2022 October 14, 2025

Version 23.1.0 December 8, 2023 December 7, 2026

Version 23.1.0 includes the following enhancements:

• Updated authentication signature
• Added DAV enable/disable button for admin conguration
• Updated reCAPTCHA key generation tooltip URL
• Fix for target origin issue for different domain in the ex form capture context
• Compatible with OpenCart versions 3.0.3.7 and 3.0.3.8
Version 22.1.0
• Initial release.

Installation
Before you install the plugin, make sure that these requirements are met:
• You are using OpenCart version 23.1.0
• Have created a Business Center account and have generated Business Center REST API
keys:
• To create an account, go to the Business Center Registration website.
• To generate REST API keys, see Getting Started with the REST API Developer Guide.
Follow these steps to install the plugin:
1. Download the plugin from the OpenCart website to your local system.
2. Open OpenCart Back Ofce and from the Dashboard, choose Extensions > Installer.
3. Click Upload and browse to the le you downloaded to your local system.
The pane displays the status of the installation. After the Plugin is installed, the pane
indicates that the module is installed. You can close it or click Congure to congure
the Plugin.

Conguration Overview
This section describes how to set up the plugin.
The following table shows where to access the plugin conguration settings.
From the left navigation panel in OpenCart Back Ofce, select Extensions and follow the
path indicated in the table for the conguration settings you want to congure.

Cybersource Built by Us 33
Built by Us

Conguration Settings

Settings Path

General Conf Extensions > Extensions > Modules > Cybers

iguration Report Configurat ource Configuration
ion Order Status Configurat
ion
Unified Checkout Paymen Extensions > Extensions > Payments > Cybe
t Action Payer Authentica rsource Unified Checkout
tion Status
Sort Order Tokenizatio
n Limit Saved Card Rate
Enforce SCA for Saving Car
d
eCheck Status Extensions > Extensions > Payments > Cybe
Sort Order rsource eCheck

Enable Basic Conguration

This section describes the required and optional basic conguration settings for the
plugin.
To enable Basic Conguration, follow these steps:
1. In OpenCart Back ofce, navigate to Extensions > Extensions > Modules > Cybersource
Conguration.
2. Click the Edit icon.
3. In the General Conguration tab of the Edit Cybersource Conguration Module pane,
from the drop down list or text box, select or enter a setting.
4. Click the Save icon.
5. Repeat for each required setting and each optional setting you want to enable.

Required Settings
These settings are required for using the plugin:
Sandbox Mode Set to Enable to operate in Sandbox (T)
mode. You can test new changes in this
mode and no funds are affected.
Set to Disable to operate in Production
(Live) mode.
Merchant ID Enter the Business Center Merchant ID or
Organization ID, which is a unique identier
for the merchant.
Merchant Key ID Enter your REST Shared Secret Key
generated from within the Business

Cybersource Built by Us 34
Built by Us

Center. This specic key authenticates and

authorizes the merchant's integration with
the gateway.
Merchant Secret Key Enter the complimentary Secret key that
is generated at the same time as the
Merchant Key ID. It is used for secure
communication between the merchant's
online store and a payment gateway.

reCAPTCHA Site key For each request, this key returns a score
based on the user interactions with your
site. Based on these scores, you can take
appropriate actions for your site, such as
allowing or blocking users.
reCAPTCHA Secret key This key authorizes communication
between the plugin's backend and the
reCAPTCHA server to verify the user's
response. The secret key should be kept
safe for security purposes.

Optional Settings
These settings are optional for using the plugin.
Fraud Management Set to Enable to allow merchants to identify
and prevent fraudulent activities.
Delivery Address Verication Set to Enable to allow merchants to verify
the delivery address.
Device Fingerprint Set to Enable to allow merchants to identify
and track devices accessing an online store.
Developer ID Identier for the developer that helps
integrate a partner solution with
Cybersource. This settings is only required
for Cybersource System Integrators.
Status Set to Enable for the Cybersource
integration to be active and visible at
checkout.
Payment Action Set to Enable to enable card payments for
Authorize Only or Sale (Authorization and
Capture) for front ofce transactions.
Enhanced Logs Set to Enable to generate logs that can
be accessed by selecting Congure >
Advanced Parameters > Logs.

Cybersource Built by Us 35
Built by Us

Cybersource strongly recommends you map your Order Status responses to your
preferred order status under the Order Status Conguration section.

Enable Unied Checkout

This section describes the required and optional conguration settings for Unied
Checkout for the plugin.
To enable Card Payment follow these steps:
1. In OpenCart Back ofce, navigate to Extensions > Extensions > Payments >
Cybersource Unied Checkout.
2. Click the Edit icon.
3. In the Edit Cybersource Unied Checkout pane, from the drop down list or text box,
select or enter the setting you want.
4. Click the Save icon.
5. Repeat for each required setting and each optional setting you want to set.

Required Settings
The following settings are required:
• Enable Basic Conguration on page 34
The following settings are required for enabling Unied Checkout for the plugin:
Payment Option Label Enter the text you want displayed to the
customer at checkout.

Allow Card Types Select the card types that you want to
accept.

Optional Settings
The following settings are optional for enabling Unied Checkout for the plugin:
Status Set to Enable for the Cybersource
integration to be active and visible at
checkout.
Sort Order Order in which a payment method displays
at checkout.

Enable Tokenization
This section describes the required and optional conguration settings for Tokenization
for the plugin.
To enable Tokenization follow these steps:
1. In OpenCart Back ofce, navigate to Extensions > Extensions > Payments >
Cybersource
Unied Checkout.
2. Click the Edit icon.

Cybersource Built by Us 36
Built by Us

3. In the Edit Cybersource pane, from the drop down list or text box, select or enter the
setting you want.
4. Click the Save icon.
5. Repeat for each required setting and each optional setting you want to set.

Required Settings
The following settings are required:
• Enable Basic Conguration on page 34
• Enable Unied Checkout on page 36
The following setting is also required for enabling Tokenization for the plugin:
Tokenization Setting allows customers to save cards for
future use while making a card payment.

Optional Settings
The following settings are optional for enabling Tokenization for the plugin:
Network Token Updates Enable this setting to subscribe to Network
Token life cycle updates.
Limit Saved Card Rate With this setting enabled, a limit is set to
save only a specied number of cards in
the My Account section in Front Ofce.
There are two settings: Saved Card Limit
Count: Number of cards that can be saved
in a certain period of time. Saved Card Limit
Time Frame: Number of hours that saved
card attempts are counted.
Enforce SCA for Saving Card If enabled, card holders are 3DS challenged
when saving a card.

Enable Fraud Management

This section describes the required and optional conguration settings for Fraud
Management for the plugin.
To enable Fraud Management follow these steps:
1. In OpenCart Back ofce, navigate to Extensions > Extensions > Modules > Cybersource
Conguration.
2. Click the Edit icon.
3. In the General Conguration tab of the Edit Cybersource Conguration Module pane,
from the drop down list or text box, select or enter the setting you want.
4. Click the Save icon.
5. Repeat for each required setting and each optional setting you want to enable.

Cybersource Built by Us 37
Built by Us

Required Settings
The following settings are required:
• Enable Basic Conguration on page 34
• Enable Unied Checkout on page 36
The following settings are also required for enabling Fraud Management for the plugin.
• Fraud Management
• Device Fingerprint (not technically required, but highly recommended)

Optional Settings
The following setting is optional for enabling Fraud Management for the plugin:
Conversion Detailed Report This report (enabled in the Report
Conguration tab) pulls Case Management
changes from Cybersource at regular
intervals to ensure orders are kept updated
within OpenCart.

Enable 3-D Secure (Payer Auth)

This section describes the required and optional conguration settings for 3-D Secure
(Payer Auth) for the plugin.
To enable 3-D Secure follow these steps:
1. In OpenCart Back ofce, navigate to Extensions > Extensions > Payments >
Cybersource Unied Checkout.
2. Click the Edit icon.
3. In the Edit Cybersource pane, select from the dropdown or specify in the text box the
conguration setting option you want to set.
4. Click the Save icon.
5. Repeat for each required setting and each optional setting you want to enable.

Required Settings
The following settings are required:
• Enable Basic Conguration on page 34
• Enable Unied Checkout on page 36
The following setting is also required for enabling 3-D Secure for the plugin:
Payer Authentication When this setting is enabled, an extra layer
of security is added at checkout.

Optional Settings
The following setting is optional but recommended for regions enforcing 3-D Secure for
the plugin:

Cybersource Built by Us 38
Built by Us

Enforce SCA for Saving Card When this setting is enabled, card holders
are 3-D Secure challenged when saving a
card.

Enable eCheck
This section describes the required and optional conguration settings for eCheck for the
plugin.
To enable eCheck follow these steps:
1. In OpenCart Back ofce, navigate to Extensions > Extensions > Payments >
Cybersource eCheck.
2. Click the Edit icon.
3. In the Edit eCheck pane, from the drop down list or text box, select or enter the setting
you want.
4. Click the Save icon.
5. Repeat for each required setting and each optional setting you want to enable.

Required Settings
The following settings are required:
• Enable Basic Conguration on page 34
• Enable Unied Checkout on page 36
The following setting is also required for enabling eCheck for the plugin:
Status With this setting enabled, eCheck is active.

Optional Settings
The following setting is optional but recommended for enabling eCheck for the plugin:
Sort Order Order in which a payment method displays
at checkout.

Enable Reporting
This section describes the required and optional conguration settings for Reporting for
the plugin.
To enable Reporting follow these steps:
1. In OpenCart Back ofce, navigate to Extensions > Extensions > Modules > Cybersource
Conguration.
2. Click the Edit icon.
3. In the Report Conguration tab of the Edit Cybersource Conguration Module pane,
from the drop down list or text box, select or enter the conguration setting you want.
4. Click the Save icon.
5. Repeat for each required setting and each optional setting you want to enable.

Cybersource Built by Us 39
Built by Us

Required Settings
The following settings are required:
• Enable Basic Conguration on page 34
• Enable Unied Checkout on page 36
The following settings are also required for enabling Reporting for the plugin:
Payment Batch Detail Report This report includes transactions that
are processed with the applications. This
report is available shortly after captured
transactions are batched.
When set to Enable, this report is
downloaded from the Business Center to
OpenCart. The report is downloaded by
default to different locations, depending on
the mode in which OpenCart is operating:
• In Sandbox (Test) mode,
the report downloads to
{OpenCartModuleInstallationDirectory}/
cybersourceofcial/Reports/Sandbox
• In Production (Live) mode,
the report downloads to
{OpenCartModuleInstallationDirectory}/
cybersourceofcial/Reports/Production.

Important
Cybersource strongly recommends
that OpenCart and the Business
Center operate in the same time
zone so that the Transaction
Request Report and Payment Batch
Detail Report work properly.

Transaction Request Report This report includes details for individual

transactions that are processed each day.
When set to Enable, this report is
downloaded from the Business Center to
OpenCart. The report is downloaded to
different locations, depending on the mode
in which OpenCart is operating:
• In Sandbox (Test) mode,
the report downloads to
{OpenCartShopModuleInstallationDirectory}/
cybersourceofcial/Reports/Sandbox

Cybersource Built by Us 40
Built by Us

• In Production (Live) mode,

the report downloads to
{OpenCartModuleInstallationDirectory}/
cybersourceofcial/Reports/Production.

Important
Cybersource strongly recommends
that OpenCart and the Business
Center operate in the same time
zone so that the Transaction
Request Report and Payment Batch
Detail Report work properly.

Optional Settings
The following settings are optional but recommended for enabling Reporting for the
plugin:
Download path If you want to download the report to a
path other than the default, specify that
path here.
Conversion Detail Report When set to Enable, this report pulls Case
Management changes from the Business
Center at regular intervals to ensure orders
are updated in OpenCart.

Enforcing Strong Customer Authentication

Select the Enforce Strong Customer Authentication setting to prompt a 3-D
Secure (3DS) challenge when a customer saves their credit card information.
The customer is 3DS challenged when a transaction is declined as reported
by response code 478 (Strong Customer Authentication required). After the
transaction is declined, another request is sent for the same order.

Important
The Enforce Strong Customer Authentication setting is only available when the
Payer Authentication/3-D Secure (General Plugin setting) and Tokenization (Fraud
Management Plugin setting) are enabled. See Enable 3-D Secure (Payer Auth) on
page 38 and Enable Tokenization on page 36 for information about enabling
these settings.
Follow these steps to enable Enforce Strong Customer Authentication:
1. Open OpenCart Back Ofce and select Extensions > Extensions > Payments >
Cybersource Unied Checkout.

Cybersource Built by Us 41
Built by Us

2. Select the Edit icon.

3. From the drop down menu next to Enforce SCA for Saving Card, select Enable.
4. Click the Save icon.

Scheduling Report Generation

Schedulers on a Linux, Mac, or Windows system are used to set up how often a specied
report is generated. Schedulers for Linux and Mac systems are set up using a Cron Tab.
The scheduler for a Windows system is set up using the Windows Task Scheduler app.
When setting up a schedule for generating a specic report, use this format:
• Format: <shop domain name>/module/cybersourceofcial/paymentReport
• Example: http://www.opencart_1.7.8.6.com/module/cybersourceofcial/paymentReport

Cron Tab Syntax for Mac and Linux Systems

When setting up the reporting schedule on a Linux or Mac system, you use crontab
commands that determine how often and when the report is generated.
The syntax is:

* * * * * [command]

The asterisk (*) represents each of these timing parameters:

• Minute (0-59)
• Hour (0-23)
• Day of Month (1-31)
• Month (1-12)
• Day of week (0-6), (0-Sunday)
For example, these timing parameters indicate how often a specied report is generated:
• * * * * * [command]: Runs every minute of every day of every week of every month.
• 0 * * * * [command]: Runs every hour of every day of every week of every month.
• 30 2 * * * [command]: Runs at 2:30 a.m. every day of every week of every month.
• 0 0 2 * * [command]: Runs once a month every month on the second day of the month.
• 0 * * * 1 [command]: Runs every Monday at every hour.
• 0,10,20 * * * * [command]: Runs on 0, 10, 20 minute of every hour of every day of every
week of every month.
• 0 5-10 * * * *[command]: Runs every hour between 5 and 10 a.m.
• @reboot [command]: Runs every time after the server reboots.
• */5 * * * * [command]: Runs every 5 minutes of every day.

Setting Up Cron Scheduler for Linux

1. Open a Linux terminal.

Cybersource Built by Us 42
Built by Us

2. Enter crontab-e to enter editor mode. For example:

root@OpencartQA4:/etc# crontab -e

3. Enter the command to set the timing for the cron job. For example, this command sets
the cron job to run every 15th minute of every hour, every day, every week, and every
month:

15 * * * * curl https://www.dev.opencart.cybsplugin.com/mps1760/module/mybank/paymentReport

4. Enter Ctrl + X to close the editor.

5. Enter the crontab -l command to check the scheduled cron job. For example:

root@OpencartQA4:/etc# crontab -l

The scheduled cron job should appear on the screen. For example:

15 * * * * curl https://www.dev.opencart.cybsplugin.com/mps1760/module/mybank/paymentReport

Setting Up Cron Scheduler for Mac

1. Open a Mac terminal.
2. Enter crontab-e to enter editor mode.

C02X63PRJG5J:~ $crontab -e

3. Enter the command to set the timing for the cron job. For example, this command sets
the cron job to run every 45th minute of every hour, every day, every week, and every
month:

45 * * * * curl https://www.qa.opencart.cybsplugin.com/mps1786/module/cybersourceofcial/
paymentReport

4. Enter Esc + : + w + q to close the editor. The editor closes and displays this message:

crontab: installing new crontab

5. Enter the crontab -l command to check the scheduled cron job.

C02X63PRJG5J:~ $crontab -l

The scheduled cron job should display on the screen. For example:

45 * * * * curl https://www.qa.opencart.cybsplugin.com/mps1786/module/cybersourceofcial/
paymentReport

Setting Up Task Scheduler for Windows

1. Open the Task Scheduler app and click Create Task.
The Create Task pane displays.
2. Select the General tab and enter a name for the task in the Name eld.
3. Select the Triggers tab and click New.

Cybersource Built by Us 43
Built by Us

The New Trigger pane displays.

4. Make the desired timing selections for the task in the New Trigger pane and click OK.
5. Select the Actions tab in the Create Task pane and click New.
The New Action pane displays.
6. Select and enter this information in the New Action pane and click OK.
• Action drop-down menu: choose Start a program.
• Program/script eld: enter the curl command.
• Add arguments (optional): enter the reporting URL.
7. Click OK in the Create Task pane to create the task. The new task displays in the Task
Scheduler Summary.

Using the Plugin

The plugin provides merchants a frictionless way to process payments, prevent fraud, and
generate reports within the Business Center while making it easy for customers to place
and cancel orders, and save or update stored credit or debit card information.

Order Management
This section describes the order management process that occurs after a customer
places an order.
The order management process is handled using these OpenCart ofce interfaces:
• OpenCart Front Ofce: customers use this interface to place and cancel orders, and
save or update stored credit or debit card information.
• OpenCart Back Ofce: merchants use this interface to congure the Plugin and
manage orders, which includes these tasks:
• Capture an authorization (multiple partial captures are also supported).
• Reverse an authorization (full authorization is supported).
• Void a capture (standard and partial voids are supported).
• Refund a capture (standard and partial refunds are supported).
• Void a refund (standard and partial voids are supported).
Merchants also use the Back Ofce interface to congure fraud management and
reporting services.
Order Status
Order status is triggered and updated when transactions are processed. The plugin
supports custom and default status states for orders.
Custom order status states:
• Cancel error
• Canceled
• Canceled Reversal
• Chargeback
• Complete
• Denied

Cybersource Built by Us 44
Built by Us

• Expired
• Failed
• Order cancelled by merchant
• Partial Refunded
• Partial Voided
• Payment error
• Payment pending for review
• Pending
• Processed
• Processing
• Refund Error
• Refunded
• Reversal
• Shipped
• Void Error
• Voided
Default order status states:
• Processed
• Canceled
• Shipped
• Delivered
• Refunded
Only the shipped and delivered status states can be manually updated.
Order Management Workows
This section describes the order of events that the merchant completes after a customer
submits an order.
After-Authorization Workow
This workow comprises the sequence of events that occur after a customer places a
new order using OpenCart Front Ofce. The workow shows how the order status is
updated when the authorized transaction is captured or reversed (full authorization
reversal).
1. The new order displays in OpenCart Back Ofce and the order status is Pending.
2. The merchant chooses one of these actions:
• Standard capture.
• Partial capture.
• Cancel products. For a full authorization reversal, the merchant must also cancel the
order, which requires that they select all the quantities and all the items included in
the order.
A partial authorization reversal is not supported.
3. When the merchant initiates a full authorization reversal, the authorization is cancelled
and the order status is set to Order cancelled by merchant.

Cybersource Built by Us 45
Built by Us

4. When the merchant initiates a multiple partial capture, they choose how many
quantities to capture and whether to include the shipping costs.
After multiple partial captures are processed, the order status is set to Processing.
5. When the merchant initiates a full capture, the entire authorization amount is captured
and the order status is set to Processed.
After-Capture Workow
This workow comprises the sequence of events that occur after an authorization is
captured. The workow shows how the order status is updated when the captured
transaction is refunded or voided.
1. The merchant selects one of these actions:
• Standard refund.
• Partial refund.
• Void capture.
2. If the merchant voids the capture, the captured transactions are voided.
When all quantities of the transaction are captured, the entire order is voided and the
order status is set to Payment cancelled.
If only a few quantities are captured, only the captured quantities are voided and the
order status is set to Partial payment accepted.
3. If the merchant initiates a standard refund before updating the order status to shipped,
the order status is set to Partial refunded (before shipped) until the refunded amount
becomes equal to the captured amount. When the refunded amount becomes equal to
the captured amount, the order status is set to Refunded.
4. When the merchant selects a refund after updating the order status to shipped, the
order status is set to Partial refunded (after shipped) until the refunded amount
becomes equal to the captured amount. When the refunded amount becomes equal to
the captured amount, the order status is set to Refunded.
To refund the amount of an order, merchants can either generate a voucher or a credit
slip for the refund. Depending on the type of refund they select and whether they issue
a voucher or a credit slip, one of these actions occurs:
• When the merchant chooses Generate a voucher for a partial refund, the sum of the
items is not refunded. Instead, a voucher is generated that can be used for future
transactions.
• When the merchant chooses Generate a voucher and enters the amount in the
shipping costs eld for a partial refund, then a voucher equal to the sum of the items
and the shipping amount is generated.
• When the merchant chooses Generate a credit slip for a standard refund, the sum of
the items is refunded.
• When the merchant chooses both Generate a credit slip and Repay shipping costs for
a standard refund, the sum of the items and the shipping amount are both refunded.
• When the merchant chooses both Generate a voucher and Repay shipping costs for
a standard refund, a voucher equal to the sum of the items and shipping amount is
generated.

Cybersource Built by Us 46
Built by Us

• When the merchant chooses both Generate a voucher and Generate credit slip for a
standard refund, a voucher is generated and a refund for the sum of the items is not
generated.
After-Refund Workow
This workow comprises the sequence of events that occur when the merchant voids a
refund under specic conditions:
• When the refund is processed before the order is shipped, the refund is cancelled and
the order status is set to Voided or Partially Voided.
• When the refund is processed after the order is shipped, the refund is cancelled and
the order status is set to Voided or Partially Voided.
• When the voided refund amount is equal to the refund amount, the refund is cancelled
and the order status is set to Voided or Partially Voided.

Important
OpenCart does not provide an option to return Gift Certicates. For orders
associated with Gift Certicates, the services mentioned below are not available:
• Front Ofce Cancel
• Back Ofce Cancel
• Void a Capture

Customer Tasks
Customers can use the My Account option on the merchant's OpenCart website to
manage orders and their payment information. The following sections contain the steps to
complete these tasks.
Saving Credit/Debit Card Information

Saving card information enables customers to use that information for

future transactions. Using OpenCart Front Ofce, customers can save their
card information during the checkout process, or they can add their card's
information to their registered OpenCart accounts using the Cybersource
My Cards feature.
If a customer wants to save their card information during the checkout process, they can
select the Save my card for future payment option when entering their credit/debit card
payment during checkout.
The card information can also be saved using the Cybersource My Cards page in
OpenCart:
1. Open OpenCart Front Ofce.
2. Click My Account > Managed Stored Credit Cards > Cybersource My Cards > Add New
Card.
If there is no current address associated with the customer account, the customer is
prompted to add an address. The customer can enter the required address information
and click Save.

Cybersource Built by Us 47
Built by Us

If there is already an address associated with the customer account, the customer can
select and use the address or add a new address.
After the address information is complete and selected, the customer can update the
card expiration information, if needed, or delete the existing card from the account.
3. To update the expiration information (expiration month/year) for the card, under Saved
Cards the customer clicks the blue arrow beneath More, then clicks either Update, or
Delete to remove the card from the account.
Customers can only add the number of cards that the merchant specied in the
account conguration. The updated card information is tokenized and securely saved.
The customer can use the saved card information for future transactions without
having to enter that card information during the checkout process.
Selecting a Default Credit/Debit Card

When a customer has multiple cards associated with their account, they can
designate the default card. By default, the rst card added to the account
will be set as the default card. In the Cybersource My Cards page, the default
card is identied using an asterisk (*) that appears to the right of the card
number.
To change the default card, the customer follows these steps:
1. Open OpenCart Front Ofce.
2. Open the Cybersource My Cards page. The page displays the saved cards associated
with the account.
3. Choose the card to set as the default card and select More > SET AS DEFAULT. The card
is set as the default card.
The default card cannot be deleted unless all other saved cards from the Cybersource
My Cards section are deleted.
Cancelling an Order

This task provides the steps a customer takes to cancel an order. They
cannot cancel an order if the order is in review with the merchant. The
Cancel option is also not available in direct Settlement for Captured and
eCheck orders.
1. Open OpenCart Front Ofce.
2. Select My Account > Order History. The Order history page displays the customer's
orders.
3. Select the View icon for the order. The Order details page appears.
4. Click the Cancel Order icon to cancel the order.
A Cancel Order conrmation notice appears.
5. Click Yes on the Cancel Order conrmation notice to cancel the order.
Above the Order History, a notication appears stating Success: Entire order was
successfully cancelled. The order is cancelled and the order status is set to Canceled.
If the order was a sales transaction or was captured, the cancellation is sent to the
merchant and the status is set to Canceled.

Cybersource Built by Us 48
Built by Us

After the customer cancels an order, the merchant can accept or reject the order
cancellation (as instructed in Processing a Cancelled Order on page 49).
If the merchant accepts the cancellation request, a refund for the order amount
is initiated and the order status is set to Refunded. If the merchant rejects the
cancellation request, the order status is set to Denied.

Merchant Tasks
Merchants use OpenCart Back Ofce to manage orders. This section describes the steps
to complete these tasks.
Processing a Cancelled Order

When a customer cancels an order, a request is sent to the merchant and the
order status is set to Cancelled. Merchants can accept or reject an order
that a customer cancels.
1. Open OpenCart Back Ofce and select Orders from the Dashboard.
2. Locate and select the checkbox next to the order the customer cancelled.
3. Click the View icon. Under Order Details, the information for that order displays.
4. Under Add Order Status, choose the order status that describes your processing of the
cancellation.
Processing a Merchandise Return

When a customer requests to return merchandise, the information appears

on the Merchandise Returns page in OpenCart Back Ofce. Follow these
steps to process the return.
1. Open OpenCart Back Ofce and select Sales > Returns. The Product Returns page
displays and identies the order or orders for which customers have requested a
return.
2. Select the check box next to the order for which you want to process the return. Then
click the Edit icon. The Edit Product Return page displays.
3. In the Product Information and Reason for Return pane, choose one of these options
from the Return Action drop-down menu:
• Credit issued
• Refunded
• Replacement Sent
The status is updated for the order on the Merchandise Returns page. Next, you can
proceed with selecting a return or refund option for the order.
4. Select Orders from the Dashboard.
5. Select the order for which you want to process a return, and select one of these
options:
• Return products
• Partial refund

Cybersource Built by Us 49
Built by Us

Fraud Management
The plugin provides fraud management functionality for merchants who also use the
Business Center. You can apply fraud management functionality to transactions when:
• Fraud management is enabled in the plugin.
• You have a fraud management prole in the Business Center.
Fraud screening includes these features:
• Fraud Management Essentials (FME): used to enforce the rules created by Cybsource
Machine Learning System (MLS). Fraud management is used to dene the merchant’s
rules.
• Fraud Management Rules:
• When the decision status from the Business Center is
AUTHORIZED_PENDING_REVIEW or PENDING_REVIEW, the order is in review and the
order status is set to Payment pending for review.
• When the decision status from the Business Center is AUTHORIZED_RISK_DECLINED,
the order is rejected and the order status is set to Order cancelled by merchant.
The table below describes the possible decisions, outcomes, and timing Decision Manager
uses when an order is triggered for review.

Important
When these transactions are in a Decision Manager review state, certain
settlement considerations apply:
• For authorizations: while accepting this transaction it is not recommended
to settle it in the Business Center. When the transaction is settled in the
Business Center, the follow-on services initiated from OpenCart Back Ofce
are impacted.
• For sales:
• The entire authorized amount should be settled in the Business Center when
accepting the transaction. When the settlement is not performed in the
Business Center, the follow-on services initiated from OpenCart Back Ofce
fail.
• A follow-on void capture will not trigger from OpenCart Back Ofce. While
accepting review transactions, merchants should not select the settle option.

Decision Manager Decisions, Execution Timings, and Outcomes for Orders

Decision Execution Timing Outcome of Decision

Monitor Before authoriza Authorization will be successful and no ac

tion tion from the Decision Manager is required. Use this de
cision to understand the outcome of a rul
e.

Cybersource Built by Us 50
Built by Us

Decision Execution Timing Outcome of Decision

Accept Before authoriza The order is processed normally and is pla

tion ced successfully.
Review Before authoriza The authorization is successful, and follo
tion w-on services are put on hold until the merchant accep
ts or rejects it. The order status will be se
t to Payment pending for review.
Reject Before authoriza The order is rejected and the authorization
tion is not processed. The merchant is not able to view the
order in OpenCart Back Office.
Monitor After authorizati The authorization is successful and no ac
on tion from Decision Manager is required. Use this decisio
n to understand the outcome of a rule.
Accept After authorizati The order is processed normally and placed
on successfully.
Review After authorizati The authorization is successful, and follo
on w-on services are put on hold until the merchant accep
ts or rejects it. The order status is set to
Payment pending for review.
Reject After authorizati The original authorization is successful an
on d then is automatically reversed and the order status is
set to Order cancelled by merchant.

Reporting
The plugin provides reporting functionality for merchants who also use the Cybersource
Business Center. You can import these reports from the Business Center into OpenCart:
• Transaction Request Report: includes details for individual transactions that are
processed each day.
• Payment Batch Detail Report: includes transactions that are processed with the
applications. This report is available shortly after captured transactions are batched.
• Conversion Detail Report: includes Case Management changes recorded in the
Business Center to ensure that updated orders are also included in OpenCart. This
report is generated at regular intervals and includes the results of the converted
orders for each reviewer. This information provides an overview of all orders that were
not immediately accepted.

Scheduling
The Plugin reporting functionality works with a system scheduler to generate and update
reports for OpenCart. There are some Cron Job modules available for OpenCart, such
as the Cron Tab, that support reporting. Merchants can use any Cron Job module that
OpenCart supports, or any other online Cron service provider to generate reports.

Cybersource Built by Us 51
Built by Us

See Scheduling Report Generation on page 42 for information about how to

schedule report generation.

Workow
The reports are processed and orders are updated in OpenCart using this workow:
1. Orders with an AUTHORIZED_PENDING_REVIEW or AUTHORIZED_RISK_DECLINED
status are included in the ps_cybersourceofcial_order table in the OpenCart
database.
2. If a review is trigged for an order based on the prole rule in Decision Manager, a
Payment pending for review order status displays for that order on the OpenCart Back
Ofce Orders page.
3. The merchant uses the Business Center to accept the order that is in review, and,
if not already enabled, enables the reports using the Report Settings on the Plugin
Conguration page.
4. The scheduler runs the report at regular intervals according to the intervals the
merchant congured. The order is accepted or rejected by the merchant in the
Business Center, is retrieved, and the new status is updated as AUTHORIZED or
DECLINED. The updated order status displays in the op_cybersourceofcial_order
table in the OpenCart database.
5. The original decision and the new decision are updated and displayed in the
op_cybersourceofcial_conversion_detail_report table in the OpenCart database.
6. The order is updated as Awaiting payment status for the authorization and displayed on
the OpenCart Back Ofce Orders page. The payment is accepted for the sale and any
associated follow-on transactions (capture, void capture, refund, void refund, and full
authorization reversal).

Testing
If you have not done so already, congure these settings using OpenCart
Back Ofce:
• General Settings: merchant ID, merchant key ID, and/or merchant secret key
• Payment Settings: applicable payment methods
After conguring the Plugin, complete this task to test the conguration
using OpenCart Front Ofce to place an order and OpenCart Back Ofce to
manage the order.
1. Open OpenCart Front Ofce to place an order.
2. At Checkout, enter any required personal information and select the payment method
you want to use to place the order.
3. Enter the card information you want to use to place the order and click Conrm Order.
If the order is successful, an order conrmation message displays.
4. Open OpenCart Back Ofce to manage the order.
5. Select Orders from the Dashboard. The Orders page displays and lists all active orders.

Cybersource Built by Us 52
Built by Us

6. Select the checkbox next to the order you processed in Step 1. Then click the View icon.
The order status for the order should display Pending.
7. Click Capture to capture the authorized amount, then Yes. The order status changes to
Processed.
8. Click Partial capture to capture part of the authorized amount. The order status
changes to Processing.
9. Click Cancel to cancel the order. The order status changes to Order Cancelled by
Merchant.
For more information about testing, including test cards, see https://
developer.cybersource.com/hello-world/testing-guide-v1.html

Upgrading
You can install a newer version of the plugin using OpenCart Back Ofce.
1. To uninstall Cybersource Payment, navigate to Extensions > Extension Types > Payments
and then uninstall all of the Cybersource payment modules.
2. To uninstall Cybersource Tax, under the same Extension dropdown, select Order Totals
and uninstall Cybersource Tax.
3. To uninstall the Cybersource Payment extension, under the Extension dropdown, select
Modules, and uninstall the Cybersource Payment extension.
4. Navigate to the Extensions tab and click Installer, then click Delete to remove the
Cybersource extension.
5. Navigate back to the Extensions tab and click Modication, then click Refresh.
6. To install the new Cybersource Payment extension, follow the steps mentioned in
Installation on page 33.

Troubleshooting Assistance
For help with troubleshooting, contact [email protected] and provide
the following information:
• Summary of the issue
• Steps needed to reproduce the issue
• Platform version
• Plugin version
• Platform Merchant ID
• Conguration screenshots
• List of themes/additional extensions installed
• Log le and any other data or screenshots related to the issue

Cybersource Built by Us 53
Built by Us

Oracle NetSuite
Cybersource services can be integrated with Oracle NetSuite to simplify your payment
management platform. This section describes the payment methods and services that the
Cybersource SuiteApp for Oracle NetSuite bundle provides.

Payment Acceptance Services

The bundle supports payment acceptance services that the customer initiates
(authorization and sale), and order management services that the merchant handles for
credit and debit cards (capture, credit, authorization reversal).
The bundle includes these credit and debit card services:
• Authentication
• Authorization only
• Authorization reversal
• Capture
• Credit
• eCheck
• Refund
• Sale (authorization and capture)
• Tokenization (TMS and network tokenization)
For the Cybersource Automatic Clearing House (ACH) service, the bundle supports
payment acceptance services that the customer initiates (authorization and sale), and
order management services the merchant handles(refund). The bundle also supports the
tokenization service for ACH.

Order Management Services

The bundle supports order management services for Apple Pay, Google Pay, PayPal, and
Click to Pay. Order management services support these operations for payment methods
Apple Pay, Google Pay, PayPal, and Click to Pay:
• Authorization reversal
• Capture
• Credit
• Sale (supported for Click to Pay and for PayPal as a workaround for multi-capture
functionality)
You must import authorizations that are processed outside of Oracle NetSuite to see
details of those authorizations using live integrations or CSV imports. For Click to Pay, the
PNRef number eld of the sales order should hold the details of the authorization ID and
Visa order ID in the format of AuthorizationID_VisaOrderID. For PayPal, the PNRef number
eld of the sales order should hold the details of the authorization ID and order ID in the
format of AuthorizationID_OrderID.

Cybersource Built by Us 54
Built by Us

Reporting Services
You can import these reports from Cybersource into Oracle NetSuite:
• Transaction Request Report
• Payment Batch Detail Report
• Conversion Detail Report

Invoicing Services
These invoicing actions can be generated in Oracle NetSuite and imported from
Cybersource:
• Creating a draft invoice
• Create an invoice without sending it
• Create and sending an invoice immediately

Processor Support
The Cybersource SuiteApp for the Oracle NetSuite bundle supports all processors
available through Cybersource. Additional features are available for these processors:
• Chase Paymentech Solutions: Level II and Level III supported for all card brands.
• FDC Nashville Global: Level II and Level III supported for all card brands.
• Global Payments: Level III supported for all card brands, and Level II supported only for
American Express, Diners Club, Discover, JCB, and Maestro.
• OmniPay Direct: Level III supported only for all card brands, and Level II supported for
American Express, Diners Club, Discover, JCB, and Maestro.
• TSYS Acquiring Solutions: Level II and Level III supported for all card brands.
• Credit Mutuel-CIC: Level II and Level III supported for all card brands.
• Elavon Americas: Level III supported for all card brands, and Level II supported only for
American Express, Diners Club, Discover, JCB, and Maestro.
• Barclays: Level III supported only for all card brands using REST, and Level II is not
supported.

Release Notes
This section provides information about functionality, bug xes, and enhancements for the
Cybersource SuiteApp for Oracle NetSuite integration.

January 2024
Cybersource Version 23.5.0 is compatible • Stripping of unsupported characters in
with Oracle NetSuite 2023.2 or earlier billTo and shipTo
• Web sec code support for ACH
transactions
• Line item support for basic transactions
• Barclaycard processor L3 support

Cybersource Built by Us 55
Built by Us

• Deprecation of delete scenario for

network tokens
• 3-D Secure enhancements – device
information
• Decoupling of bundled Payer
Authentication requests
• Bug x for ACH quantity eld in REST
• Bug x for delay shipment with partial
capture
• Bug x for PayPal multi-capture
• Bug x for delay shipment without multi-
currency feature
• Notice of SOAP and Secure Acceptance
deprecation in August 2024
• Partner Solution IDs update
• Conguration Guide update

September 2023
Cybersource Version 23.4.0 is compatible • SCA enhancements
with Oracle NetSuite 2023.2 or earlier • Source based PS ID
• Map NS ID on reporting records
• Payment facilitator support
• Network tokenization
• Bug x for delay shipment handling with
foreign currency
• Bug x for declined sale operations
accepted in Oracle NetSuite when using
SOAP
• Company name support in payment
acceptance and order management
• Update to Cybersource authentication
signature
• Partner solution IDs update

August 2023
Cybersource Version 23.3.1 is compatible • BFN certication for Oracle NetSuite
with Oracle NetSuite 2023.2 or earlier 2023.2 release
• Bug x for Mastercard level III sale for
TSYS
• Bug x for special character support for
REST

Cybersource Built by Us 56
Built by Us

• Company name support for Pay by Link

• Support for hold transaction reason
codes multi-select eld
• Fix for subtotal not calculating on Pay by
Link
• Auto-cancel pending secure acceptance
invoice payments
• Fix for unexpected token < in JSON in the
user event script
• Fix for incorrect elds being passed for
MOTO CIT

July 2023
Cybersource Version 23.3.0.1 is compatible • Patch x for anti-clickjacking
with Oracle NetSuite 2023.1 or earlier

June 2023
Cybersource Version 23.3.0 is compatible • Alternative payment methods using REST
with Oracle NetSuite 2023.1 or earlier approach (PayPal)
• Raw request/response rendering (the
formatting on the raw request/response
elds on the payment event records
are removed to overcome the Oracle
NetSuite eld character limit from
version 23.3.0 onwards.)
• SuiteApp optimization
• Invoicing roll-up feature (requires
custom transaction feature to be
enabled)
• Invoicing alternate email eld sourcing
(requires custom transaction feature to
be enabled)
• HTML in saved search formula x
• Webstore invoice URL eld support
for invoice payments through secure
acceptance
• Bug x for REST reason code mapping
• Reinstate dummy billing email address
• Transaction request report by date
search
• Payment batch detail report mapping to
Oracle NetSuite transaction

Cybersource Built by Us 57
Built by Us

• Partner solution ID update

• Conguration guide update

March 2023
Cybersource Version 23.2.0 is compatible • 3-D Secure 2.0 support
with Oracle NetSuite 2023.1 or earlier • SA invoice payment reject scenario x
• SA bug x for alphanumeric transaction
IDs
• log.error issue workaround
• Customer name special character issue
x
• Partner solution ID updated
• Conguration guide updated

January 2023
Cybersource Version 23.1.0 is compatible • REST support for credit and debit card,
with Oracle NetSuite 2022.2 or earlier credit and debit card token, ACH, ACH
token, Visa checkout, Apple Pay, Google
Pay
• Transaction level downgrade feature
• Invoice payment through webstore
feature
• $0 item ltering for sale transaction
requests update
• Secure acceptance request/response on
same payment event update
• Provided support for merchant initiated
transaction for REST API
• Started supporting abbreviation instead
of full name for unit of measure
• Partner solution ID updated
• Conguration guide updated

September 2022
Cybersource Version 22.2.2 is compatible • AVS CVN international support
with Oracle NetSuite 2022.2 or earlier • Secondary tax issue xed for invoice
• Secure acceptance tokenization
transaction support
• Hold transaction reason codes for
secure acceptance

Cybersource Built by Us 58
Built by Us

• Void transaction error xed

• ACH default SEC code support
• Reporting elds mapping updated
• Field validation updated
• Conguration guide updated

September 2021
Cybersource Version 22.2.1 is compatible • Added Level II and III support on
with Oracle NetSuite 2022.2 or earlier transaction level
• Strong customer authentication
implementation for secure acceptance
• Enhanced secure acceptance ow
• getAddressee issue xed
• Secure acceptance cancel pending
transaction time gap customization
• Conguration guide updated
• Dummy default billing email address
functionality removed

Cybersource Version 22.2.0 is compatible • External MIT initial authorization support

with Oracle NetSuite 2022.1 or earlier in Oracle NetSuite
• Redirect message display for external
checkout transaction
• AVS/CVN response code display in
Oracle NetSuite for sale transactions
• Payment import optimization for Pay by
Link invoicing feature
• $0 shipping and handling issue x for
customer deposit
• SuiteApp installed version display on
SuiteApp conguration page
• Payment method mapping simplication
• Default merchant ID and invoice create
action support for Pay by Link invoice
feature
• Default Cybersource invoice ID to Oracle
NetSuite invoice number support Pay by
Link invoice feature
• ACH and ACH token (as general token)
transaction support in Oracle NetSuite
• Auth response issue x
• ShipTo addressee issue x

Cybersource Built by Us 59
Built by Us

• Conguration guide updated

SuiteApp Installation and Update

You must have a Business Center account to install the SuiteApp integration.
Go to the Business Center Registration website to create an account. Follow the email
instructions that you received to activate your merchant account, and then log in to the
Business Center to complete the registration process.
From your Business Center account, you also need your merchant key ID and shared
secret key to enable the integration with Oracle NetSuite. For steps on how to generate a
shared secret key, see Creating a Shared Secret Key Pair. Store your merchant key ID and
shared secret key for later use.

Installing SuiteApp
Follow these steps if you are installing Cybersource SuiteApp for Oracle
NetSuite integration for the rst time:
1. In your Oracle NetSuite account, click Customization.
2. On the left panel, click SuiteBundler, and then click Search & Install Bundles.
3. In the KEYWORDS eld, enter Cybersource for Oracle NetSuite.
4. Click the bundle ID 316818.
5. Click Install.

Installing the SuiteApp Update

Follow these steps if you already installed the SuiteApp integration.
1. In your Oracle NetSuite account, click Customization.
2. On the left panel, click SuiteBundler, and then click Search & Install Bundles.
3. In the KEYWORDS eld, enter Cybersource for Oracle NetSuite.
4. Click the bundle ID 316818.
5. From the list, ensure that the Replace Data option is selected for the following
contents:
• API response code/message
• Processor Name
• Sec Code
6. Click Update Bundle to start the update.
7. To verify progress, follow Steps 1-4 to go to the list of bundles.

Installing SuiteApp from Legacy Prole

Follow these steps to migrate from the Oracle NetSuite legacy prole to the
SuiteApp prole:
1. Install the SuiteApp integration. For more information, see Installing SuiteApp on page
60.

Cybersource Built by Us 60
Built by Us

2. Congure the new Payment Processing Prole and congure the required settings. For
more information, see Conguring Payment Processing Proles on page 67.
3. After you congure the new processing prole following the steps from the linked
section in the previous step, enable the new prole for the existing payment method
and websites in the Payment Processing Prole form. Test the new prole integration in
test mode.
4. When the conguration is working properly, uncheck the Test mode box in the Payment
Processing Prole form to use the integration in live mode.
5. Search for any default Payment Processing Prole assigned on the customer master
record. If necessary, remove the legacy prole and update it to the new SuiteApp
prole. This ensures you have updated the reference to the new prole.
6. Remove the reference to the legacy prole from the website setup, and assign the new
SuiteApp prole to the same website.
7. Clear the Authorization and Sale request type from the legacy prole to partially disable
the legacy prole. This ensures that new authorizations or sales do not process with
the legacy prole.
8. Verify that the open sales orders and cash sales were authorized by the legacy prole.
Congure a related transaction (cash, sale, or refund) with the legacy prole itself so
that related payment events are shown on the transaction.
If a sales order (authorization) is executed with a legacy Cybersource prole, and a
cash sale is executed with a new SuiteApp prole, the capture happens successfully
until the merchant ID and the gateway in the legacy prole and in the new SuiteApp
prole match. However, during a Sales Order Payment event, the reference is shown
only for the Authorization. It might not show the capture payment. The capture payment
event is visible in the cash sale record only.
9. When all sales orders authorized by the legacy prole are processed, uncheck the
Capture box, and Inactivate the legacy prole to fully disable the legacy prole.

Conguring SuiteApp
The SuiteApp integration supports the payment acceptance and order management
services for credit and debit cards, and the order management service supports
alternative payment methods: Apple Pay, Google Pay, PayPal, and Click to Pay.
The below sections provide details for conguring the payment acceptance and order
management services. You must go through each section in order for detailed instructions
on how to congure each feature.

Enabling the Plug-in

You must rst enable the plug-in before you begin conguring the SuiteApp features.
1. In your Oracle NetSuite account, click Customization.
2. On the left panel, click Plugins, and click Manage Plug-ins.
3. Ensure that the CYBERSOURCE FOR NETSUITE box is checked, and then click Save.

Cybersource Built by Us 61
Built by Us

Completing the SuiteApp Congurations

You must complete the following conguration to use all of the features offered in the
Cybersource Oracle NetSuite integration. Each feature requires detailed actions, which
are explained further in the linked sections below:
1. Conguring Payment Methods on page 62
2. Mapping Payment Methods on page 66
3. Conguring Payment Processing Proles on page 67
4. Conguring Reports on page 72
5. Conguring Invoicing on page 74

Conguring Payment Methods

The sections below describe how to congure specic payment methods.
• Conguring Automatic Payment Methods on page 62
• Conguring Credit and Debit Payment Methods on page 63
• Conguring Order Management Payment Methods on page 64
• Conguring Payment Card Token Payment Method on page 64
• Conguring Payment Card Token Payment Method on page 64
• Conguring the ACH Token Payment Method on page 65
The sections below describe the next tasks you must complete after you congure all of
the payment methods:
• Uploading a Payment Method Logo on page 66
• Mapping Check for Card Types on page 67

Conguring Automatic Payment Methods

Follow these steps to congure all supported payment methods
automatically:
1. In your Oracle NetSuite account, on the top navigation, hover over Cybersource
Integration > SuiteApp Conguration. Click SuiteApp Conguration.
2. On the top navigation, hover over Conguration > SuiteApp > Step 1: Payment Method.
Click Create Supported Payment Methods (Automatic).
3. Payment Method Mapping is automatically processed for credit and debit cards, ACH,
and tokens. For Order Management and Secure Acceptance Payment Methods (such
as Google Pay, Apple Pay, and Secure Acceptance credit and debit card), mapping is
automatically processed if the payment method name matches the supported plug-in
payment methods. Otherwise, select the respective Payment Method Mapping.
4. To view the created payment methods, click the Payment Method Record column link.
5. Make any desired changes.
6. Select the Display in Website eld to enable the automatic payment method.
7. Under the Payment Visuals tab, in the Flags eld, type web/standard.
8. For the URL eld, type the logo image URL.

Cybersource Built by Us 62
Built by Us

9. For the local payment card payment method, you must upload and copy the logo image
URL. For more information, see Uploading a Payment Method Logo on page 66.
10.Click Add.
11. Click Save.
The following payment methods are automatically congured:
• Apple Pay
• ACH
• ACH Token
• American Express
• Click to Pay
• Discover
• Google Pay
• Mastercard
• Payment Card Token
• PayPal Credit
• PayPal Express Checkout
• Secure Acceptance credit and debit card
• Secure Acceptance eCheck
• Visa
To use the ACH or token management functionality, you must enable payment
instruments. For more information, see Enabling Payment Instrument Support on page
80.
Klarna is currently not supported in the SuiteApp.

Conguring Credit and Debit Payment Methods

Follow these steps to congure credit and debit card payment methods:
1. In your Oracle NetSuite account, on the top navigation, hover over Cybersource
Integration > SuiteApp Conguration. Click SuiteApp Conguration.
2. On the top navigation, hover over Conguration > Suite > Step 1: Payment Method. Click
Create Payment Method (Manual).
3. Enter the name of the card (such as American Express).
4. From the Type eld drop-down list, choose Payment Card.
5. Check the REQUIRES LINE-LEVEL DATA box.
6. Check the Display in Website box to enable this payment method.
7. Under the Payment Visuals tab, in the Flags eld, type web/standard.
8. For the URL eld, enter the logo image URL. For more information, see Uploading a
Payment Method Logo on page 66.
9. For the local payment card payment method, you must upload and copy the logo image
URL.
10.Click Add.
11. Click Save.

Cybersource Built by Us 63
Built by Us

The following payment methods are automatically congured:

• Apple Pay
• ACH
• ACH Token
• American Express
• Click to Pay
• Discover
• Google Pay
• Mastercard
• Payment Card Token
• PayPal Credit
• PayPal Express Checkout
• Secure Acceptance credit and debit card
• Secure Acceptance eCheck"/>
• Visa
To use the ACH or token management functionality, you must enable payment
instruments. For more information, see Enabling Payment Instrument Support on page
80.
Klarna is currently not supported in the SuiteApp.

Conguring Order Management Payment Methods

Follow these steps to congure the order management payment methods
like Apple Pay, Google Pay, and PayPal:
1. In your account, on the top navigation, hover over Cybersource Integration > SuiteApp
Conguration. Click SuiteApp Conguration.
2. On the top navigation, hover over Conguration > SuiteApp > Step 1: Payment Method.
Click Create Payment Method (Manual).
3. Enter the name of this payment method (such as Google Pay, Apple Pay).
4. Select the type as External Checkout, and then click the corresponding account.
5. Click the Requires Line-Level Data box.
6. Click Add.
7. Click Save.

Conguring Payment Card Token Payment Method

Follow these steps to congure a Payment Card Token payment method on
the Payment Processing Prole:
1. In your Oracle NetSuite account, on the top navigation, hover over Cybersource
Integration > SuiteApp Conguration. Click SuiteApp Conguration.
2. On the top navigation, hover over Conguration > SuiteApp> Step 1: Payment Method.
Click Create Payment Method (Manual).
3. In the name eld, type Token.

Cybersource Built by Us 64
Built by Us

4. Check the Requires Line-Level Data box.

5. In the Type eld, choose Payment Card Token.
6. Check the Display in Website box to enable this payment method.
7. Under the Payment Visuals tab, in the Flags eld, type web/standard.
8. For the URL eld, enter the logo image URL. For more information, see Uploading a
Payment Method Logo on page 66.
9. For the local payment card payment method, you must upload and copy the logo image
URL.
10.Click Add.
11. Click Save.
To use the ACH or token management functionality, you must enable payment
instruments. For more information, see Enabling Payment Instrument Support on page
80.

Conguring the ACH Payment Method

Follow these steps to congure an ACH payment method on the Payment
Processing Prole:
1. In your Oracle NetSuite account, on the top navigation, hover over Cybersource
Integration > SuiteApp Conguration. Click SuiteApp Conguration.
2. On the top navigation, hover over Conguration > SuiteApp > Step 1: Payment Method.
Click Create Payment Method (Manual).
3. In the Name eld, type ACH.
4. Click the Requires Line-Level Data box.
5. Select the type as ACH.
6. Click the Display in Website box to enable this payment method.
7. Under the Payment Visuals tab, in the Flags eld, type web/standard.
8. For the URL eld, enter the logo image URL. For more information, see Uploading a
Payment Method Logo on page 66.
9. For the local payment card payment method, you must upload and copy the logo image
URL.
10.Click Add.
11. Click Save.
To use the ACH or token management functionality, you must enable payment
instruments. For more information, see Enabling Payment Instrument Support on page
80.

Conguring the ACH Token Payment Method

Follow these steps to congure an ACH token payment method on the
Payment Processing Prole:
1. In your Oracle NetSuite account, on the top navigation, hover over Cybersource
Integration,> SuiteApp Conguration. Click SuiteApp Conguration.

Cybersource Built by Us 65
Built by Us

2. On the top navigation, hover over Conguration > SuiteApp > Step 1: Payment Method.
Click Create Payment Method (Manual).
3. In the Name eld, type ACH Token.
4. Check the Requires Line-Level Data box.
5. From the Type drop-down list, choose General Token
6. Choose Display in Website eld to enable this payment method.
7. Under the Payment Visuals tab, in the Flags eld, type web/standard.
8. For the URL eld, enter the logo image URL. For more information, see Uploading a
Payment Method Logo on page 66.
9. For the local payment card payment method, you must upload and copy the logo image
URL.
10.Click Add.
11. Click Save.

Uploading a Payment Method Logo

Follow these steps to upload the logo of the payment method to the payment
visual:
1. On the top navigation, go to Documents > Files > File Cabinet.
2. Click the name of the folder to which you will add the new logo.
3. If you want to create a new folder, go to the File Cabinet menu, and click New.
4. Enter the folder name and click Save.
5. Click Add File and select the image from your computer.
6. Click Save. The le is now uploaded to the Oracle NetSuite le cabinet.
7. Click View/Edit next to the image.
8. View the URL. Select the URL from /Core until the h parameter. For example: /core/
media/media.nl?id=3406&c=TSTDRV2094488&h=3ea0d58984e482e565b1
9. Populate the URL eld of the Payment Visuals tab on the payment method screen with
the value obtained in Step 5.

Mapping Payment Methods

Payment method mapping is automatically completed for credit and debit
cards, ACH, and tokens and for order management and Secure Acceptance
payment methods (such as, Google Pay, Apple Pay, Secure Acceptance credit
and debit card) if the payment name matches the supported plug-in payment
methods. If the payment method name does not match the payment name,
follow these steps to map the payment methods:
1. In your Oracle NetSuite account, on the top navigation, hover over Cybersource
Integration > SuiteApp Conguration. Click SuiteApp Conguration.
2. On the top navigation, hover over SuiteApp Conguration, > Step 2: Payment Method
Mapping > Map Payment Methods.

Cybersource Built by Us 66
Built by Us

3. In the PAYMENT NAME row, choose the corresponding payment name from the drop-
down list for that payment method.

Mapping Check for Card Types

Sometimes the same credit and debit card can be referred with different
names in Oracle NetSuite and Cybersource. For example, credit and debit
card American Express can be referred to as Amex in Oracle NetSuite and as
American Express in Cybersource. To cross reference the credit and debit
card names between two systems, mapping is required.
Follow these steps to map credit and debit card names between the Cybersource and
Oracle NetSuite applications with a unique number:
1. Go to Customization, choose Lists > Records > Fields > Record Types.
2. From the results, select the custom record Card Type Mapping, and click the List link.
3. Verify that the mapping of the credit and debit card name between Oracle NetSuite and
Cybersource is correct.
4. If the mapping does not exist on the list page, click New Card Type Mapping to add a
new mapping.
5. Enter the Oracle NetSuite payment method name in Name eld.
6. Enter the card type value in the Card Type ID eld (this is a unique numeric value).
7. Enter the Cybersource payment method name in Card Type Name eld.
8. Uncheck the Inactive box.
9. Click Save.
10.Click the Edit link to update the credit and debit card name on any existing mappings.

Conguring Payment Processing Proles

Congure a new payment processing prole to support credit and debit cards and other
payment methods. Follow these steps to navigate to the Payment Processing Prole:
1. In your Oracle NetSuite account, on the top navigation, hover over Cybersource
Integration > SuiteApp Conguration. Click SuiteApp Conguration.
2. On the top navigation, hover over Conguration > SuiteApp > Step 3: Payment
Processing Prole. Click Create Payment Processing Prole.

Primary
From the Payment Processing Prole, follow these steps to complete the Primary section
of the Payment Processing Prole:
1. In the Primary section, in the WEB SITE box, choose the website for which this prole
must be applied.
2. In the Name eld, enter a name for the payment processing prole (such as Payment
Integration).
3. From the Subsidiary drop-down list, choose the subsidiary to which the prole should
be mapped.

Cybersource Built by Us 67
Built by Us

4. From the Charge Currencies box, choose a currency.

5. From the Settlement Currency drop-down list, choose which currency you want to
accept.
6. From the Settlement Bank Account drop-down list, choose the bank account for
receiving payments.
7. Check the Support Line Level Data box to support line data for the integration.
8. Check the Test Mode box to integrate with the Payment Gateway Test account for
processing the payment transactions. Clear the Test Mode box to run the integration
with the Payment Gateway Production account.

Payment Acceptance and Order Management

Follow these steps to complete the Payment Acceptance and Order Management section
of the Payment Processing Prole:
1. In the Payment Acceptance and Order Management section, in the Merchant ID eld,
enter the Cybersource merchant ID.
2. In the Payment Processing Prole, choose one of the level types:
• Level II to pass the Level II data.
• Level III to pass the Level III data.
• Basic to pass the default data to the gateway.
3. Choose the processor name. Click Blank to pass the request to gateway with the
default structure, which is processor agnostic.

Payment Facilitator
From the Payment Facilitator drop-down list, choose the desired Payment Facilitator for
the subsidiary corresponding to this Payment Processing Prole. This eld can be left
blank if Payment Facilitator is not used. For more information, see Enabling a Payment
Facilitator on page 80.

Payer Authentication Conguration

Select the desired Strong Consumer Authentication (SCA) settings for certain scenarios.
You can select one or more of these settings:
• Check the Enforce Strong Consumer Authentication for All Transactions box to enable
SCA for all transactions.
• Check the Enforce Strong Consumer Authentication When Saving Cards box to enable
SCA when the card is being saved for the rst time.
• Check the Proceed To Authorization when ECI Values are 00/07 box to proceed with
the authorization when the Electronic Commerce Indicator values are 00 or 07, which
means the cardholder was unable to authenticate for various reasons.

REST Keys Conguration

You must enter the required REST information you obtained from the Business Center:

Cybersource Built by Us 68
Built by Us

1. In the REST Key ID eld, enter the REST Key Identier value from the Business Center.
2. In the REST Secret Key eld, enter the REST Secret Key value from the Business Center.
For steps on how to generate a key ID and a secret key, see Creating a Shared Secret Key
Pair.

SOAP Key Conguration

Currently, you can enter REST or SOAP credentials to use the services, but SOAP and
Secure Acceptance will be removed from SuiteApp in August 2024. If you are using SOAP
or Secure Acceptance, consider moving to REST before August 2024.

Transaction Hold Reason

Select the reason codes when a payment must be put on hold (such as 101 -
MISSING_FIELD, 102 - INVALID_DATA). For more information about reason codes, see
Reason Codes for Oracle NetSuite on page 85.

Merchant Reference Number Customization

Set one of these options in the For Capture eld and one in the For Refund eld:
• Sales Order # to set the merchant reference code to the sales order number
• Cash Sale # to set the merchant reference code to the cash sale number
• Cash Refund # to set the merchant reference code to the cash refund number

Fraud Management
Check the Enable Fraud Management box to use the Decision Manager rules or the rules
enforced by the Cybersource machine learning system. Clear this option to ignore the
Cybersource Fraud Management Services.
In the Decision Manager Reject eld, choose the External Fraud Reject Hold to keep the
payment on hold when the Cybersource Fraud Management services rejects the payment.
Choose the External Fraud Reject Hold and Cancel Order to cancel the order when the
Cybersource Fraud Management services reject the payment.

AVS/CVN Rules
By default, only Address Verication Service (AVS) code N results in an AVS decline. Use
the Decline AVS Flags eld to specify a list of AVS codes that should result in an AVS
decline. You must include the value N in the list if you want to receive declines for AVS
code N. These are the available codes are 1, 2, 3, 4, 5, A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P,
Q, R, S, T, U, V, W, X, Y, Z.
Choose the Ignore AVS Response box to disable AVS functionality. If this box is checked,
the plugin ignores the results from the Cybersource AVS, even when you use Decline
AVS ags. The plugin processes the payment transaction when a customer's address
information does not match the billing address of the credit or debit card account.
The No AVS Match, AVS Service Not Available, and the Partial AVS Match settings indicate
how SuiteApp handles AVS results returned during an authorization and sale operation.
For each AVS setting, in their respective eld, choose one of these actions:

Cybersource Built by Us 69
Built by Us

• Accept
• Cancel Order
• Verication Review

Credit Card Verication (CSC) Rules

Check the Ignore CSC Response box to disable CSC functionality. If this box is checked,
the plugin ignores the results from the Cybersource CVN service. The plugin processes
the payment transaction even when the CSC code entered does not match the security
code of the credit and debit card account.
These settings indicate how SuiteApp handles CVN results returned during an
authorization and sale operation:
• CSC Not Submitted
• CSC Not Supported by Cardholder Bank
• CSC Service Not Available
• CSC Check Failed
• No CSC Match
For each CSC setting (listed above), in their respective eld, choose one of these actions:
• Accept
• Cancel Order
• Verication Review

Override Options
Check the Use Dummy Billing Email Address box to use a dummy email on requests with an
empty email address.

Secure Acceptance Prole Conguration

Follow these steps to Secure Acceptance as a payment method, if you are using it:
1. In the Prole ID eld, enter your Business Center Secure Acceptance prole ID.
2. In the Access Key eld, enter your Business Center Secure Acceptance access key.
3. In the Key Secret eld, enter your Business Center Secure Acceptance key secret.
4. In the Web Store URL eld, enter the Web Store URL link. Make sure that you replace
the relevant account ID on the following URL https://accountid.secure.Oracle
NetSuite.com/app/site/backend/returnfromplacedorder.nl. You can nd the
account ID in Setup/Company/Company Information/Account ID. After logging in
to Oracle NetSuite, the account ID is visible on the URL as well (such as: https://
tstdrv2134322.secure.netsuite.com/app/site/backend/returnfromplacedorder.nl).
5. In the Web Store Invoice URL eld, enter the Web Store Invoice URL. Make sure that you
replace the relevant account ID on the following URL along with the website version.
https://<accountid>.secure.Oracle NetSuite.com/c.<accountid>/<websiteversion>/
my_account.ssp
Examples:

Cybersource Built by Us 70
Built by Us

• For SuiteCommerce Advanced: https://123456.secure.Oracle NetSuite.com/c.123456/

sca-src-2022-2-0/my_account.ssp
• For SuiteCommerce: https://123456.secure.netsuite.com/c.123456/scs/
my_account.ssp
• For SiteBuilder: https://123456.secure.netsuite.com/c.123456/sbe-src-kilimanjaro/
my_account.ssp. You can nd the account ID in Setup/Company/Company
Information/Account ID. When you login to Oracle NetSuite, the account ID will be
visible on the URL as well. (for example, https://tstdrv2134322.secure.netsuite.com/
app/site/backend/returnfromplacedorder.nl).

Merchant Dened Data Mapping

In the Merchant Dened Data Mapping elds, choose the Merchant Dened Data Mapping
eld if you want the eld value from the transaction to sync to the Business Center.
This service is not supported when Payer Authentication (3-D Secure) is enabled due to
limitations.
Under the Decision Manager section, Payer Authentication (DMPA) is not supported as of
now. You must disable the DMPA rules set in the Business Center.

Default Custom Messages and Developer ID

Enter the customer messages that you want displayed for each of these scenarios:
• External Reject Message: Enter the custom message to be displayed for transactions
that are rejected.
• External Hold Message: Enter the custom message to be displayed for transactions that
are kept on hold.
• Developer ID: Enter the developer ID (for example, 20083856). This ID is populated by
the solution partner or solution integrator who performs the implementation on your
behalf.

ACH Conguration
Choose the Default SEC Code for all ACH transactions through Oracle NetSuite. You can
change the SEC (Standard Entry Class) Codes at the transaction level. These are the SEC
codes you can choose:
• PPD: Pre-arranged payment or deposit
• CCD: Corporate credit or debit
• TEL: Telephone initiated entries
Oracle NetSuite SuiteCommerce automatically sets the SEC code for transactions to WEB
(internet initiated/mobile entry).

Cybersource Built by Us 71
Built by Us

Webhook Conguration for Network Tokenization

If you want to enable creating a webhook subscription, check the Webhook Subscription
box. Then enter a custom name in the Webhook Name box and a custom description in the
Webhook Description box.
For more information, see Enabling Network Tokenization on page 81.

Payment Information
In the Supported Payment Methods eld, select all of the payment methods that you
require. In the Gateway Request Types eld, select all of the gateway request types that
you require (authentication, authorizations, capture authorization, credits, refunds, sales,
void authorizations).

Tokenization
Check the Replace Payment Card by Token box to support tokenization (tokenization is
supported through Strong Customer Authentication (SCA) and not Oracle NetSuite).
Then, in the Payment Card Token Payment Method eld, select the payment method. For
ACH, in the General Token Payment Method eld, select the payment card token payment
method.

Conguring Reports
The Cybersource SuiteApp for Oracle NetSuite bundle provides these reporting services,
which you can import from Cybersource into Oracle NetSuite:
• Transaction Request Report
• Payment Batch Detail Report
• Conversion Detail Report

Conguring Reports
Follow these steps to congure the reports that you want to use:
1. In your Oracle NetSuite account, on the top navigation, hover over Cybersource
Integration > SuiteApp Conguration. Click SuiteApp Conguration.
2. On the top navigation, hover over Conguration > Reporting. Click Create Reporting
Setup.
3. Enter your Business Center merchant ID and the key ID and secret key that you
generated from the Business Center.
4. Check the Conversion Detail Report box to move details of the Conversion Detail
Report from the Business Center to Oracle NetSuite.
5. Check the Test Mode box to run the integration in test mode. Clear the Test Mode box
to run the integration in live mode.
6. Click the Reporting File Details tab. The conguration for standard Payment Batch
Detail Report and Transaction Request Report appear by default. They cannot be
removed.
7. Choose a report (Payment Batch Detail Report or Transaction Request Report).

Cybersource Built by Us 72
Built by Us

8. Enter the name of the custom report under Name and click OK.
9. Enter an end date for a custom one-time report like these examples. Keep the eld
blank for subscription reports.
Example 1: If your report start date is 2023-03-06 and the end date is 2023-03-09, the
Report End Date passed in the query is 2023-03-09.
Example 2: If your report runs from midnight to midnight on 2023-03-09, the Report End
Date passed in the query is 2023-03-10.

Conguring the Schedule for the Transaction Request Report

The reporting scripts pull the information from the payment application to
Oracle NetSuite based on schedules dened in Oracle NetSuite. To ensure
timely generation of reports, set up the same timezone on your Oracle
NetSuite account and on the Business Center.
Follow these steps to congure a schedule for the Transaction Request Report:
1. In your Oracle NetSuite account, on the top navigation, hover over Cybersource
Integration > Reporting Scripts. Click Transaction Request Report.
2. On the script deployments page, click View to view the scheduler details.
3. On the Schedule tab of the Script Deployment page, you can view the frequency of the
event, the start date and start time, and the end date and end time.
4. By default, the schedule is set as a daily event with a start time of 12:00 a.m.
5. You can change the schedule options. Click Edit on the script deployments page to
update the scheduler options.
6. On the Schedule tab, choose the appropriate frequency of the event (daily/weekly/
monthly), start date and start time, the end date and end time of the event.

Conguring the Schedule for Payment Batch Detail Report

The reporting scripts pull the information from the payment application to
Oracle NetSuite based on schedules dened in Oracle NetSuite. To ensure
timely generation of reports, set up the same timezone on your Oracle
NetSuite account and on the Business Center.
Follow these steps to congure a schedule for the Payment Batch Detail Report:
1. In your Oracle NetSuite account, on the top navigation, hover over Cybersource
Integration > Reporting Scripts. Click Payment Batch Detail Report.
2. On the script deployments page, click View to view the scheduler details.
3. On the Schedule tab of the Script Deployment page, you can view the frequency of the
event, the start date and start time, and the end date and end time.
4. By default, the schedule is set as a daily event with a start time of 12:00 a.m.
5. You can change the schedule options. Click Edit on the script deployments page to
update the scheduler options.
6. On the Schedule tab, choose the appropriate frequency of the event (daily/weekly/
monthly), start date and start time, the end date and end time of the event.

Cybersource Built by Us 73
Built by Us

Conguring the Schedule for Conversion Detail Report

The reporting scripts pull the information from the payment application to
Oracle NetSuite based on schedules dened in Oracle NetSuite. To ensure
timely generation of reports, set up the same timezone on your Oracle
NetSuite account and on the Business Center.
Follow these steps to congure a schedule for the Conversion Detail Report:
1. In your Oracle NetSuite account, on the top navigation, hover over Cybersource
Integration > Reporting Scripts. Click Conversion Detail Report.
2. On the script deployments page, click View to view the scheduler details.
3. On the Schedule tab of the Script Deployment page, you can view the frequency of the
event, the start date and start time, and the end date and end time.
4. By default, the schedule is set as a daily event with a start time of 12:00 a.m.
5. You can change the schedule options. Click Edit on the script deployments page to
update the scheduler options.
6. On the Schedule tab, choose the appropriate frequency of the event (daily/weekly/
monthly), start date and start time, the end date and end time of the event.
7. The script Update SO status by Conversion Detail Report updates the sales order
status according to the information from the conversion detail report. To view the
scheduler option of this script, hover over Cybersource Integration > Reporting Script.
Click Update SO status by Conversion Detail Report.
8. You can view and change the schedule options on the Script Deployment page.

Creating a Reporting Script

If any of the imported reporting records are missing from the mapping to the
transaction in Oracle NetSuite, you can initiate a script on demand to map
the existing reporting records to the transaction IDs. Follow these steps to
initiate this script:
1. In your Oracle NetSuite account, on the top navigation, hover over Cybersource
Integration > Reporting Script. Click Map NS ID on Reporting Records.
2. On the Script Deployments page, click Edit next to
customdeploy_cs_pymt_map_reporting_ns_id for the status Not Scheduled.
3. Click the drop-down button next to Save, and click Save and Execute. The script will
now update the reporting records in the background.

Conguring Invoicing
The Cybersource invoicing feature enables you to create invoices and share them with
your customers. You can manage invoices and import existing invoices within Oracle
NetSuite.
If an invoice is created in Oracle NetSuite, Cybersource recommends you make all
of the updates to that transaction on Oracle NetSuite and have the feature update
the corresponding invoice in Business Center. If an invoice is created in the Business
Center and imported into Oracle NetSuite, Cybersource recommends that all updates

Cybersource Built by Us 74
Built by Us

to that transaction be done on the Business Center and have the feature update the
corresponding invoice in Oracle NetSuite.

Enabling the Custom Transaction Feature for Invoicing

You must enable the Custom Transaction feature to use the upgraded
invoicing features.
1. In the top navigation, hover on Setup > Company. Click Enable Features.
2. Click the SuiteCloud tab.
3. Scroll down to the SuiteGL section, and check the Custom Transactions box.

Setting Up an Invoicing for the Pay by Link Feature

Follow these steps to set up the Cybersource Pay by Link Invoicing feature:
1. In your Oracle NetSuite account, on the top navigation, hover over Cybersource
Integration > SuiteApp Conguration. Click SuiteApp Conguration.
2. On the top navigation, hover over Conguration > Invoicing. Click Create Invoicing
Setup.
3. Under Merchant Details, enter the required elds. Enter a name in the corresponding
eld for your invoicing conguration.
4. If you are working with a Business Center Test Account, check the Test Mode box.
5. For the Merchant ID eld, enter the Business Center account merchant ID (MID).
6. For the Secret Key eld, enter the Business Center account secret key (key ID). For
steps on how to generate a shared secret key, see Creating a Shared Secret Key Pair.
7. For the Key eld, enter the Business Center account merchant key (secret key). For
steps on how to generate a shared secret key, see Creating a Shared Secret Key Pair.
8. Under Oracle NetSuite Invoice Default Values, check the Set as Default MID box to add
the MID you entered earlier as the Pay by Link account on new invoices.
9. Check Use Invoice Number as Pay by Link Invoice ID box to automatically set the Oracle
NetSuite generated invoice ID on the Pay by Link Invoice ID eld (if left blank).
10.Select a Default Invoice Action that you want set on the invoice record. This selection
has to be set at the same value on the Pay by Link Create Invoice eld when you create
a new invoice. These are the options:
• Create a draft invoice.
• Create and send the invoice immediately. This creates the invoice and the customer
receives the Pay by Link invoice.
• Create an invoice without sending it. This creates an invoice and generates the Pay
by Link invoice, but does not send it to the customer.
11. Select the Default MID Cong eld, which displays the current default invoicing setup.
The default MID cannot be inactivated or deleted. Assign another invoicing setup as the
default before inactivating or deleting the default invoicing setup. If an item has auto
sourcing values, which are mandatory on an invoice line level, then these values must be
set on the default items present on the invoicing conguration record.

Cybersource Built by Us 75
Built by Us

12.Under Business Center Import Invoice Default Values, check the Import EBC Invoices
box to import invoices created in Business Center into Oracle NetSuite.
13.Select the On Demand Scheduler to run the invoices script on demand.
14.Choose the Default Customer in case of any error while creating or updating existing
customer in an invoice. Choose the same customer as the subsidiary.
15.Choose the Subsidiary you want recorded on the invoices.
16.Choose the Location you want recorded on the invoice.
17. Choose the Item that defaults on the invoice when an item is not matched.
18.Choose the Shipping Item that defaults on an invoice for shipping cost.
19.Choose the Tax Item that defaults on an invoice for tax amount.
20.Choose the Discount Item to add a default item on an invoice for discount amount.
21.Choose a Tax Code to use on an invoice. The default is Not Taxable.
22.Choose a Deposit Account to deposit paid invoices.
23.Check the Default Header Only box to set the default header as the only option for all
the invoicing transactions.
24.Click Save.

Creating a New Invoice

You must enter all of the details in the Invoice page and then ll out the
Cybersource tab to create an invoice in Oracle NetSuite and send it to
Cybersource.
1. In your Oracle NetSuite account, hover over Transactions, hover over Sales, and then
click Create Invoices. For detailed instructions on how to complete the Invoice page,
see Creating an Invoice. Then, continue following the steps in this section to complete
the Cybersource portion.
2. While still on the Invoice page, scroll down and click the Cybersource tab.
3. In the Pay by Link MID Account eld, select the same MID account as the Default
MID Cong eld contains from the Conguring an Invoicing Setup section. This eld
contains all the active set up records, so double check that you select the correct
account.
4. In the Pay by Link Create Invoice eld, select the same invoice action that you selected
for the Default Invoice Action eld in the Conguring an Invoicing Setup section.
5. (Optional) If you want to create an invoice using a specic number, enter that number
in the Pay by Link Invoice ID eld. If you leave it blank, Cybersource auto-generates the
invoice number and saves it. The invoice ID allows only letters, numbers, and special
characters: _ -.
6. If you want to allow partial payments for the invoice, enter the amount in the Pay by Link
Partial Allowed Amount eld. The partial amount entered should not be greater than the
total invoice amount.
7. Enter the email to be used to send the Pay by Link Invoice Link eld at the transaction
level. If you leave this eld blank, the system sources the email address from the Pay by

Cybersource Built by Us 76
Built by Us

Link Email eld on the Customer record. If that eld is also blank, the system sources
the email address from the standard Email eld on the Customer record.
8. Check the Pay by Link Header Only box if you do not want to send line-level data in the
request to the Business Center. If you do want to send line level data, it cannot exceed
the maximum limit of 30 lines, and you must leave the box clear.
9. Click Save. If you exceed the line-level data limit and did not check the Pay by Link
Header Only box, a warning message appears when you try to save it. You must either
reduce the number of lines or check the Pay by Link Header Only box to send the
header only.
10.When you save the record, a new invoice is created in the Business Center with these
details. The system saves the invoice number from the Business Center in the Pay by
Link Invoice ID eld and the status in the Pay by Link Invoice Status eld.
11. If an issue occurs while you are creating the invoice, the error message appears in the
Pay by Link Error Message eld. After you resolve the error, save the record again to
create the invoice. For more information about the reason codes, see Reason Codes
for Oracle NetSuite on page 85.

Updating an Existing Invoice

Follow these steps to update an existing invoice from Oracle NetSuite to the
Business Center:
1. On the top navigation, hover over Transactions > Sales > Create Invoices. Click List.
2. On the Invoices page, click Edit on the invoice that you want to update.
3. Make the appropriate changes in the invoice.
4. Scroll down and click the Cybersource tab.
5. In the Pay by Link Invoice Action eld, select Update.
6. Click Save. The invoice is now updated in the Business Center in the Pay by Link Invoice
Status eld.

Sending an Invoice
Follow these steps to send or resend an invoice from Oracle NetSuite:
1. On the top navigation, hover over Transactions > Sales > Create Invoices Click List.
2. On the Invoices page, click Edit on the invoice that you want to update.
3. Scroll down and click the Cybersource tab.
4. In the Pay by Link Invoice Action eld, choose the SEND.
5. Click Save. The invoice link is sent from the Business Center to the customer email.

Voiding an Invoice
Follow these steps to void an invoice in Oracle NetSuite and cancel it in the
Business Center:
1. On the top navigation, go to Setup > Accounting > Accounting Preferences.
2. Clear the Void Transactions Using Reversing Journals box if checked.

Cybersource Built by Us 77
Built by Us

3. Click Save.
4. On the top navigation, hover over Transactions > Sales > Create Invoices. Click List.
5. On the Invoices page, click Edit on the invoice that you want to update.
6. Scroll down and click the Cybersource tab.
7. In the Pay by Link Invoice Action eld, select Cancel.
8. Click Save. The invoice is now voided from Oracle NetSuite and canceled in the Business
Center.

Searching for an Invoice

You can search for invoices created and imported in Oracle NetSuite from
these four lists:
• Invoices Created and Send: Shows the list of invoices.
• Paid Invoices: Shows the list of paid invoices.
• Errored Invoices When Exporting: Shows the invoices errored out when an invoice had
an error message.
• Errored Invoices When Importing: Shows the invoices errored out when importing or
updating an invoice had an error message.
To search for an invoice, on the top navigation, hover over Cybersource
Integration > Invoicing. Select the list for the invoice you want to nd.
Invoicing using the Webstore

Enabling the Payment Link Feature

You must enable the Payment Link feature in Oracle NetSuite to use invoicing with the
webstore. Follow these steps to enable Payment Link:
1. On the top navigation, hover over Setup > Company. Click Enable Features.
2. Click the Transactions tab, and then scroll down to Payment Processing.
3. Check the Payment Link box.
4. Click Save.

Setting Up Invoicing for Suite Payment

Follow these steps to setup the invoicing for Suite Payment:
1. On the top navigation, go to Commerce, and click Payment Link.
2. Enter a name in the Domain Prex eld to be part of the domain.
3. Select the payment methods in the Payment Methods eld that you want to make
available.
4. Check the Accept Partial Payments box to allow customers to select the amount to be
paid on an invoice.
5. Upload and select a company logo in the Company Logo eld to display in the header of
the Payment Link page.

Cybersource Built by Us 78
Built by Us

6. Enter a name in the Company Name eld to display in the header of the Payment Link
page.
7. Enter additional company information in the Company Info eld to display in the header
of the Payment Link page.
8. Set the system email template in the Payment Accepted eld that you want to send to
customers when payment is conrmed.
9. Set the system email template in the Payment Rejected eld that you want to send to
customers when payment is rejected.
10.Click Save.

Creating an Invoice and Generating a Payment Link

To create an invoice and generate a payment link in Oracle NetSuite:
1. On the top navigation, hover over Transactions > Sales. Click Create Invoices. For
detailed instructions on how to ll out the Invoice page, see Creating an Invoice. Then,
continue following the steps in this section to generate a payment link.
2. Click Save.
3. While still on the Invoice page, click the Billing tab, and click Payment.
4. On the Payment tab, the payment link will be generated.
5. Click Payment Link, and complete all of the required elds.
6. Click Submit.
7. After the payment is successful, refresh the invoice in Oracle NetSuite.
8. Go to Related Records to view the customer payment reference.

Testing an Invoice Payment Using Webstore Invoice Payment

through Credit and Debit Card
Follow these steps to test an invoice payment transaction from a credit or debit card:
1. On the top navigation, hover over Transactions > Sales. Click Create Invoices. For
detailed instructions on how to ll out the Invoice page, see Creating an Invoice. Then,
continue following the steps in this section to generate a payment link.
2. Click Save.
3. After you save the invoice, go to Commerce > Website. Click Website List.
4. Click Preview for the applicable website.
5. Log in to your website using your credentials.
6. Go to Billing, and click Invoices.
7. Select the specic invoice that you want to pay.
8. Click Make payment.
9. Select the payment method as credit or debit card.
10.Enter the card details, and the billing and shipping address.
11. Click Submit.
12.If the customer cancels the transaction, the payment record in Oracle NetSuite is
voided and the customer can reprocess the same invoice. If the payment is not voided
during retry, click Payment record, and then click the Finalize your Payment link to void

Cybersource Built by Us 79
Built by Us

the transaction. The message "Pending Payment Voided Successfully" appears. Go back
to the invoice in Billing, and then Invoices to retry the payment.
Due to Oracle NetSuite limitations, multiple invoices cannot be processed simultaneously
with requires line-level data checked on the Payment Methods.
Invoice payment through web store works only with the latest Suite Commerce and Suite
Commerce Advance versions.

Enabling Payment Instrument Support

You must enable the Payment Instruments conguration to use these specic features:
• Tokenization
• Network Tokenization
• ACH
• Multi-Capture
• Delay Shipment
• Merchant Initiated Transactions (MIT Mandate)
• Invoicing – Pay by Link
Follow these steps to enable Payment Instruments:
1. Go to Setup > Company. Click Enable Features.
2. Click the Transactions tab.
3. Scroll down to the Payment Processing section, and check the Payment Instruments
box.

Enabling a Payment Facilitator

A Payment Facilitator (PayFac) is registered by an acquirer to facilitate transactions on
behalf of merchants. With the introduction of a PayFac, the merchant becomes a sub-
merchant, and the PayFac becomes the main merchant.
If you are using the multi-subsidiary customer feature in Oracle NetSuite, ensure that
there is a Payment Processing Prole for each transacting subsidiary to enable payment
processing for transactions pertaining to those subsidiaries.
The PayFac feature in the SuiteApp is supported only using REST keys. To support PayFac
processing, additional conguration is required in order to enter the sub-merchant
information.
Follow these steps to congure the PayFac feature:
1. On the top navigation, hover over Cybersource Integration > SuiteApp Integration. Click
SuiteApp Integration.
2. Hover over SuiteApp Conguration > Step 3: Payment Processing Prole. Click View
Payment Processing Proles.
3. Click Edit next to the prole that you need to enable the Payment Facilitator.
4. Scroll down to the Payment Facilitator section.
5. In the Payment Facilitator drop-down eld, click New.
6. Enter a name for the Payment Facilitator in the Name eld.

Cybersource Built by Us 80
Built by Us

7. Open the Aggregator Information tab and complete all of the mandatory elds. These
include:
• Aggregator Name
• Aggregator ID
• Sub Merchant Name
• Sub Merchant Country
• Sub Merchant State
• Sub Merchant City
• Sub Merchant Postal Code
• Sub Merchant Address1
• Sub Merchant Email
• Sub Merchant Phone Number
• Sub Merchant Card Acceptor ID
• Sub Merchant Region
8. Open the Merchant Information tab and complete all of the mandatory elds. These
include:
• Merchant Descriptor Name
• Merchant Country
• Merchant State
• Merchant City
• Merchant Postal Code
• Merchant Address1
• Merchant Contact
• Merchant Category Code
• Merchant Tax ID
• Merchant Sales Organization Code
9. Save the Payment Facilitator record.

Enabling Network Tokenization

A network token is a network scheme generated token, that represents customer card
information for secure transactions that reference an actual PAN.
Before you can enable a MID for Network Tokenization, you must provision it with a Token
Requestor ID (TRID) for each card scheme. The Network Tokenization feature in the
SuiteApp supports only REST keys.
Oracle NetSuite must subscribe to the necessary webhook notications and ingest
them for changes to the card. The system automatically creates the subscription when
processing the authorization when the webhook subscription feature is enabled in
the prole. If you perform an authorization as an external event, you must update the
subscription ID in Oracle NetSuite along with the import of the tokens to accept webhook
notications for these card changes.
Oracle NetSuite processes only these token updates:
• Active: The system updates the Payment Card Token Inactive eld based on this value.

Cybersource Built by Us 81
Built by Us

• Deleted: The system deletes the Payment Card Token record from Oracle NetSuite.

Conguring Network Tokenization

Follow these steps to congure the network tokenization feature:
1. On the top navigation, hover over Cybersource Integration > SuiteApp Integration. Click
SuiteApp Integration.
2. Hover over Conguration > Step 3: Payment Processing Prole. Click View Payment
Processing Proles.
3. Click Edit next to the prole that you need to enable network tokenization.
4. Scroll down to the Webhook Conguration for Network Tokenization section, and check
the Webhook Subscription box.
5. Go to back to Cybersource Integration, and then go to SuiteApp Integration.
6. Hover over Conguration > SuiteApp Integration. Click Copy Webhook - Notication
URL. You must enter the Oracle NetSuite Suitelet URL in your Business Center webhook
settings.
7. Go to your Business Center account.
8. In your Business Center account, go to Payment Conguration, and click Webhook
Settings.
9. Click Create.
10.In the URL eld, enter the Oracle NetSuite Suitelet URL to receive the webhook
notications.
11. Turn on the Enable switch.
12.From the list, select the same Shared Secret Key that you use for the subscription
record in Oracle NetSuite.
13.Click Save.

Conguring External Subscriptions

If you created subscriptions outside of Oracle NetSuite, then you must create a
subscription record in Oracle NetSuite. Follow these steps to create a subscription
record:
1. Go back to Cybersource Integration > SuiteApp Integration. Click SuiteApp Integration.
2. Go to Conguration > Step 3: Payment Processing Prole. Click View Payment
Processing Proles.
3. Click Edit next to the prole you need to create a subscription record.
4. Scroll down to the Webhook Conguration For Network Tokenization section, and click
New.
5. Enter these required elds:
• Subscription ID: Enter the Webhook Subscription ID
• PPP Record ID: Enter the internal ID of the payment processing prole record to use
with this subscription.
Keep the associated payment processing prole active, or update this eld with the
active payment processing prole record ID to accept webhook notications. If the
PPP Record ID eld is empty, has invalid data, or is associated with an inactive prole

Cybersource Built by Us 82
Built by Us

or missing REST keys, Oracle NetSuite does not process the webhook notications
for token updates.
• Webhook Security Key: Enter the Webhook Security Key
• Merchant ID: Enter the Merchant ID
6. Click Save.
7. Import the payment card tokens into Oracle NetSuite.

Oracle NetSuite Merchant-Initiated Transactions

The MIT mandate ensures that merchants, acquirers, and issuers understand the
transaction processing cycle. The MIT framework introduces a global standard for
identifying transaction intent and whether a transaction is merchant initiated (without
participation of cardholder).
The MIT framework facilitates exemptions from Strong Customer Authentication (SCA)
using 3-D Secure depending on the transaction context (such as recurring transactions or
Mail-Order/Telephone-Order (MOTO) transactions).

Benets of Complying with the MIT Mandate

Merchants, acquirers, and issuers can link a series of related transactions.
• MIT transactions—token-based transactions in particular, have better approval rates
when the issuer can identify them.
• MIT and token-based transactions can be processed without strong customer
authentication (these transactions might otherwise fail, especially in regions complying
with PSD2).
• Transaction transparency, which results in higher authorization rates and improved
cardholder experience.

Supported MIT Transaction Types

The MIT transaction types mentioned below are industry-specic transactions supported
by the plugin:
• Resubmission: A merchant resubmits transactions that request authorization but were
declined due to insufcient funds while the goods or services were already delivered
to the cardholder. A merchant in this situation can resubmit the request to recover
outstanding debt from cardholders.
• Reauthorization: A merchant initiates a reauthorization when the original order or
service is not complete or fullled within the authorization validity limit set by the
scheme. Common instances that require reauthorizations include delayed shipments,
split shipments, extended stays, and extended rentals.
• Delayed Charges: A delayed charge is associated with an agreement between you and
the cardholder for services rendered. Merchants might use delayed charges after
providing services such as lodging, travel, or auto rental.
• No Show: A no-show transaction occurs when you and a cardholder have an agreement
for a purchase, but the cardholder does not meet the terms of the agreement. No-

Cybersource Built by Us 83
Built by Us

show transactions are often used in hotels or restaurants where bookings are not
honored despite the agreement entered into by the cardholder.
• Unscheduled/Auto Top-up: This type of transaction uses a stored credential for a
xed or variable amount and does not occur on a scheduled or regularly occurring
transaction date. The cardholder must provide consent for the merchant to initiate one
or more future transactions.
If a MIT type is not selected, the transaction is agged and processed as MOTO by default.
To avoid issues processing a MIT with a custom role, you must provide the payment
instrument permission to the role. The Payment Type eld is supported only when the
Payment Instrument feature is enabled.
Follow these steps to assign the role:
1. Go to Setup.
2. Click Users/Roles, and click Manage Roles.
3. Click Customize on the role you want to assign the permission to.
4. Scroll down, and under the Permissions tab, click the Lists subtab.
5. Find the Payment Instrument row and set permission level to Full.
6. Click Save.

Initial Authorization of External Merchant Initiated Transactions

Follow these steps to trigger subsequentAuth instead of subsequentAusubsequentAuth and
authFirst for payment card tokens imported into Oracle NetSuite.
1. Go to Cybersource Integration > SuiteApp Conguration. Click SuiteApp Conguration.
2. On the top navigation, hover over Conguration > Reporting.
3. Click the Payment tab.
4. In the Payment Network Reference eld, select MOTO transaction.

Reference Information
This section contains reference information that is useful when integrating with Oracle
NetSuite.

Testing Endpoints
Follow these steps to verify the test and live endpoint URLs to be used by the integration.
1. Go to Customization > Lists, Records, and Fields > click Record Types.
2. Under Record Types, click List of the Payment API Conguration record type.
3. Verify that the test and live endpoint URLs are correct. If any changes are required,
conrm with the company team, and update them in the custom record.
4. You can also check the SuiteApp version on the bottom of the Oracle NetSuite
Conguration Screen. This helps easily identify the version that you currently use.
5. To check the SuiteApp version, go to Cybersource Integration > SuiteApp
Conguration. Click SuiteApp Conguration.

Cybersource Built by Us 84
Built by Us

Reason Codes for Oracle NetSuite

The following table describes the reason codes that are returned by Oracle NetSuite.

Reason Codes

Reason Description
Code

100 Successful transaction.

101 Decline: The request is missing one or more fields.
102 Decline: One or more fields in the request contains invalid data.
104 Decline: The merchantReferenceCode sent with this authorizati
on request matches the merchantReferenceCode of another
authorization request that you sent in the last 15 minutes.
110 Partial amount was approved.
150 Error: General system failure.
151 Error: The request was received but there was a server timeout. This error does
not include timeouts between the client and the server.
152 Error: The request was received, but a service did not finish running in time.
200 Soft Decline: The authorization request was approved by the issuing bank but fla
gged by Cybersource because it did not pass the Address Verification Service (
AVS) check.
201 Decline: The issuing bank has questions about the request. You do not receive a
n authorization code programmatically, but you might receive one verbally by ca
lling the processor.
202 Decline: Expired card. You might also receive this if the expiratio
n date you provided does not match the date the issuing bank ha
s on file. The ccCreditService does not check the expiration d
ate; instead, it passes the request to the payment processor. I
f the payment processor allows issuance of credits to expired
cards, Cybersource does not limit this functionality.
203 Decline: General decline of the card. No other information provided by the issui
ng bank.
204 Decline: Insufficient funds in the account.
205 Decline: Stolen or lost card.
207 Decline: Issuing bank unavailable.
208 Decline: Inactive card or card not authorized for card-not-present transactions
.
209 Decline: Card verification number (CVN) did not match.

Cybersource Built by Us 85
Built by Us

Reason Description
Code

210 Decline: The card has reached the credit limit.

211 Decline: Invalid Card Verification Number (CVN).
220 Decline: Generic decline.
221 Decline: The customer matched an entry on the processor's negative file.
222 Decline: Customer's account is frozen.
230 Soft Decline: The authorization request was approved by the issuing bank but fla
gged by Cybersource because it did not pass the Card Verification Number (CV
N) check.
231 Decline: Invalid account number.
232 Decline: The card type is not accepted by the payment processor.
233 Decline: General decline by the processor.
234 Decline: There is a problem with your Cybersource merchant configuration.
235 Decline: The requested amount exceeds the originally authorize
d amount. This can occur if you try to capture an amount larger t
han the original authorization amount.
236 Decline: Processor failure.
237 Decline: The authorization has already been reversed.
238 Decline: The transaction has already been settled.
239 Decline: The requested transaction amount must match the previous transactio
n amount.
240 Decline: The card type sent is invalid or does not correlate with t
he credit/debit card number.
241 Decline: The referenced request ID is invalid for all follow-on tra
nsactions.
242 Decline: The request ID is invalid. You requested a capture, but t
here is no corresponding, unused authorization record. This can
occur if there was not a previously successful authorization request
or if the previously successful authorization has already been used
in another capture request.
243 Decline: The transaction has already been settled or reversed.
246 Decline: The capture or credit is not voidable because the captu
re or credit information has already been submitted to your proc
essor. Or, you requested a void for a type of transaction that ca
nnot be voided.
247 Decline: You requested a credit for a capture that was previously voided.

Cybersource Built by Us 86
Built by Us

Reason Description
Code

248 Decline: The boleto request was declined by your processor.

250 Error: The request was received, but there was a timeout at the payment proces
sor.
251 Decline: The pinless debit card's use frequency or maximum amount
per use has been exceeded.
254 Decline: Account is prohibited from processing stand-alone refunds.
400 Soft Decline: Fraud score exceeds threshold.
450 Apartment number missing or not found.
451 Insufficient address information.
452 House/Box number not found on street.
453 Multiple address matches were found.
454 P.O. Box identifier not found or out of range.
455 Route service identifier not found or out of range.
456 Street name not found in postal code.
457 Postal code not found in database.
458 Unable to verify or correct address.
459 Multiple address matches were found (international).
460 Address match not found (no reason given).
461 Unsupported character set.
475 The cardholder is enrolled in Payer Authentication. Please authenticate the car
dholder before continuing with the transaction.
476 Encountered a Payer Authentication problem. Payer could not be authenticated
.
480 The order is marked for review by Decision Manager.
481 The order has been rejected by Decision Manager.
490 Your aggregator or acquirer is not accepting transactions from you at this time.
491 Your aggregator or acquirer is not accepting this transaction.
520 Soft Decline: The authorization request was approved by the iss
uing bank but declined by Cybersource based on your Smart Aut
horization settings.
700 The customer matched the Denied Parties List.
701 Export bill_country/ship_country match.
702 Export email_country match.

Cybersource Built by Us 87
Built by Us

Reason Description
Code

703 Export hostname_country/ip_country match.

Export Execution Logs

You can use the Execution Logs Saved Search feature of Oracle NetSuite to analyze logs.
Go to Cybersource Integration > SuiteApp Conguration > Export Logs. The Execution
Logs will be downloaded.

Support
If you require support with the SuiteApp, contact
[email protected] and provide these details:
• Steps to recreate the issue.
• SuiteApp version. Go to Cybersource Integration> SuiteApp Conguration. Click
SuiteApp Conguration. Find the version on the page footer.
• Export and share the logs. Go to Cybersource Integration > SuiteApp Conguration >
SuiteApp Conguration > Export Logs. The Execution Logs le is now downloaded in
your local system. Include the date and time of occurrence of the issue while sharing
the logs.
• Business Center merchant ID.
• Oracle NetSuite transaction ID, Business Center request ID.
• Payment event screenshots with raw request and raw response visible.
• Payment processing prole screenshots.
• Invoicing conguration screenshots (if applicable).
• Reporting set up screenshots (if applicable)
• Summary of the issue.

PrestaShop
The plugin for PrestaShop provides a payment solution for merchants using PrestaShop to
manage their orders. This section describes the payment methods and services the plugin
provides.
Supported payment methods:
• Credit and debit cards
• eCheck
• Click to Pay
• Apple Pay
• Google Pay
Supported payment services:
• Payment acceptance services:

Cybersource Built by Us 88
Built by Us

• Authorization only
• Sale (bundled authorization and capture)
• Electronic check debit (sale) for eCheck payment method
• Installment payments for Brazil, Chile, Colombia, Mexico, and Peru
• Grace period payments for Mexico
• Order management services:
• Capture an authorization (not for eCheck)
• Multiple partial captures (not for eCheck)
• Standard and partial refunds
• Standard and partial void captures (not for eCheck)
• Standard and partial void refunds
• Full authorization reversal (not for eCheck)
• Token Management Service (TMS) for credit and debit card payments:
• Create payment token along with authorization
• Update an existing token along with authorization
• Update an existing token from My Account section
• Delete an existing token from My Account section
• Create payment token for new payment methods during checkout
• Make a payment with a stored token during checkout
• Reporting services that allow you to import these Cybersource Business Center
reports into PrestaShop:
• Transaction Request Report
• Payment Batch Detail Report
• Conversion Detail Report

Release Information
This section provides information about the plugin releases.

Release Version Release Date Support End Date

2.1.0 April 5, 2022 September 29, 2022

3.1.0 September 29, 2022 April 5, 2022
4.1.0 September 21, 2023 July 2026
4.2.0 December 13, 2023 December 13, 2026

Version 4.2.0 includes the following enhancements:

• Cybersource authentication signature updated.
• Compatible with PrestaShop versions 1.7.6.0 to 1.7.8.10
Version 4.1.0 includes enhancements that provide customers with a exible and
convenient purchasing experience:

Cybersource Built by Us 89
Built by Us

• Installment payment options for customers in Mexico, Brazil, Colombia, Chile, and Peru.
This feature enables customers to conveniently split their payments into installments.
• Grace period payment options for customers in Mexico. This feature enables customers
to delay a payment for a specied period after making a purchase.
• Expanded card payment services, which includes credit and debit card options. This
feature enables customers to securely make payments using their preferred card type.

Installation
Before you install the plugin, make sure that these requirements are met:
• You are using PrestaShop version 1.7.x.
• You have created a Business Center account and have generated Business Center REST
API keys:
• To create an account, go to the Business Center Registration website.
• To generate REST API keys, see Getting Started with REST Developer Guide.
• You have created an Apple Developer account if you are processing Apple Pay
transactions.
• You have created an Google Pay Developer account if you are processing Google Pay
transactions.
Follow these steps to install the plugin:
1. Download the Plugin from the PrestaShop website to your local system.
PrestaShop Modules > Payments > Other Payments > Cybersource Ofcial
2. Open PrestaShop Back Ofce and choose Modules > Module Manager from the
Dashboard.
The Module Manager page opens.
3. Click Upload a Module on the Module Manager page.
The Upload a module pane appears.
4. Click select le from the Upload a module pane and select the le you downloaded to
your local system. You can also drag the le into the Upload a module pane.
The pane displays the status of the installation. After the Plugin is installed, the pane
indicates that the module is installed. You can close it or click Congure to congure
the Plugin.

Conguration
This section describes how to set up the plugin. You complete most of the Plugin
conguration using PrestaShop Back Ofce.
• For information about the conguration settings for the Plugin, see Conguration
Settings on page 91.
• For information about how to access the conguration settings for the Plugin, see
Conguring Plugin Settings on page 91
When merchants support digital payment processing using Apple Pay or Google Pay, they
must complete some setup using the Apple Pay or Google Pay Developer websites.

Cybersource Built by Us 90
Built by Us

Conguring Plugin Settings

Use PrestaShop Back Ofce to congure these settings:
• General settings
• Payment method settings
• Fraud management settings
• Report settings
• Latin American country settings, if they apply
For details about these settings, see Conguration Settings on page 91.
To congure these settings, follow these steps:
1. Open PrestaShop Back Ofce and select Modules > Module Manager from the
Dashboard. The Module Manager page opens.
2. Find the Plugin in the Payment section on the Module Manager page, or enter
Cybersource Ofcial in the Search eld and click Enter.
3. Click Congure. The Congure Cybersource Ofcial page opens.
4. Under each tab, enter your conguration information, and click Save.
Conguration Settings

This section describes the conguration settings for the Cybersource Ofcial Plugin.

General Settings
Sandbox Mode When sandbox mode is set to Yes,
PrestaShop operates in sandbox (test)
mode so that you can test new changes and
conduct experiments.
When sandbox mode is set to No,
PrestaShop operates in production (live)
mode.
Merchant ID This setting species the shop or store
Cybersource Merchant ID, which is a unique
Cybersource identier for the merchant.
Merchant Key ID This setting identies a specic key or
token provided by a payment gateway to
authenticate and authorize the merchant's
integration with the gateway.
Merchant Secret Key This setting identies a condential or
private key used for secure communication
between the merchant's online store and a
payment gateway.
Payer Authentication/3-D Secure When this setting is set to Yes, customers
may receive one-time-password (OTP)
pop-ups when placing orders using credit

Cybersource Built by Us 91
Built by Us

cards. This enables the exchange of data

between the merchant, card issuer, and,
when necessary, the customer, to validate
that the transaction is being initiated by the
rightful owner of the account. This may be
a requirement for the country in which you
are trading.
Enhanced Logs When this setting is set to Yes, logs
are generated and can be accessed by
selecting Congure > Advanced Parameters
> Logs.
Payment Action Use the drop-down menu to choose one of
these transaction settings:
• Authorize: when selected, this setting
generates an authorize-only transaction
for a customer order.
• Sale: when selected, this setting
generates a sale (bundled authorization
and capture) transaction for a customer
order.

Payment Settings
Card Payment When this setting is set to Yes, customers
can use a credit or debit card as a payment
method.
Click to Pay When this setting is set to Yes, customers
can use Click to Pay as a payment method.
When the setting is set to Yes, you must also
provide a Click to Pay API key, which you
can congure in the Cybersource Business
Center.
Google Pay When this setting is set to Yes, customers
can use Google Pay as a payment method.
When the setting is set to Yes, you must
also enter the Google Pay Merchant ID
and Google Pay Merchant Name, which
you obtain from a Google Pay Developer
account.
Apple Pay When this setting is set to Yes, customers
can use Apple Pay as a payment method.
When the setting is set to Yes, you must
also enter the Apple Pay Merchant ID,

Cybersource Built by Us 92
Built by Us

Path to Certicate (le), and Path to Key

(le), which you obtain from an Apple
Developer account. See Enabling Apple Pay
on page 97 for information about the
requirements for enabling Apple Pay and
generating these les.
eCheck When this setting is set to Yes, customers
can use eCheck as a payment method.

Fraud Management Settings

Fraud Management When this setting is set to Yes, merchants
can identify and prevent fraudulent
activities that might occur when their
customers are using PrestaShop.
Tokenization When this setting is set to Yes, customers
can safely save and store their card
information so that it can be used for future
purchases.
Enforce Strong Customer Authentication When this setting is set to Yes, the card
holder is 3-D Secure challenged when
saving their card information.

Important
The Enforce Strong Customer
Authentication setting is
available only when the Payer
Authentication/3-D Secure
(general Plugin setting) and
Tokenization (fraud management
Plugin setting) are enabled.

Limited Saved Card Rate When this setting is set to Yes, merchants
can specify the number of cards that
customers can save in their account, and
they can specify the amount of time for
which that card information can be saved:
1. Saved Card Limit Count: species the
maximum number of cards a customer
can save to their account.
2. Saved Card Limit Time Frame: species
the time frame (from 1 to 24 hours) for

Cybersource Built by Us 93
Built by Us

which customers can save the specied

number of cards to their account.

Google reCAPTCHA When this setting is set to Yes, merchants

enter the Google reCAPTCHA keys, which
are used to provide an advanced risk
analysis engine and adaptive challenges to
keep malicious software from engaging in
abusive activities on your website:
• reCAPTCHA Site Key
• reCAPTCHA Secret key, which can be
congured on the Google reCAPTCHA
website
See Generating a Google reCAPTCHA Site
Key and Secret Key on page 99 for the
steps on how to generate these keys.
Device Fingerprint When this setting is set to Yes, merchants
can identify and track devices that access
their website such as computers, smart
phones, and tablets.

Report Settings
Transaction Request Report This report includes details for individual
transactions that are processed each day.
When this setting is set to Yes, this report
is downloaded from the Business Center to
PrestaShop. The report is downloaded to
different locations, depending on the mode
in which PrestaShop is operating:
• In sandbox (test) mode,
the report downloads to
{PrestaShopModuleInstallationDirectory}/
cybersourceofcial/Reports/Sandbox
• In production (live) mode,
the report downloads to
{PrestaShopModuleInstallationDirectory}/
cybersourceofcial/Reports/Production.

Important
Cybersource strongly recommends
that PrestaShop and the Business
Center operate in the same time

Cybersource Built by Us 94
Built by Us

zone so that the Transaction

Request Report and Payment Batch
Detail Report work properly.

Payment Batch Detail Report This report includes transactions that

are processed with the applications. This
report is available shortly after captured
transactions are batched.
When set to Yes, this report is downloaded
from the Business Center to PrestaShop.
The report is downloaded to different
locations, depending on the PrestaShop
mode:
• In sandbox (test) mode, the
report downloads to this location:
{PrestaShopModuleInstallationDirectory}/
cybersourceofcial/Reports/Sandbox
• In production (live) mode, the
report downloads to this location:
{PrestaShopModuleInstallationDirectory}/
cybersourceofcial/Reports/Production

Important
Cybersource strongly recommends
that PrestaShop and the Business
Center operate in the same time
zone so that the Transaction
Request Report and Payment Batch
Detail Report work properly.

Conversion Detailed Report This report retrieves Case Management

changes from the Business Center at
regular intervals to ensure that orders are
updated in PrestaShop.

Latin American Country Settings

Installments When this setting is set to Yes, customers
can make installment payments ranging
from 1 to 24 months. You can congure
installment payment settings for these
Latin American countries: Brazil, Chile,
Columbia, Mexico, and Peru. See Enabling
Installment Payments on page 96 for how
to congure installment payments.

Cybersource Built by Us 95
Built by Us

Merchant Descriptor Name This conguration applies only to Brazil and

Mexico.
This setting enables merchants to add
a short description that appears on
a customer credit card statement or
bank statement to identify a particular
transaction.
Grace Period This setting stipulates a time period after
a due date during which a payment can
be made without incurring late fees or
penalties. See Enabling Grace Period
Payments on page 96 for further
information about conguring grace period
payments for Mexico, the only country for
which this setting currently applies.

Enabling Installment Payments

Use PrestaShop Back Ofce to enable installment payments, which are
applicable for payments in Brazil, Chile, Colombia, Mexico, and Peru.
1. Open PrestaShop Back Ofce and select Modules > Module Manager from the
Dashboard. The Module Manager page opens.
2. Find the Plugin in the Payment section on the Module Manager page, or enter
Cybersource Ofcial in the Search eld and click Enter.
3. Click Congure. The Congure Cybersource Ofcial page opens.
4. Select the LATAM SETTINGS tab.
5. From the Country drop-down menu, choose the country for which you want to
congure the installment payments.
6. Choose the relevant options from each drop-down menu for these settings and click
Save:
• Processor
• Installments (In Months)
• Choose Card Types
When a specic card type is selected for a processor in a certain country, it cannot be
chosen for any other processor within that country.

Enabling Grace Period Payments

Use PrestaShop Back Ofce to enable grace period payments, which are
applicable only for payments in Mexico.
1. Open PrestaShop Back Ofce and select Modules > Module Manager from the
Dashboard. The Module Manager page opens.

Cybersource Built by Us 96
Built by Us

2. Find the Plugin in the Payment section on the Module Manager page, or enter
Cybersource Ofcial in the Search eld and click Enter.
3. Click Congure. The Congure Cybersource Ofcial page opens.
4. Select the LATAM SETTINGS tab.
5. From the Country drop-down menu, choose Mexico.
You must select Mexico as the country to get access to the Grace Period setting
because this setting is only applicable in Mexico.
6. To enable grace period payments, set Grace Period to Yes, and click Save.

Enforcing Strong Customer Authentication

Select the Enforce Strong Customer Authentication setting to prompt a 3-
D Secure challenge when a customer saves their credit card information.
The customer is 3-D Secure challenged when a transaction is declined as
reported by response code 478 (Strong Customer Authentication required).
After the transaction is declined, another request is sent for the same order.

Important
The Enforce Strong Customer Authentication setting is available only when the
Payer Authentication/3-D Secure (general Plugin setting) and Tokenization (fraud
management Plugin setting) are enabled. See Conguration Settings on page 91
for information about these settings and Conguring Plugin Settings on page 91
for information about how to set them.
Follow these steps to enable Enforce Strong Customer Authentication:
1. Open PrestaShop Back Ofce and select Modules > Module Manager from the
Dashboard. The Module Manager page opens.
2. Find the Plugin in the Payment section on the Module Manager page, or enter
Cybersource Ofcial in the Search eld and click Enter.
3. Click Congure. The Congure Cybersource Ofcial page opens.
4. Select the FRAUD MANAGEMENT SETTINGS tab.
5. Set the Enforce Strong Customer Authentication setting to Yes.
6. Click Save.

Enabling Apple Pay

This section describes the requirements for conguring and using the plugin to process
Apple Pay transactions through PrestaShop.

Account and Website Requirements

Before you congure the Plugin to process Apple Pay transactions, ensure that these
requirements are met:
• You have a Cybersource Business Center account.
• You have an Apple Developer account.

Cybersource Built by Us 97
Built by Us

• Your website:
• Adheres to the Apple Pay guidelines specied on the Acceptable Use Guidelines for
Apple Pay on the Web page on the Apple Pay Developer site.
• Uses the HTTPS protocol. For more information about this requirement, see Setting
Up Your Server page on the Apple Pay Developer site.
Setting Up Apple Pay

This section describes the requirements for setting up Apple Pay to process
Apple Pay transactions through PrestaShop.
1. Follow the instructions for enabling Apple Pay on the Setting Up Apple Pay page on the
Apple Developer website. Before proceeding, ensure that you have completed these
steps:
a. Create a Merchant ID
b. Create a Payment Processing Certicate
c. Validate the merchant domain
d. Create a Merchant Identity Certicate
2. Download the Merchant Identity Certicate.
3. Convert the downloaded certicate to a PEM format:

openssl x509 -inform der -in merchant_id.cer -out merchant_id.pem

After the certicate is converted, it displays in the Keychain Access menu.

4. Double-click the certicate on the Keychain Access menu. The certicate is installed
and the associated private key displays in the Keychain Access menu.
5. Right-click the private key, select the Export option, and export the key as
merchant_id.p12.
6. Convert the exported private key to a KEY format:

openssl pkcs12 -in merchant_id.p12 -out merchant_id.key -nodes

7. Upload the converted key (merchant_id.key) and certicate (merchant_id.pem) les to

your website server.
8. Open PrestaShop Back Ofce and select Modules > Module Manager from the
Dashboard. The Module Manager page opens.
9. Find the Plugin in the Payment section on the Module Manager page, or enter
Cybersource Ofcial in the Search eld and click Enter.
10.Click Congure. The Congure Cybersource Ofcial page opens.
11. Select the PAYMENT SETTINGS tab and enter the complete path to the certicate and
key in the Apple Pay section.

Enabling Google Pay

This section describes the requirements for using and conguration steps to enable the
plugin to process Google Pay transactions through PrestaShop.

Cybersource Built by Us 98
Built by Us

Account Requirements
Before you congure the Plugin to process Google Pay transactions, ensure that you have
a Google Pay Developer account.
Generating a Google reCAPTCHA Site Key and Secret Key

The Google reCAPTCHA site and secret keys allow you to safely process
Google Pay payments. These keys protect your website when your customers
use Google Pay to make payments.
1. Go to the Google reCAPTCHA website and click the Admin Console link.
2. Complete these steps to register a new site:
a) Enter a label that will be used to identify the site.
b) Choose the Score based (v3) option for the reCAPTCHA type.
c) Enter the domain on which PrestaShop is hosted.
d) Enter the email address of the website owner.
e) Check the box to accept the terms of service and click Submit.The reCAPTCHA site
key and secret key are generated.
3. Open PrestaShop Back Ofce and select Modules > Module Manager from the
Dashboard. The Module Manager page opens.
4. Find the Plugin in the Payment section on the Module Manager page, or enter
Cybersource Ofcial in the Search eld and click Enter.
5. Click Congure. The Congure Cybersource Ofcial page opens.
6. Select the FRAUD MANAGEMENT SETTINGS tab and enter the keys in the Google
reCAPTCHA section of the tab.

Scheduling Report Generation

Schedulers on a Linux, Mac, or Windows system are used to set up how often a specied
report is generated. Schedulers for Linux and Mac systems are set up using a Cron Tab.
The scheduler for a Windows system is set up using the Windows Task Scheduler app.
When setting up a schedule for generating a specic report, use this format:
• Format: <shop domain name>/module/cybersourceofcial/paymentReport
• Example: http://www.prestashop_1.7.8.6.com/module/cybersourceofcial/
paymentReporth

Cron Tab Syntax for Mac and Linux Systems

When setting up the reporting schedule on a Linux or Mac system, you use crontab
commands that determine how often and when the report is generated.
The syntax is:

* * * * * [command]

The asterisk (*) represents each of these timing parameters:

• Minute (0-59)
• Hour (0-23)

Cybersource Built by Us 99
Built by Us

• Day of Month (1-31)

• Month (1-12)
• Day of week (0-6), (0-Sunday)
For example, these timing parameters indicate how often a specied report is generated:
• * * * * * [command]: Runs every minute of every day of every week of every month.
• 0 * * * * [command]: Runs every hour of every day of every week of every month.
• 30 2 * * * [command]: Runs at 2:30 a.m. every day of every week of every month.
• 0 0 2 * * [command]: Runs once a month every month on the second day of the month.
• 0 * * * 1 [command]: Runs every Monday at every hour.
• 0,10,20 * * * * [command]: Runs on 0, 10, 20 minute of every hour of every day of every
week of every month.
• 0 5-10 * * * *[command]: Runs every hour between 5 and 10 a.m.
• @reboot [command]: Runs every time after the server reboots.
• */5 * * * * [command]: Runs every 5 minutes of every day.
Setting Up Cron Scheduler for Linux

1. Open a Linux terminal.

2. Enter crontab-e to enter editor mode. For example:

root@PrestashopQA4:/etc# crontab -e

3. Enter the command to set the timing for the cron job. For example, this command sets
the cron job to run every 15th minute of every hour, every day, every week, and every
month:

15 * * * * curl https://www.dev.prestahop.cybsplugin.com/mps1760/module/mybank/paymentReport

4. Enter Ctrl + X to close the editor.

5. Enter the crontab -l command to check the scheduled cron job. For example:

root@PrestashopQA4:/etc# crontab -l

The scheduled cron job should appear on the screen. For example:

15 * * * * curl https://www.dev.prestahop.cybsplugin.com/mps1760/module/mybank/paymentReport

Setting Up Cron Scheduler for Mac

1. Open a Mac terminal.

2. Enter crontab-e to enter editor mode.

C02X63PRJG5J:~ $crontab -e

Cybersource Built by Us 100

Built by Us

3. Enter the command to set the timing for the cron job. For example, this command sets
the cron job to run every 45th minute of every hour, every day, every week, and every
month:

45 * * * * curl https://www.qa.prestahop.cybsplugin.com/mps1786/module/cybersourceofcial/
paymentReport

4. Enter Esc + : + w + q to close the editor. The editor closes and displays this message:

crontab: installing new crontab

5. Enter the crontab -l command to check the scheduled cron job.

C02X63PRJG5J:~ $crontab -l

The scheduled cron job should display on the screen. For example:

45 * * * * curl https://www.qa.prestahop.cybsplugin.com/mps1786/module/cybersourceofcial/
paymentReport

Setting Up Task Scheduler for Windows

1. Open the Task Scheduler app and click Create Task.

The Create Task pane displays.
2. Select the General tab and enter a name for the task in the Name eld.
3. Select the Triggers tab and click New.
The New Trigger pane displays.
4. Make the desired timing selections for the task in the New Trigger pane and click OK.
5. Select the Actions tab in the Create Task pane and click New.
The New Action pane displays.
6. Select and enter this information in the New Action pane and click OK.
• Action drop-down menu: choose Start a program.
• Program/script eld: enter the curl command.
• Add arguments (optional): enter the reporting URL.
7. Click OK in the Create Task pane to create the task. The new task displays in the Task
Scheduler Summary.

Using the Plugin

The plugin provides merchants a frictionless way to process payments, prevent fraud, and
generate reports within the Business Center while making it easy for customers to place
and cancel orders, and save or update stored credit or debit card information.

Order Management
This section describes the order management process that occurs after a customer
places an order.
The order management process is handled using these PrestaShop ofce interfaces:

Cybersource Built by Us 101

Built by Us

• PrestaShop Front Ofce: customers use this interface to place and cancel orders, and
save or update stored credit or debit card information.
• PrestaShop Back Ofce: merchants use this interface to congure the Plugin and
manage orders, which includes these tasks:
• Capture an authorization (multiple partial captures are also supported).
• Reverse an authorization (full authorization is supported).
• Void a capture (partial void is supported).
• Refund a capture (standard and partial refunds are supported).
• Void a refund (partial void is supported).
Merchants also use the Back Ofce interface to congure fraud management and
reporting services.
Order Status
Order status is triggered and updated when transactions are processed. The plugin
supports custom and default statuses for orders.
Custom order statuses:
• Awaiting payment
• Awaiting cancel
• Cancel rejected
• Cancelled, refund initiated
• Payment pending for review
• Partial payment accepted
• Partial payment cancelled
• Payment cancelled
• Partial refunded (before shipped)
• Partial refunded (after shipped)
• Partial refund cancelled (before shipped)
• Partial refund cancelled (after shipped)
• Payment error
• Refund cancel error
• Payment cancel error
• Refund error
• Refund cancelled
• Order cancelled by merchant
Default order statuses:
• Payment accepted
• Cancelled
• Shipped
• Delivered
• Refunded
Only the shipped and delivered statuses can be manually updated.

Cybersource Built by Us 102

Built by Us

Order Management Workows

This section describes the order of events that the merchant completes after a customer
submits an order.
After-Authorization Workow
This workow comprises the sequence of events that occur after a customer places
a new order using PrestaShop Front Ofce. The workow shows how the order status
is updated when the authorized transaction is captured or reversed (full authorization
reversal).
1. The new order displays in PrestaShop Back Ofce, and the order status is Awaiting
payment.
2. The merchant chooses one of these options:
• Standard capture.
• Partial capture.
• Cancel products. For a full authorization reversal, the merchant must also cancel the
order, which requires that they select all the quantities and all the items included in
the order.
A partial authorization reversal is not supported.
3. When the merchant initiates a full authorization reversal, the authorization is cancelled
and the order status is set to Cancelled.
4. When the merchant initiates a multiple partial capture, they choose how many
quantities to capture and whether to include the shipping costs.
After multiple partial captures are processed, the order status is set to Partial payment
accepted.
5. When the merchant initiates a full capture, the entire authorization amount is captured,
and the order status is set to Payment accepted.
After-Capture Workow
This workow comprises the sequence of events that occur after an authorization is
captured. The workow shows how the order status is updated when the captured
transaction is refunded or voided.
1. The merchant chooses one of these options:
• Standard refund.
• Partial refund
• Void capture.
2. If the merchant voids the capture, the captured transactions are voided.
When all quantities of the transaction are captured, the entire order is voided and the
order status is set to Payment cancelled.
If only a few quantities are captured, only the captured quantities are voided, and the
order status is set to Partial payment accepted.
3. If the merchant initiates a standard refund before updating the order status to shipped,
the order status is set to Partial refunded (before shipped) until the refunded amount
becomes equal to the captured amount. When the refunded amount becomes equal to
the captured amount, the order status is set to Refunded.

Cybersource Built by Us 103

Built by Us

4. When the merchant selects a refund after updating the order status to shipped, the
order status is set to Partial refunded (after shipped) until the refunded amount
becomes equal to the captured amount. After the refunded amount becomes equal to
the captured amount, the order status is set to Refunded.
To refund the amount of an order, merchants can either generate a voucher or a credit
slip for the refund. Depending on the type of refund they select and whether they issue
a voucher or a credit slip, one of these actions occurs:
• When the merchant chooses Generate a voucher for a partial refund, the sum of the
items is not refunded. Instead, a voucher is generated that can be used for future
transactions.
• When the merchant chooses Generate a voucher and enters the amount in the
shipping costs eld for a partial refund, then a voucher equal to the sum of the items
and the shipping amount is generated.
• When the merchant chooses Generate a credit slip for a standard refund, the sum of
the items is refunded.
• When the merchant chooses both Generate a credit slip and Repay shipping costs for
a standard refund, the sum of the items and the shipping amount are both refunded.
• When the merchant chooses both Generate a voucher and Repay shipping costs for
a standard refund, a voucher equal to the sum of the items and shipping amount is
generated.
• When the merchant chooses both Generate a voucher and Generate credit slip for a
standard refund, a voucher is generated and a refund for the sum of the items is not
generated.
After-Refund Workow
This workow comprises the sequence of events that occur when the merchant voids a
refund under specic conditions:
• When the refund is processed before the order is shipped, the refund is cancelled and
the order status is set to Partial refund cancelled (Before shipped).
• When the refund is processed after the order is shipped, the refund is cancelled and
the order status is set to Partial refund cancelled (After shipped).
• When the voided refund amount is equal to the refund amount, the refund is cancelled
and the order status is set to Refund cancelled.

Customer Tasks
Customers can use the My Account option on the merchant's PrestaShop website to
manage orders and their payment information. The following sections contain the steps to
complete these tasks.
Saving Credit/Debit Card Information

Saving card information enables customers to use that information for future
transactions. Using PrestaShop Front Ofce, customers can save their
card information during the checkout process, or they can add their card
information to their registered PrestaShop accounts using the My cards
feature.

Cybersource Built by Us 104

Built by Us

If a customer wants to save their card information during the checkout process, they can
select the Save my card for future payment option when entering their credit/debit card
payment (as shown below) during checkout.
The card information can also be saved on the My cards page in PrestaShop:
1. Open PrestaShop Front Ofce.
2. Go to the My cards section of the page and click ADD CARD.
If no current address is associated with the customer account, the customer is
prompted to add an address. The customer can enter the required address information
and click Save.
If there is already an address associated with the customer account, the customer can
select and use the address or add a new address.
After the address information is complete and selected, the customer can update the
card expiration information, if needed, or delete the existing card from the account.
3. To update the expiration information for the card (expiration month/year), the
customer clicks Update, or clicks Delete to remove the card from the account. The
customer can also change the billing address for the card by clicking Change.
Customers can add only the number of cards that the merchant specied in the
account conguration. The updated card information is tokenized and securely saved.
The customer can use the saved card information for future transactions without
having to enter that card information during the checkout process.
Selecting a Default Credit/Debit Card

When a customer has multiple cards associated with their account, they can
designate the default card. By default, the rst card added to the account
is set as the default card. In the My cards page, the default card is identied
with an asterisk (*) that appears to the right of the card number.
To change the default card, the customer follows these steps:
1. Open PrestaShop Front Ofce.
2. Open the My cards page. The page displays the saved cards associated with the
account.
3. Choose a card to set as the default card, and choose More > SET AS DEFAULT. The card
is set as the default card.
The default card cannot be deleted unless all other saved cards from the My cards
section are deleted.
Cancelling an Order

This task provides the steps a customer takes to cancel an order. They
cannot cancel an order if the order is in review with the merchant.
1. Open PrestaShop Front Ofce.
2. Select My Account > Order History. The Order history page displays the customer's
orders.
3. Select the Details icon for the order to cancel. The Order details page appears.
4. Click the Cancel icon to cancel the order.
An Order cancellation conrmation notice appears.

Cybersource Built by Us 105

Built by Us

5. Click Yes on the Order cancellation conrmation notice to cancel the order.
The order is cancelled and the order status is set to Cancelled.
If the order was a sales transaction or was captured, the cancellation is sent to the
merchant and the status is set to Awaiting cancel.
After the customer cancels an order, the merchant can accept or reject the order
cancellation (as instructed in Processing a Cancelled Order on page 106). If the
merchant accepts the cancellation request, a refund for the order amount is initiated,
and the order status is set to Cancelled, refund initiated. If the merchant rejects the
cancellation request, the order status is set to Cancel rejected.

Merchant Tasks
Merchants use PrestaShop Back Ofce to manage orders. This section describes the
steps to complete these tasks.
Processing a Cancelled Order

When a customer cancels an order, a request is sent to the merchant, and

the order status is set to Awaiting cancel. Merchants can accept or reject an
order that a customer cancels.
1. Open PrestaShop Back Ofce and select Orders > Orders from the Dashboard.
2. Locate and select the order the customer cancelled. The information for that order
displays.
3. Choose one of these options:
• Click Accept cancellation to accept and process the cancelled order. A refund for
the order amount is processed, and the order status is set to Cancelled, refund
initiated.
• Click Reject cancellation to reject the cancelled order. The order status is set to
Cancel rejected.
Processing a Merchandise Return

When a customer requests to return merchandise, the information appears

on the Merchandise Returns page in PrestaShop Back Ofce. Follow these
steps to process the return.
1. Open PrestaShop Back Ofce and select Customer Service > Merchandise Returns.
The Merchandise Returns page displays and identies the order or orders for which
customers have requested a return.
2. Select the order for which you want to process the return. The Edit > Return
Merchandise Authorization (RMA) menu displays.
3. Choose one of these options from the Status drop-down menu and click Save:
• Waiting for conrmation
• Waiting for package
• Package received
• Return completed

Cybersource Built by Us 106

Built by Us

The status is updated for the order on the Merchandise Returns page. Next, you can
proceed with selecting a return or refund option for the order.
4. Select Orders > Orders from the Dashboard.
5. Select the order for which you want to process a return, and select one of these
options:
• Return products
• Partial refund

Fraud Management
The plugin provides fraud management functionality for merchants who also use
the Cybersource Business Center. You can apply fraud management functionality to
transactions in these situations:
• Fraud management is enabled in the plugin.
• You have a fraud management prole in the Business Center.
Fraud screening includes these features:
• Fraud Management Essentials (FME): used to enforce the rules created by the
Cybersource Machine Learning System (MLS). Fraud management is used to dene the
merchant’s rules.
• Fraud Management Rules:
• When the decision status from the Business Center is
AUTHORIZED_PENDING_REVIEW or PENDING_REVIEW, the order is in review and the
order status is set to Payment pending for review.
• When the decision status from the Business Center is AUTHORIZED_RISK_DECLINED,
the order is rejected and the order status is set to Order cancelled by merchant.
The table below describes the possible decisions, outcomes, and timing that Decision
Manager uses when an order is triggered for review.

Important
When the following transactions are in a Decision Manager review state, certain
settlement considerations apply:
• For authorizations: while accepting this transaction it is not recommended to
settle it in the Business Center. When the transaction is settled in the Business
Center, the follow-on services initiated from PrestaShop Back Ofce are
impacted.
• For sales:
• The entire authorized amount should be settled in the Business Center when
accepting the transaction. When the settlement is not performed in the
Business Center, the follow-on services initiated from PrestaShop Back
Ofce fail.

Cybersource Built by Us 107

Built by Us

• A follow-on void capture will not initiate from PrestaShop Back Ofce. While
accepting review transactions, merchants should not select the settle option.

Decision Manager Decisions, Execution Timings, and Outcomes for Orders

Decision Execution Timing Outcome of Decision

Monitor Before authoriza Authorization is successful and no action

tion from the Decision Manager is required. Use this decisio
n to understand the outcome of a rule.
Accept Before authoriza The order is processed normally and is pla
tion ced successfully.
Review Before authoriza The authorization is successful, and follo
tion w-on services are put on hold until the merchant accep
ts or rejects it. The order status is set to
Payment pending for review.
Reject Before authoriza The order is rejected and the authorization
tion is not processed. The merchant is not able to view the
order in PrestaShop Back Office.
Monitor After authorizati The authorization is successful and no ac
on tion from Decision Manager is required. Use this decisio
n to understand the outcome of a rule.
Accept After authorizati The order is processed normally and placed
on successfully.
Review After authorizati The authorization is successful, and follo
on w-on services are put on hold until the merchant accep
ts or rejects it. The order status will be se
t to Payment pending for review.
Reject After authorizati The original authorization is successful an
on d then is automatically reversed and the order status is
set to Order cancelled by merchant.

Reporting
The plugin provides reporting functionality for merchants who also use the Business
Center. You can import these reports from the Business Center into PrestaShop:
• Transaction Request Report: includes details for individual transactions that are
processed each day.
• Payment Batch Detail Report: includes transactions that are processed with the
applications. This report is available shortly after captured transactions are batched.
• Conversion Detail Report: includes Case Management changes recorded in the
Business Center to ensure that updated orders are also included in PrestaShop. This
report is generated at regular intervals and includes the results of the converted

Cybersource Built by Us 108

Built by Us

orders for each reviewer. This information provides an overview of all orders that were
not immediately accepted.

Scheduling
The Plugin reporting functionality works with a system scheduler to generate and update
reports for PrestaShop. There are some Cron Job modules available for PrestaShop, such
as the Cron Tab, that support reporting. Merchants can use any Cron Job module that
PrestaShop supports or any other online Cron service provider to generate reports.
See Scheduling Report Generation on page 99 for information about how to
schedule report generation.

Workow
The reports are processed and orders are updated in PrestaShop as described in this
workow:
1. Orders with an AUTHORIZED_PENDING_REVIEW or AUTHORIZED_RISK_DECLINED
status are included in the ps_cybersourceofcial_order table in the PrestaShop
database.
2. If a review is trigged for an order based on the prole rule in Decision Manager, a
Payment pending for review order status displays for that order on the PrestaShop
Back Ofce Orders page.
3. The merchant uses the Business Center to accept the order that is in review, and, if not
already enabled, the merchant enables the reports using the Report Settings on the
Plugin Conguration page.
4. The scheduler runs the report at regular intervals according to the intervals the
merchant congured. The order is accepted or rejected by the merchant in the
Business Center, is retrieved, and the new status is updated as AUTHORIZED or
DECLINED. The updated order status displays in the ps_cybersourceofcial_order table
in the PrestaShop database.
5. The original decision and the new decision are updated and displayed in the
ps_cybersourceofcial_conversion_detail_report table in the PrestaShop database.
6. The order is updated as Awaiting payment status for the authorization and displayed on
the PrestaShop Back Ofce Orders page. The payment is accepted for the sale and any
associated follow-on transactions (capture, void capture, refund, void refund, and full
authorization reversal).

Testing
If you have not done so already, congure these settings using PrestaShop
Back Ofce. See Conguring Plugin Settings on page 91 for information about
how to access these settings:
• General Settings: merchant ID, merchant key ID, and/or merchant secret key
• Payment Settings: applicable payment methods

Cybersource Built by Us 109

Built by Us

After conguring the Plugin, complete this task to test the conguration
using PrestaShop Front Ofce to place an order and PrestaShop Back Ofce
to manage the order.
1. Open PrestaShop Front Ofce to place an order.
2. Enter any required personal information and select the payment method that you want
to use to place the order.
3. Enter the card information you want to use to place the order and click Pay. If the order
is successful, an order conrmation message displays.
4. Open PrestaShop Back Ofce to manage the order.
5. Select Orders > Orders from the Dashboard. The Orders page displays and lists all
active orders.
6. Select and open the order you processed in Step 1. The order status for the order
should display Awaiting payment.
7. Click Standard Capture icon to capture the authorized amount, and click Yes to capture
the entire order. The order status changes to Payment accepted.
8. Click Standard Refund to refund the full captured amount. The order status changes to
Refunded.
9. Click Void Refund to void the refunded amount. The order status changes to Refund
cancelled.
For more information about testing, including test cards, see
https://developer.cybersource.com/hello-world/testing-guide-v1.html

Upgrading
You can install a newer version of the plugin using PrestaShop Back Ofce.
1. Open PrestaShop Back Ofce and select Improve > Modules > Module Manager from the
Dashboard.
2. Click the arrow next to the plugin Congure icon and choose Upgrade from the drop-
down menu.

Troubleshooting
This section might help you resolve specic issues that can occur during the installation
and upgrade processes for the plugin.

Issue: PrestaShop Language Pack Installation Error

You get a 1: Cannot download language pack "en" error message when installing the Plugin.
To resolve this issue, complete these steps:
1. Locate and open the Tools.php le, which resides in htdocs/PrestaShop root/Classes
directory on your system.
2. Search for and select this string in the Tools.php le:
curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, false);
3. Replace the selected string with this string:

Cybersource Built by Us 110

Built by Us

curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, true);

4. Save the le and reload your browser page.

Issue: Debug Mode is Enabled in Production

When debug mode is enabled in the production instance, you need to disable it.
1. Open PrestaShop Back Ofce and select Congure > Advanced Parameters from the
Dashboard. The Advanced Parameters page appears.
2. Select Performance from the Advanced Parameters page.
3. Set Debug mode to No.

Issue: User Interface Appears Incorrectly After a Plugin Upgrade

After upgrading the Plugin, if the user interface looks incorrect, you need to clear the
cache.
1. Open PrestaShop Back Ofce and select Congure > Advanced Parameters from the
Dashboard. The Advanced Parameters page appears.
2. From the Advanced Parameters page, click Performance.
3. Click Clear Cache.

Conguring and Testing Email

Follow these steps to congure the email that customers receive during
order management.
1. Open PrestaShop Back Ofce and select Advance Parameters > Email from the
Dashboard. The email page appears.
2. Select these options from the Email section of the page to congure how email is sent:
• Send emails to: Customer service
• Set my own SMTP parameters (for advanced users ONLY)
• Both HTML and text formats
• Yes for log emails
3. Select and specify this information for your SMTP parameters:
• Mail domain name: do not enter information (leave this eld empty)
• SMTP server: enter the server domain. For example, smtp.gmail.com.
• SMTP username: enter the email address from which emails are sent. For example,
[email protected].
• SMTP password: enter the password for the email address provided above.
• Encryption: select TLS
• Port: enter 587
4. Click Save to save the conguration.
5. Test your email conguration by entering an email address to which you want to send
the test message, and click Send a test email.

Cybersource Built by Us 111

Built by Us

Conguring Order Status Visibility

You can choose to hide order status messages that you do not want
customers to view.
1. Open PrestaShop Back Ofce, and select Customer Service > Order Messages from the
Dashboard.
2. Click the pencil icon beside the order status message you would like to hide.
3. In the Order status pane, select hide this status in all customer orders.
4. Click Save.

Troubleshooting Assistance
For help with troubleshooting, contact [email protected] and provide
the following information:
• Summary of the issue
• Steps needed to reproduce the issue
• Platform version
• Plugin version
• Platform Merchant ID
• Conguration screenshots
• List of themes/additional extensions installed
• Log le and any other data or screenshots related to the issue

Shopify
The Cybersource app on Shopify provides commerce tools to start, grow, market, and
manage retail businesses. You can accept payments in multiple currencies and get paid in
your local currency. The Cybersource app on Shopify supports popular payment methods
to meet your business needs.
The Cybersource app on Shopify supports these features:
• 3-D Secure
• Apple Pay
• Card payments
• Google Pay
• Fraud Management tools
Cybersource supports these transaction types on Shopify:
• Authorization (authorize only)
• Sale (auth and capture)
• Capture (capture only)
• Payer Authentication (3-D Secure)

Cybersource Built by Us 112

Built by Us

• Refund (credit)
• Void (reversal)

Conguring Security Credentials

You must have a Cybersource Business Center account. If you do not have one, you must
create one before installing the Cybersource app on Shopify. You also need to retrieve
details from that account to install the plugin.

Creating a Business Center Account

Follow these steps to congure your Business Center account:
1. Go to the Business Center Registration website, and create an account.
2. Follow the email instructions that you received to activate your merchant account.
3. Log in to the Business Center to complete the registration process.

Installing the Cybersource App on Shopify

You must enable the Cybersource app in your Shopify account settings. Follow these
steps to install the Cybersource app on Shopify:
1. To nd the Cybersource app from the list in Shopify settings, go to Store Home >
Settings > Payments > See all other providers.
2. In the search box, enter Cybersource.
3. Select the app and click Install.
4. A page opens on Shopify. Provide the required permissions to the payment app.
5. After you set the permissions, the Business Center log in opens.
6. Log in to the Business Center with your Cybersource credentials. An agreement page
opens.
7. Check or clear the 3-D Secure enrollment box based on your business needs. If you
choose to enroll for 3-D Secure, ensure that the Payer Authentication feature is
enabled and congured.
8. Submit the form. The Shopify store settings page re-opens so that you can congure
and activate the Cybersource app.

Conguring Shopify
Congure the Shopify payment settings. Follow these steps to congure the Cybersource
App in your Shopify store:
1. Log in to your Shopify account.
2. Go to your Cybersource store, and go to Settings > Payments > Manage.
3. Select the card brands and payment methods that you want to accept.
4. Click Save.

Cybersource Built by Us 113

Built by Us

Using 3-D Secure

If you are going to use 3-D Secure, you must have Payer Authentication
enabled and have your Cardinal keys stored within the Business Center. To
enable Payer Authentication, contact Cybersource support or your account
manager. Request that the Payer Authentication enablement include support
for the direct integration method.
After Payer Authentication is enabled, follow these steps to verify your Payer
Authentication credentials:
1. Log in to your Business Center account.
2. Go to Payment Conguration > Payer Authentication Conguration.
3. View the Org Unit ID, API Identier, and API Key to use in Shopify to verify your
credentials.
Because you veried the Payer Authentication credentials and enabled the 3-D Secure
feature when you installed the Cybersource app, the transactions will support 3-D Secure
ows.

Reference Information
This section contains reference information to help you use the Cybersource app on Shopify.

Testing
You can test your integration before you start accepting payments. To test the application
before moving to the production environment, you must request a dedicated the test app
from Cybersource. Send to [email protected] and provide your Shopify domain and store
name.
Follow these steps to verify that the app is enabled and congured properly:
1. In your Shopify account, and go to your web store.
2. Add an item to the cart and proceed to checkout.
3. Enter the shipping information.
4. Enter the test card information.
5. Click Pay Now.
6. Log in to your Business Center account.
7. Review the test transaction.
8. If there is a problem with the transaction or it does not appear in the Business Center,
contact Cybersource support.

Troubleshooting
Contact Cybersource to troubleshoot transactions and request support. Include this
information when you contact Cybersource:
• Cybersource merchant ID
• Shopify store name
• Shopify payment ID
• Shopify reason string and code

Cybersource Built by Us 114

Built by Us

• Date and time

• Test or production environment
• Steps to recreate the error

Cybersource Built by Us 115

Built by Our Partners

Built by Our Partners

Explore solutions built by our industry-leading partners that offer real-time fraud
screening, account takeover protection, and comprehensive payment solutions. Our
partners provide potential use cases such as personalizing shopping experiences
through advanced analytic. Offer your customers a seamless omnichannel experience and
improve site performance for higher customer satisfaction. Benet from the centralized
management of product information, automated order processing and fulllment, and
real-time data synchronization between SAP Commerce Cloud and existing ERP systems.
Moreover, our partners' solutions offer scalable infrastructure, exible integration
capabilities, advanced reporting tools, and enhanced visibility into supply chain and
inventory management.
This is built by our partner:
BigCommerce

BigCommerce
BigCommerce provides a software-as-a-service (SaaS) payment platform where you can
manage your online business. BigCommerce provides customizable functionality ready
for you to build and integrate with Cybersource. This section describes the payment
methods and services that the platform provides. These payment features and methods
are supported:
• Card Payments
• Apple Pay
• Google Pay
• 3-D Secure
• Token Management Service
• Decision Manager and Fraud Management Essentials
• OAuth for connecting your BigCommerce account with Cybersource

Cybersource Built by Our Partners 116

Built by Our Partners

Release Information
This section provides information about the releases for BigCommerce.
Version 2 includes the following features:
• Global availability in more than 190 countries
• Transaction currency support in all available countries
• 3-D Secure 2.0
• Support for the these card brands:
• American Express
• Diners Club
• Discover
• JCB
• Maestro
• Mastercard
• Visa
• Stored Credit Cards
• Apple Pay
• Google Pay
• Decision Manager and Fraud Management Essentials
For more information, see New Features Available in Cybersource.

Requirements and Prerequisites

Before installing and conguring the Cybersource Extension ensure that you meet these
requirements:
• Have a BigCommerce merchant account.
• Have Optimize One Page Checkout. For more information, see Optimize One Page
Checkout.
• Have a Business Center account. To create an account, go to the Business Center
Registration website.
• Can accept payments in one of the supported currencies.
• Have cardinal credentials saved within your Business Center account for 3-D Secure
transactions.

Supported Features
This section describes payment, services, and features provided by BigCommerce through
Cybersource.
These are the supported payment methods:
• Credit and debit card payments
• Card types:
• American Express

Cybersource Built by Our Partners 117

Built by Our Partners

• Diners Club
• Discover
• JCB
• Maestro
• Mastercard
• Visa
• Apple Pay
• Google Pay
These are the supported services:
• Authorization only
• Authorization and capture
• Captures
• Partial Refunds
• Refunds
These are the supported features:
• 3-D Secure
• Token Management Service (TMS): Removes your customer's stored card information
from your environment and exchanges sensitive payment data for tokens that cannot
be reversed. Contact Cybersource customer support to request that TMS be enabled
to use the Stored credit cards feature on your Cybersource merchant account.
• Fraud Management Essentials: Decision Manager
• OAuth is an industry-standard authorization protocol that enables you to use your
Business Center account credentials to connect to BigCommerce for transaction
processing.

Conguring BigCommerce
This section describes how to set up your BigCommerce account to Cybersource. Before
you begin, make sure that you have a Business Center account.
Create an Evaluation Account
If you do not have an Business Center account, go to the Business Center Registration
website to create one.
To complete the registration process, follow the email instructions that you received to
activate your merchant account, and log in to the Business Center.

Enabling the Extension

Follow these steps to enable the Cybersource extension.
1. Navigate to Store Setup › Payments.
2. From the list of Online Payment Methods, choose Cybersource.

Cybersource Built by Our Partners 118

Built by Our Partners

3. From the Cybersource Settings tab, click Sign up to create an account.

Connecting to Cybersource
Follow these steps to connect BigCommerce on the Cybersource Settings
page.
1. From Cybersource Settings page, choose the environment you want to connect to
your BigCommerce account, and choose Connect with. You will be redirected to the
Cybersource login page.

2. Enter your credentials and click Allow to give BigCommerce permission to connect to
your account. If you used OAuth to log in, your account will automatically connect to
Cybersource with the appropriate permissions.
Conguration Settings

This section describes the conguration settings for the Cybersource

Extension.
In the Cybersource Settings page, congure your preferences based on the services you
will be using.
1. Display Name: Control how the payment gateway appears at checkout. Cybersource
recommends something like Credit/Debit.

Cybersource Built by Our Partners 119

Built by Our Partners

2. Merchant ID: Enter the merchant ID (such as 87654321) that you received when you
signed up with Cybersource.

3. Transaction Type: Choose Authorize and Capture or Authorize Only. Authorize Only
allows you to capture the funds manually. See Manually Capturing Transactions
(Authorize Only) to learn more.

4. Test Mode: Determines whether your store is in Test Mode. Set to No (Recommended)
when you are ready to take payments.

5. Require CVV (credit card security codes): This option requires users to enter the CVV/
CVV2/CVD code for their credit card during checkout. Enabling this option adds extra
security on credit card transactions.

6. Enable 3-D Secure: This option enables an additional security layer that helps to
prevent unauthorized transactions. See 3-D Secure for more information about this
feature.

Cybersource Built by Our Partners 120

Built by Our Partners

7. Enable Google Pay: This option allows shoppers to pay using Google Pay on your
storefront. See Connecting with Google Pay for more information.

8. Set up Apple Pay: You can allow shoppers to pay using Apple Pay on your storefront. To
congure this feature, see Connecting with Apple Pay for more information.
9. Show the Card Element: This option allows you to display or hide the credit card eld at
checkout. See Show Card Element for more information on this feature.

10.Click Save.

Upgrade
If you already have an account, you can upgrade to V2 from the Cybersource Settings
page. For more details, see Upgrading from Cybersource to Cybersource V2.

Cybersource Built by Our Partners 121

Becoming a Partner

Becoming a Partner

As a partner of Visa, you have access to a range of solutions that can help you grow
your business and offer your customers more ways to pay. You can leverage Visa's global
network, innovative products, and trusted brand to enhance your value proposition and
drive revenue.
Visa Acceptance Solutions are designed to meet the diverse needs of different types of
partners and their end customers. You can choose from a variety of options depending on
your business model, target market, and integration preferences. Some of the benets of
partnering with Visa include:
• Access to the world's largest payment network, reaching over 200 countries and
territories.
• Ability to offer your customers multiple payment methods, including contactless,
mobile, online, and in-app payments.
• Opportunity to leverage Visa's expertise, resources, and tools to support your business
growth and innovation.
• Exposure to Visa's extensive network of merchants, acquirers, issuers, and other
partners.
The Visa Acceptance Solutions portfolio is categorized by the brands you can work with.
Each brand represents a different way of integrating with Visa and delivering payment
solutions to your customers. The three main brands are:
• Visa Acceptance Platform
• Cybersource
• Authorize.Net

Cybersource Becoming a Partner 122

Becoming a Partner

Key Information
The Visa Acceptance Partnership program encompasses multiple partner offerings, all of
whom have an important role in allowing customers to transact in a simple and efcient
manner. The following section introduces you to the main partner structures and their key
features.
Enablement Partners
Integrate your offerings into our platform and build innovative, custom payment solutions
for your merchants. For guidance on what this entails and how to apply, see below:
Enablement | Visa Acceptance Solutions
Reseller Partners
Sell our solutions directly to your merchants with the option to deliver them under your
brand. For guidance on what this entails and how to apply, see below:
Reseller | Visa Acceptance Solutions
Referral Partners
The lowest level of commitment and an easy way to diversify your revenue streams:
Just refer merchants to Visa Acceptance Solutions so they can build great payments
experiences. For guidance on what this entails and how to apply, see below:
Referral | Visa Acceptance Solutions
Authorize.Net Partners
Complement your own merchant account offering with our Authorize.Net payment
gateway. We deliver a competitive buy rate, and you set the pricing for your customers. We
then offer residuals on the difference in the buy and sell rate monthly.
Become a partner | Authorize.net

Tech Partner Requirements

To join the Visa Acceptance partnership ecosystem, the following steps are required
before development can commence.

Create a Sandbox Account

First you will need to create a sandbox account.

Cybersource Becoming a Partner 123

Becoming a Partner

Obtain a Partner Solution ID

A Partner Solution ID is a short code that is supplied in a transaction request. This code
allows Visa to identify a transaction as being supplied via your software. A mandatory
requirement for any partner, the Partner Solution ID will allow for improved reporting,
servicing, and troubleshooting. You must be assigned a unique Partner Solution ID specic
to your integration with the platform.
To initiate this process, the above Sandbox Account sign up process will trigger an alert to
our teams to generate and supply you with this ID, soon after account creation.
Visa Acceptance Platform and Cybersource use Partner Solution ID to track technology
partner transaction volume by linking merchant transactions to your solution. The below
provides instructions for integrating and validating your assigned Partner Solution ID.
1. Include your Partner Solution ID with every API call made by your integration in both
Test and Production.
2. Self-validate that your Partner Solution ID has been properly sent.
Sample: clientReferenceInformation.partner.solutionId attribute

{
"clientReferenceInformation" : {
"code" " : "clientCode",
"partner" : {
"solutionId" : "888888888"
}
}
}

Example: Sending a Partner Solution ID

Request with a Partner Solution ID

{
"clientReferenceInformation": {
"code": "TC50171_3",
"partner": {
"solutionId": "88888888"
}
},
"paymentInformation": {
"card": {
"number": "4111111111111111",
"expirationMonth": "12",
"expirationYear": "2031"
}
},
"orderInformation": {
"amountDetails": {
"totalAmount": "102.21",
"currency": "USD"
},
"billTo": {
"rstName": "John",

Cybersource Becoming a Partner 124

Becoming a Partner

"lastName": "Doe",
"address1": "1 Market St",
"locality": "san francisco",
"administrativeArea": "CA",
"postalCode": "94105",
"country": "US",
"email": "[email protected]",
"phoneNumber": "4158880000"
}
}
}

How to Validate the Account in the Business Center

To ensure the Partner Solution ID is being passed correctly, you can validate the receipt of
this information within the EBC, when viewing a transaction:
1. Log into the test Business center.
2. Navigate to the Transaction Details Search page.
3. Search for transactions with your Partner Solution ID.
If your search nds your assigned Partner Solution ID, then your account is valid. If the
search does not nd your Partner Solution ID (shows value 9999), then your account is not
valid.
The Transaction Details Page

Cybersource Becoming a Partner 125

Becoming a Partner

Develop Your Integration

This is a high-level overview of the available integration models and offer supporting
resources such as SDKs and developer forums.

Getting Started
If you have not already done so, begin by following the steps on the Tech Partner
Requirements page.
Tech Partner Requirements
After the sandbox account creation process, you will receive a link to log in to the
Enterprise Business Center.
From the Enterprise Business Center, you can create any API keys your integration may
need for testing.
There are other authentication mechanisms available, such as Oauth. If you believe your
integration may benet from this, refer to the relevant documentation.
OAuth Developer Document

Best Practices
As best practice, you are strongly encouraged to utilise our REST APIs and where possible,
use integration mechanisms designed to safely capture sensitive payment data using
our hosted payments elds. To ensure safety of cardholder data and to reduce PCI
requirements for your customers, you are encouraged to make use of the Microform,
Unied Checkout, and/or Tokenization approaches.
Secure Integration Methods
Legacy APIs, such as Simple Order API, are supported though these APIs may not have the
full feature set.
Note that many regions mandate the use of 3D Secure to facilitate Strong Customer
Authentication. The inclusion of Payer Authentication should be strongly considered to
ensure your software is available in such regions.
There are a multitude of products and services that you may wish to include in your
integration. Consider the needs of your customers when deciding what functionality to
utilise.
If you are unsure of what features you might include, do not hesitate to Get In Contact
with customer support.

SDKs and Github

REST API SDKs (cybersource.com)

Developer Center and API Libraries

The links below provide an overall introductory summary of Card Not Present (e.g.
Ecommerce) and Card Present (In-Person) integrations.
Accept Payments Online
In-Person Accept

Cybersource Becoming a Partner 126

Becoming a Partner

You should review our wider API Reference for further information on additional
transaction types and APIs available.
API Reference

Developer Center Forum

To ask a question, or otherwise engage with the developer community, please visit the
below reference hub:
Cybersource Developer Community

Partner Blog and Newsletter

Click here to subscribe to Subscription Management Center | Visa Acceptance.

The Partner Directory

The Partner Directory serves as a public platform for you to showcase your solutions as a
Visa Acceptance Platform-integrated partner. This platform is designed to highlight your
offerings, enabling you to stand out and demonstrate how your solutions integrate with
the Visa Acceptance Platform. This is an excellent opportunity to increase your visibility to
merchants and acquirers looking for technology partners to realize new projects.
The Partner Directory is a public-facing platform. Its primary function is to facilitate
connections between Acceptance Solutions ISV and technology partners and VPC-
connected acquirers.
After you have a fully developed integration, you can list your offering on the Partner
Directory (Coming Soon).

Prerequisites
Before submitting information for your partner listing, ensure you should complete the
following prerequisites:
• You have an active agreement with Visa Acceptance Solutions or Cybersource.
• You have agreed to be listed under Visa Acceptance Solutions branding (signed our
legal addendum).
• You have registered for the Visa Acceptance Partner portal.
• You have designated two Directory editors from your team who are responsible for
creating and editing your listing information.

Sign-Up Steps
• Enter into a partnership agreement (see Becoming a Partner).
• Complete the integration with Visa Acceptance Platform.
• Submit Transactions in Production with your assigned Partner Solution ID (PSID).
• Return Signed Trademark Consent Agreement.
• Register for Account on Acceptance Solutions Partner Portal.

Cybersource Becoming a Partner 127

Becoming a Partner

• Populate Directory Prole on Acceptance Solutions Partner Portal.

Populating the Directory Prole

The content on this page is yours to manage. However, before publishing, this content is
subject to approval by Visa Acceptance. You are encouraged to follow a rough framework
and best practices, as outlined on the Sample Partner Page.
Creating and updating your listing on the Visa Acceptance Solutions Partner Directory is
a seamless process that can be completed entirely in our Partner portal. You’ll be able to
add, remove, and update information about your company and product within the portal’s
UX.
1. Update your company prole: We encourage all partners to review their “Company
Prole” under their user prole to ensure that all information and logos are up-to-date.
This ensures that the correct data is applied to your listing. Within this short form, we
encourage you to:
• Add your company’s logo.
• Indicate which Visa Acceptance Solutions products your offering is compatible with.
• Indicate which countries your offering is available in.
• Indicate which industries your offering serves.
Update Your Company Logo

2. Input the Information for your listing: Once you log into the partner portal, navigate to
the “Marketplace Prole” tab to add information for your partner listing. See the table
below for guidance on adding content into each block.

Cybersource Becoming a Partner 128

Becoming a Partner

Add Information to Your Listing

Directory Prole Information

Information Required Response Guidance (All information can be edited under Relevant Link
your Marketplace Profile tab)

Headline A short headline of your business.

Company Description 2-3 sentences summarizing your company and product
offering.
Value proposition (open 2-3 sentences summarizing the value of your company (optional)
text) and offering.
Graphics (.jpeg) Image s Include any images you’d like to display on your (optional)
hould be at least 575px listing (.jpeg, or .png files).
Video (.mp4) (Optional) Include a video you would li (optional)
ke to display on your listing (link or
.mp4 files).
Product Overview (open Include available version number. (optional)
text)
Include your system requirements. (optional)
Include your product compatibility. (optional)
Integration Information Step 1: Create a sandbox (2-3 sentences): Create a None needed
(open text) sandbox account - The first step to set up y
our integration is registering for a san
dbox account. From this account, you
can create your security certificates and test your
implementation.

Cybersource Becoming a Partner 129

Becoming a Partner

Information Required Response Guidance (All information can be edited under Relevant Link
your Marketplace Profile tab)

Step 2: Create your credentials (2-3 None needed

sentences)Create your credentials - Create REST
Keys to connect Visa Acceptance Solutions t
o your (company) accounts. Click the l
ink above for detailed instructions.
Step 3: Configure the Plug-in (2-3 s Input the link
entences) Step 3: Configure the Plug-in - Click So
the link above to access the Cybersource offeri
ng within the (insert your company’s p
age name). Upon completion of the ch
eckout, you will be granted access keys by (your company
) to download them into your Adobe C
ommerce instance,
(optional) Secondary step to configure your instance None needed
(2-3 sentences).
Resources (open text) Submit any relevant links to content that you would (optional)
like to share. These links may include docu
mentation, listing information, GitHu
b sites, etc.
Downloadable Assets (.p Submit any relevant files you would like to share. (optional)
df files) These files will be available for download on y
our listing.
3. Send your listing to the Visa Acceptance Solutions team: After completing the rst two
steps, click the Request Review button to send a draft of your listing for review to the
Visa Acceptance Solutions team.
Request a Review of Your Company Prole

You have successfully submitted a listing to our Visa Acceptance Solutions team for
review. After review, our team will either approve and publish your listing to our Partner
Directory or request changes.

Cybersource Becoming a Partner 130

Becoming a Partner

If changes are required, you can repeat the process described above to access your
Marketplace prole, make changes, and request another review. You will receive an
email notication when the status of your listing changes.
Contact your Account Executive if you have any questions or concerns.

Frequently Asked Questions

How do I sign up for the partner portal? You can sign up at this link:
cybersource.partner-experience.com/
login. You will receive a portal approval and
login credentials will be emailed within 2-5
business days.
What does the partner portal contain? The Visa Acceptance Solutions partner
portal is a self-service resource to help
partners to be successful in maximizing
mutual partnership value. The portal will
enable you to access helpful product and
thought leadership content, take training
on our products, register referral leads
(only for referral partners), view our event
calendar, and (now) edit your Directory
listing.
How many users can we have in the partner As many as you see t! However, we do
portal? ask that you designate only two users as
Directory Editors.
What if I have future edits to my listing? If you’d like to make changes to your
partner listing, you may follow the same
process. You can log back into the partner
portal, make edits to your Prole page, and
request a review by our Visa team.

Contact Information
Contact your Visa partner representative for details or register your interest at one of
these pages:
• Enablement Partners Enablement | Visa Acceptance Solutions
• Reseller Partners Reseller | Visa Acceptance Solutions
• Referral Partners Partner with us to support your merchants | Visa Acceptance
Solutions
• Authorize.Net Become a partner | Authorize.net

Cybersource Becoming a Partner 131