Cybersource

Cybersource is a payment provider that integrates directly with StoreConnect. You can use Cybersource for:

• Standard checkout payments (Visa, Mastercard, American Express)
• Additional and Salesforce payments
• Pre-authorization
• Google Pay and Apple Pay wallets
• Express checkout

Already have your credentials? Go to Configure Cybersource in StoreConnect.

What you need

• Cybersource merchant account
• Cybersource Merchant ID, API Key ID, and Secret Key
• For Google Pay: a Google Merchant ID from the Google Pay & Wallet Console
• For Apple Pay: an Apple Developer account and OpenSSL installed on your computer

Get your Cybersource credentials

Merchant ID

Your Merchant ID appears at the top of every page in the Cybersource Business Center. You will need it for the API Options field in StoreConnect.

API Key ID and Secret Key

1. In Cybersource, go to Payment Configuration > Key Management.
2. Click Generate Key.
3. Copy the Key ID — this is your API Key in StoreConnect.
4. Copy the Key Secret — this is only displayed once at generation time. Store it securely before closing the page.

Configure Cybersource in StoreConnect

1. Open StoreConnect and go to Setup > Payments > Payment Providers.
2. Select New. Complete the fields as follows, then Save:

StoreConnect field	Cybersource value
Name	Cybersource. For testing, add - Sandbox.
Provider	Select Cybersource from the list
API Mode	sandbox or production
API Key	Your Key ID
API Secret	Your Key Secret
API Options	merchant_id: 'yourmerchantidinlowercase'

Enable other payment features in the API Options field

The API Options field in the payment provider record is where you enable payment features such as 3DS, Apple Pay, Google Wallet, etc. The following sections step you through setting these up and then adding them to StoreConnect.

:::note The API Options field uses YAML format. Each option goes on its own line. :::

Enable Google Pay and Apple Pay

Cybersource supports Google Pay and Apple Pay through its Digital Payment Solutions integration.

Enable wallets in Cybersource

Before configuring wallets in StoreConnect, you need to enable them in the Cybersource Business Center.

1. In Cybersource, go to Payment Configuration > Digital Payment Solutions.
2. Ensure both Android Pay and Apple Pay are enabled.

:::note Android Pay is Google Pay under its original name — they are the same thing in Cybersource. Ignore Samsung Pay — it is not supported by StoreConnect. :::

If either option is missing from your dashboard, contact your Cybersource support representative to have it enabled on your account.

Enable wallets in StoreConnect

Once wallet types are enabled in Cybersource, add the following to the API Options field on the Payment Provider record in StoreConnect:

yaml show_wallets: true express_checkout_enabled: true

Then continue with the setup below for each wallet.

Google Pay setup

Step 1: Get a Google Merchant ID

1. Go to the Google Pay & Wallet Console and create a merchant account if you don’t already have one.
2. Note your Merchant ID at the top of the console — it looks like BCR2DN4T7XDOFC2K.

Step 2: Get your Android Pay credentials from Cybersource

1. In Cybersource, go to Payment Configuration > Digital Payment Solutions.
2. Click Configure next to Android Pay.
3. Click Generate public key and download the file.
4. Note the Android Pay ID and Android Public Key values shown on the page.

Step 3: Add Google Pay options in StoreConnect

In the Payment Provider record in StoreConnect, add the following to the API Options field:

yaml merchant_country_code: AU google_merchant_name: 'Your Store Name' google_merchant_id: 'BCR2DN4T7XDOFC2K' android_pay_id: 'yourandroidpayid' android_public_key: 'yourbase64encodedpublickey'

Replace AU with the two-letter country code for your store if it is not based in Australia.

Apple Pay setup

Setting up Apple Pay with Cybersource involves three parts:

1. Set up the Apple Pay Payment Processing Certificate
2. Create a Merchant Identity Certificate
3. Register your store domain

Before starting, find your Apple Merchant Identifier at the top of the Certificates, Identifiers & Profiles page in your Apple Developer account, then add it to the API Options field in StoreConnect:

yaml apple_merchant_id: merchant.storeconnect.cybersource

Part 1: Set up the Apple Pay Payment Processing Certificate

This certificate links Apple Pay to Cybersource. For this step, Cybersource generates the Certificate Signing Request (CSR) — you do not need to generate it yourself.

In Cybersource:

1. Go to Payment Configuration > Digital Payment Solutions.
2. Click Configure next to Apple Pay.
3. Enter your Apple Merchant ID (for example, merchant.com.yourdomain.applepay).
4. Click Generate new certificate signing request and download the .csr file.

In Apple Developer:

1. Go to your merchant identifier and under Apple Pay Payment Processing Certificate, click Create Certificate.
2. Upload the .csr file you downloaded from Cybersource, then click Continue.
3. Click Download to receive the certificate file.

