{"title":"Cybersource","slug":"cybersource-payment-provider","url":"https://support.storeconnect.com/articles/cybersource-payment-provider","url_markdown":"https://support.storeconnect.com/articles/cybersource-payment-provider.md","subtitle":null,"summary":"Configure Cybersource as a payment provider in StoreConnect, including standard checkout, accepted card networks, Google Pay, Apple Pay, and express checkout.","type":"Help_Documentation","video_url":"","keywords":"cybersource, payment provider, payment gateway, apple pay, google pay, express checkout, digital wallets, pre-authorization, merchant account, api options, sandbox configuration, checkout payments, card networks, discover, jcb, allowed card networks","last_modified":"2026-08-21T07:12:35+0000","body_markdown":"Cybersource is a payment provider that integrates directly with StoreConnect. You can use Cybersource for:\n\n- Standard checkout payments (Visa, Mastercard, American Express, and other networks supported by your account)\n- Additional and Salesforce payments\n- Pre-authorization\n- Google Pay and Apple Pay wallets\n- Express checkout\n\n\u003e Already have your credentials? Go to [Configure Cybersource in StoreConnect](#configure-cybersource-in-storeconnect).\n\n## What you need\n\n- [Cybersource merchant account](https://www.cybersource.com/en-us/why-cybersource/merchant-payment-processing.html)\n- Cybersource Merchant ID, API Key ID, and Secret Key\n- For Google Pay: a Google Merchant ID from the Google Pay \u0026 Wallet Console\n- For Apple Pay: an Apple Developer account and OpenSSL installed on your computer\n\n## Get your Cybersource credentials\n\n### Merchant ID\n\nYour 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.\n\n### API Key ID and Secret Key\n\n1. In Cybersource, go to **Payment Configuration \u003e Key Management**.\n2. Click **Generate Key**.\n3. Copy the **Key ID** — this is your API Key in StoreConnect.\n4. Copy the **Key Secret** — this is only displayed once at generation time. Store it securely before closing the page.\n\n## Configure Cybersource in StoreConnect\n\n1. Open StoreConnect and go to **Setup \u003e Payments \u003e Payment Providers**.\n2. Select **New**. Complete the fields as follows, then **Save**:\n\n| StoreConnect field | Cybersource value                          |\n|--------------------|--------------------------------------------|\n| Name               | Cybersource. For testing, add - Sandbox.  |\n| Provider           | Select Cybersource from the list          |\n| API Mode           | sandbox or production                     |\n| API Key            | Your Key ID                               |\n| API Secret         | Your Key Secret                           |\n| API Options        | `merchant_id: 'yourmerchantidinlowercase'` |\n\n## Enable other payment features in the API Options field\n\nThe **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. \n\n:::note\nThe API Options field uses YAML format. Each option goes on its own line.\n:::\n\n## Configure accepted card networks\n\nBy default, Cybersource's card input form accepts Visa, Mastercard, and American Express. If your Cybersource account supports additional card types — such as Discover or JCB — you can configure which networks are accepted using the `allowed_card_networks` option.\n\nAdd the following to the **API Options** field, listing only the networks your processor supports:\n\n```yaml\n\nallowed_card_networks:\n  - VISA\n  - MASTERCARD\n  - AMEX\n  - DISCOVER\n  - JCB\n```\n\n:::note\nNetwork names must be uppercase. If `allowed_card_networks` is not set or is left empty, StoreConnect defaults to Visa, Mastercard, and American Express.\n:::\n\n## Enable Google Pay and Apple Pay\n\nCybersource supports Google Pay and Apple Pay through its Digital Payment Solutions integration.\n\n### Enable wallets in Cybersource\n\nBefore configuring wallets in StoreConnect, you need to enable them in the Cybersource Business Center.\n\n1. In Cybersource, go to **Payment Configuration \u003e Digital Payment Solutions**.\n2. Ensure both **Android Pay** and **Apple Pay** are enabled.\n\n:::note\nAndroid Pay is Google Pay under its original name — they are the same thing in Cybersource. Ignore Samsung Pay — it is not supported by StoreConnect.\n:::\n\nIf either option is missing from your dashboard, contact your Cybersource support representative to have it enabled on your account.\n\n### Enable wallets in StoreConnect\n\nOnce wallet types are enabled in Cybersource, add the following to the **API Options** field on the Payment Provider record in StoreConnect:\n\n```yaml\n\nshow_wallets: true\nexpress_checkout_enabled: true\n```\n\nThen continue with the setup below for each wallet.\n\n### Google Pay setup\n\n**Step 1: Get a Google Merchant ID**\n\n1. Go to the [Google Pay \u0026 Wallet Console](https://pay.google.com/business/console) and create a merchant account if you don't already have one.\n2. Note your **Merchant ID** at the top of the console — it looks like `BCR2DN4T7XDOFC2K`.\n\n**Step 2: Get your Android Pay credentials from Cybersource**\n\n1. In Cybersource, go to **Payment Configuration \u003e Digital Payment Solutions**.\n2. Click **Configure** next to Android Pay.\n3. Click **Generate public key** and download the file.\n4. Note the **Android Pay ID** and **Android Public Key** values shown on the page.\n\n**Step 3: Add Google Pay options in StoreConnect**\n\nIn the Payment Provider record in StoreConnect, add the following to the **API Options** field:\n\n```yaml\n\nmerchant_country_code: AU\ngoogle_merchant_name: 'Your Store Name'\ngoogle_merchant_id: 'BCR2DN4T7XDOFC2K'\nandroid_pay_id: 'yourandroidpayid'\nandroid_public_key: 'yourbase64encodedpublickey'\n```\n\nReplace `AU` with the two-letter country code for your store if it is not based in Australia.\n\n### Apple Pay setup\n\nSetting up Apple Pay with Cybersource involves three parts:\n\n1. [Set up the Apple Pay Payment Processing Certificate](#part-1-set-up-the-apple-pay-payment-processing-certificate)\n2. [Create a Merchant Identity Certificate](#part-2-create-a-merchant-identity-certificate)\n3. [Register your store domain](#part-3-register-your-store-domain)\n\nBefore starting, find your Apple Merchant Identifier at the top of the **Certificates, Identifiers \u0026 Profiles** page in your Apple Developer account, then add it to the **API Options** field in StoreConnect:\n\n```yaml\n\napple_merchant_id: merchant.storeconnect.cybersource\n```\n\n#### Part 1: Set up the Apple Pay Payment Processing Certificate\n\nThis certificate links Apple Pay to Cybersource. For this step, Cybersource generates the Certificate Signing Request (CSR) — you do not need to generate it yourself.\n\n**In Cybersource:**\n\n1. Go to **Payment Configuration \u003e Digital Payment Solutions**.\n2. Click **Configure** next to Apple Pay.\n3. Enter your Apple Merchant ID (for example, `merchant.com.yourdomain.applepay`).\n4. Click **Generate new certificate signing request** and download the `.csr` file.\n\n**In Apple Developer:**\n\n5. Go to your merchant identifier and under **Apple Pay Payment Processing Certificate**, click **Create Certificate**.\n6. Upload the `.csr` file you downloaded from Cybersource, then click **Continue**.\n7. Click **Download** to receive the certificate file.\n\n:::note\nThis step only involves exchanging certificates between Cybersource and Apple. No changes to API Options in StoreConnect are required.\n:::\n\n#### Part 2: Create a Merchant Identity Certificate\n\nThe Merchant Identity Certificate establishes the relationship between the Payment Provider and Apple Pay, using certificates. You need OpenSSL installed to complete these steps.\n\n1. On your computer, open a terminal and run the following to generate a private key and Certificate Signing Request (CSR):\n\n   ```bash\n\n   openssl genrsa -out apple_pay_merchant.key 2048\n   openssl req -new -key apple_pay_merchant.key -out apple_pay_merchant.csr\n   ```\n\n2. In Apple Developer, go to your merchant identifier and under **Apple Pay Merchant Identity Certificate**, click **Create Certificate**.\n3. Upload `apple_pay_merchant.csr` and click **Continue**.\n4. Click **Download** to receive `merchant_id.cer`.\n5. Convert the certificate to PEM format:\n\n   ```bash\n\n   openssl x509 -inform DER -in merchant_id.cer -out merchant_id.pem\n   ```\n\n6. 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.\n\n   ```yaml\n\n   apple_pay_private_key: |-\n     -----BEGIN PRIVATE KEY-----\n     (paste contents of apple_pay_merchant.key here)\n     -----END PRIVATE KEY-----\n   apple_pay_certificate: |-\n     -----BEGIN CERTIFICATE-----\n     (paste contents of merchant_id.pem here)\n     -----END CERTIFICATE-----\n   ```\n\n:::warning\nWhen 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.\n:::\n\n#### Part 3: Register your store domain\n\nApple requires your store domain to be registered and verified before Apple Pay will work in a browser.\n\n1. In Apple Developer, go to your merchant identifier and scroll to **Merchant Domains**.\n2. Click **Add Domain**, enter your store's hostname (for example, `store.yourdomain.com`), then click **Save**.\n3. Click **Download** to receive `apple-developer-merchantid-domain-association.txt`.\n4. Add the file contents to the **API Options** field in StoreConnect:\n\n   ```yaml\n\n   applepay_verification: |-\n     (paste the contents of apple-developer-merchantid-domain-association.txt here)\n   ```\n\n5. Back in Apple Developer, click **OK** next to the domain to trigger Apple's verification check.\n\n:::note\nApple 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.\n\nOnce verification is complete, you can remove the `applepay_verification` key from API Options — it is only needed during initial domain registration.\n:::\n\nWhen setup is complete, the Apple Pay button appears on product pages and at checkout in Safari.\n\n## Sandbox and production configuration reference\n\nOnce all features are set up, use the reference below to see how sandbox and production configurations differ in StoreConnect.\n\n| StoreConnect field | Sandbox | Production |\n|--------------------|---------|------------|\n| API Mode | sandbox | production |\n| API Key | Sandbox Key ID | Production Key ID |\n| API Secret | Sandbox Key Secret | Production Key Secret |\n| API Options: `merchant_id` | Sandbox Merchant ID | Production Merchant ID |\n| API Options: `android_pay_id` | Sandbox Android Pay ID | Production Android Pay ID |\n| API Options: `android_public_key` | Sandbox Android Public Key | Production Android Public Key |\n\nAll other API Options values — including `allowed_card_networks` — are the same for both environments.\n\n**Sandbox — complete API Options:**\n\n```yaml\n\nmerchant_id: 'yoursandboxmerchantid'\nshow_wallets: true\nexpress_checkout_enabled: true\nmerchant_country_code: AU\ngoogle_merchant_name: 'Your Store Name'\ngoogle_merchant_id: 'YOUR_GOOGLE_MERCHANT_ID'\nandroid_pay_id: 'yoursandboxandroidpayid'\nandroid_public_key: 'yoursandboxbase64encodedpublickey'\napple_merchant_id: merchant.storeconnect.cybersource\napple_pay_private_key: |-\n  -----BEGIN PRIVATE KEY-----\n  (contents of apple_pay_merchant.key)\n  -----END PRIVATE KEY-----\napple_pay_certificate: |-\n  -----BEGIN CERTIFICATE-----\n  (contents of merchant_id.pem)\n  -----END CERTIFICATE-----\n```\n\n**Production — complete API Options:**\n\n```yaml\n\nmerchant_id: 'yourproductionmerchantid'\nshow_wallets: true\nexpress_checkout_enabled: true\nmerchant_country_code: AU\ngoogle_merchant_name: 'Your Store Name'\ngoogle_merchant_id: 'YOUR_GOOGLE_MERCHANT_ID'\nandroid_pay_id: 'yourproductionandroidpayid'\nandroid_public_key: 'yourproductionbase64encodedpublickey'\napple_merchant_id: merchant.storeconnect.cybersource\napple_pay_private_key: |-\n  -----BEGIN PRIVATE KEY-----\n  (contents of apple_pay_merchant.key)\n  -----END PRIVATE KEY-----\napple_pay_certificate: |-\n  -----BEGIN CERTIFICATE-----\n  (contents of merchant_id.pem)\n  -----END CERTIFICATE-----\n```\n\n:::note\nOnly 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.\n:::"}