:::note This step only involves exchanging certificates between Cybersource and Apple. No changes to API Options in StoreConnect are required. :::

Part 2: Create a Merchant Identity Certificate

The Merchant Identity Certificate establishes the relationship between the Payment Provider and Apple Pay, using certificates. You need OpenSSL installed to complete these steps.

1. On your computer, open a terminal and run the following to generate a private key and Certificate Signing Request (CSR):

   bash openssl genrsa -out apple_pay_merchant.key 2048 openssl req -new -key apple_pay_merchant.key -out apple_pay_merchant.csr

2. In Apple Developer, go to your merchant identifier and under Apple Pay Merchant Identity Certificate, click Create Certificate.
3. Upload apple_pay_merchant.csr and click Continue.
4. Click Download to receive merchant_id.cer.

5. Convert the certificate to PEM format:

   bash openssl x509 -inform DER -in merchant_id.cer -out merchant_id.pem

6. Add the contents of both files to the API Options field in StoreConnect. Make sure the apple_pay_merchant.key has a two-space indent.

   yaml apple_pay_private_key: |- -----BEGIN PRIVATE KEY----- (paste contents of apple_pay_merchant.key here) -----END PRIVATE KEY----- apple_pay_certificate: |- -----BEGIN CERTIFICATE----- (paste contents of merchant_id.pem here) -----END CERTIFICATE-----

:::warning When pasting multi-line certificate content into the API Options field, every line of the certificate must be indented consistently beneath the key name. Prepare the YAML in a text editor before pasting. :::

Part 3: Register your store domain

Apple requires your store domain to be registered and verified before Apple Pay will work in a browser.

1. In Apple Developer, go to your merchant identifier and scroll to Merchant Domains.
2. Click Add Domain, enter your store’s hostname (for example, store.yourdomain.com), then click Save.
3. Click Download to receive apple-developer-merchantid-domain-association.txt.

4. Add the file contents to the API Options field in StoreConnect:

   yaml applepay_verification: |- (paste the contents of apple-developer-merchantid-domain-association.txt here)

5. Back in Apple Developer, click OK next to the domain to trigger Apple’s verification check.

:::note Apple verifies your domain by requesting the verification file from https://yourstorename.com/.well-known/apple-developer-merchantid-domain-association.txt. StoreConnect serves this file automatically once it is saved in API Options.

Once verification is complete, you can remove the applepay_verification key from API Options — it is only needed during initial domain registration. :::

When setup is complete, the Apple Pay button appears on product pages and at checkout in Safari.

Sandbox and production configuration reference

Once all features are set up, use the reference below to see how sandbox and production configurations differ in StoreConnect.

StoreConnect field	Sandbox	Production
API Mode	sandbox	production
API Key	Sandbox Key ID	Production Key ID
API Secret	Sandbox Key Secret	Production Key Secret
API Options: merchant_id	Sandbox Merchant ID	Production Merchant ID
API Options: android_pay_id	Sandbox Android Pay ID	Production Android Pay ID
API Options: android_public_key	Sandbox Android Public Key	Production Android Public Key

All other API Options values are the same for both environments.

Sandbox — complete API Options:

yaml merchant_id: 'yoursandboxmerchantid' show_wallets: true express_checkout_enabled: true merchant_country_code: AU google_merchant_name: 'Your Store Name' google_merchant_id: 'YOUR_GOOGLE_MERCHANT_ID' android_pay_id: 'yoursandboxandroidpayid' android_public_key: 'yoursandboxbase64encodedpublickey' apple_merchant_id: merchant.storeconnect.cybersource apple_pay_private_key: |- -----BEGIN PRIVATE KEY----- (contents of apple_pay_merchant.key) -----END PRIVATE KEY----- apple_pay_certificate: |- -----BEGIN CERTIFICATE----- (contents of merchant_id.pem) -----END CERTIFICATE-----

Production — complete API Options:

yaml merchant_id: 'yourproductionmerchantid' show_wallets: true express_checkout_enabled: true merchant_country_code: AU google_merchant_name: 'Your Store Name' google_merchant_id: 'YOUR_GOOGLE_MERCHANT_ID' android_pay_id: 'yourproductionandroidpayid' android_public_key: 'yourproductionbase64encodedpublickey' apple_merchant_id: merchant.storeconnect.cybersource apple_pay_private_key: |- -----BEGIN PRIVATE KEY----- (contents of apple_pay_merchant.key) -----END PRIVATE KEY----- apple_pay_certificate: |- -----BEGIN CERTIFICATE----- (contents of merchant_id.pem) -----END CERTIFICATE-----

:::note Only include the options for features you have set up. For example, if you are not using Apple Pay, omit the apple_merchant_id, apple_pay_private_key, and apple_pay_certificate keys. :::