{"title":"Eway","slug":"eway-payment-provider","url":"https://support.storeconnect.com/articles/eway-payment-provider","url_markdown":"https://support.storeconnect.com/articles/eway-payment-provider.md","subtitle":null,"summary":"Configure Eway as a payment provider in StoreConnect, including standard checkout, subscriptions, 3DS2, Google Pay, Apple Pay, and express checkout.","type":"Help_Documentation","video_url":"","keywords":"eway, payment provider, payment gateway, 3d secure, 3ds2, google pay, apple pay, express checkout, subscriptions, pre-authorization, wallet payments, payment configuration","last_modified":"2026-08-21T07:12:35+0000","body_markdown":"Eway is a payment provider that integrates directly with StoreConnect. You can use Eway for:\n\n- Standard checkout and subscription payments\n- Additional and Salesforce payments\n- Pre-authorization\n- 3D Secure 2.0 (3DS2)\n- Google Pay and Apple Pay wallets\n- Express checkout\n\n\u003e Already have your credentials? Go to [Configure Eway in StoreConnect](#configure-eway-in-storeconnect).\n\n## What you need\n\n- [Eway account](https://www.eway.com.au/online-payments/) (sandbox or production)\n- Eway API Key and Password\n- For 3DS2: 3D Secure 2.0 enabled in your Eway dashboard\n- For Google Pay: a Google Merchant ID obtained 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 Eway credentials\n\nTo generate your API credentials:\n\n- **Sandbox:** Follow [Creating an Eway Sandbox API key](https://eway.io/api-v3/#authentication) in the Eway API documentation.\n- **Production:** Log in to your Eway account and go to **My Account \u003e API Keys** to generate your API Key and Password.\n\n## Configure Eway 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 | Eway value                                    |\n|--------------------|-----------------------------------------------|\n| Name               | Eway. For testing, add - Sandbox.             |\n| Provider           | Select Eway from the list                     |\n| API Mode           | 'sandbox' or 'production' (must be lowercase)                         |\n| API Key            | Your Eway API Key                             |\n| API Secret         | Your Eway Password                            |\n| API Options        | `public_key: \"YOUR_CLIENT_SIDE_ENCRYPTION_KEY\"` |\n\nThe Client Side Encryption Key is used to encrypt card details in the browser before they reach the server. You can find this key in your Eway account under **My Account \u003e API Keys**.\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 in Eway 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## Enable 3DS2\n\nFrom v21, Eway supports 3D Secure 2.0 (3DS2), which adds an additional authentication step during checkout to reduce fraud.\n\n**Step 1: Enable 3DS2 in your Eway dashboard**\n\nIn your Eway dashboard, go to **Settings** and enable **3D Secure 2.0**.\n\n**Step 2: Add to API Options in StoreConnect**\n\nIn the Payment Provider record in StoreConnect, add the following to the **API Options** field:\n\n```yaml\n\nthree_d_secure: true\n```\n\n## Enable Google and Apple Pay\n\nFrom v21, Eway supports Google Wallet and Apple Pay on standard checkout, subscriptions, and express checkout.\n\nTo enable wallets, 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\nYou will also need to complete the setup below for each wallet and add the resulting keys to API Options.\n\n### Google setup\n\nStoreConnect uses the Direct Connection integration with Eway for Google Pay. Each store needs its own Google Merchant ID, obtained directly from Google.\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.\n2. Review and agree to Google's terms:\n   - [Acceptable use policy](https://payments.developers.google.com/terms/aup)\n   - [Google API Terms of Service](https://payments.developers.google.com/terms/sellertos)\n3. Note your **Merchant ID** — it looks something like `BCR1234567`.\n4. For production, follow Google's process to [request production access to Google Pay](https://developers.google.com/pay/api/web/guides/test-and-deploy/request-prod-access).\n\n**Step 2: Configure Google Pay in your Eway dashboard**\n\nIn your Eway dashboard, go to **Settings \u003e Google Pay Settings** and enter your Google Merchant ID.\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\n# For sandbox:\nmerchant_id: GPewaymerchantid\n# For production, replace with:\n# merchant_id: BCR2DN6T266KBHAD\n\n# Your Google Merchant ID from Step 1\ngoogle_merchant_id: 'BCR1234567'\n\n# Store name shown to customers at checkout\nmerchant_name: 'Your Store Name'\n```\n\n### Apple Pay setup\n\nSetting up Apple Pay with Eway involves three parts:\n\n1. [Activate Apple Pay and create a Payment Processing Certificate](#part-1-activate-apple-pay-and-create-a-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\n#### Part 1: Activate Apple Pay and create a Payment Processing Certificate\nThe Payment Processing Certificate establishes the relationship between eWAY gateway and Apple Pay.\n**In your Eway dashboard:**\n\n1. Go to **Settings \u003e Apple Pay**.\n2. Activate Apple Pay. The status changes from inactive to active once enabled.\n\n   \u003c!-- Screenshot: Eway Apple Pay settings before and after activation --\u003e\n\n3. Enter your admin email address and select **Generate CSR**.\n4. Click the blue public key link to download the `.csr` file.\n\n**In Apple Developer:**\n\n5. Go to [Certificates, Identifiers \u0026 Profiles](https://developer.apple.com/account/resources/identifiers/list/merchant) and create or select your Eway merchant identifier.\n6. Under **Payment Processing Certificate**, click **Create Certificate**.\n7. Under **Upload a Certificate Signing Request**, choose the `.csr` file you downloaded from Eway, then click **Continue**.\n8. Click **Download** to receive `apple_pay.cer`.\n\n**Back in your Eway dashboard:**\n\n9. Return to **Settings \u003e Apple Pay**.\n10. Click **Choose File**, select the `apple_pay.cer` file, then click **Upload**.\n\n**In StoreConnect, add your Apple Merchant ID to API Options:**\n\n11. In your Apple Developer account, note your Apple Merchant Identifier (it looks like `merchant.storeconnect.eway`).\n\n12. In the Payment Provider record in StoreConnect, add the following to the **API Options** field:\n\n    ```yaml\n\n    apple_merchant_id: merchant.storeconnect.eway\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.\n\nYou 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   ```\n2. In the Payment Provider record in StoreConnect, add the contents of the files to **API Options**. Make sure the `apple_pay_merchant.key` has a two-space indent.\n\n   ```yaml\n\n   apple_pay_private_key: |\n     -----BEGIN RSA PRIVATE KEY-----\n     (paste contents of apple_pay_merchant.key here)\n     -----END RSA PRIVATE KEY-----\n   ```\n\n3. In Apple Developer, select your merchant identifier and under **Merchant Identity Certificate**, click **Create Certificate**.\n4. Upload the `apple_pay_merchant.csr` file and click **Continue**.\n5. Click **Download** to receive `merchant_id.cer`.\n6. 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\n7. In the Payment Provider record in StoreConnect, add the contents of both files to **API Options**:\n\n   ```yaml\n\n   apple_pay_certificate: |\n     -----BEGIN CERTIFICATE-----\n     (paste contents of merchant_id.pem here)\n     -----END CERTIFICATE-----\n   ```\n\n:::tip\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 the domain verification file (`apple-developer-merchantid-domain-association.txt`).\n4. In the Payment Provider record in StoreConnect, add the file contents to **API Options**:\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. Note that the API Mode 'sandbox' or 'production' must be lowercase.\n\n| StoreConnect field | Sandbox | Production |\n|--------------------|---------|------------|\n| API Mode           | sandbox | production |\n| API Key            | Sandbox API Key | Production API Key |\n| API Secret         | Sandbox Password | Production Password |\n| API Options: `merchant_id` | `GPewaymerchantid` | `BCR2DN6T266KBHAD` |\n\nAll other API Options values are the same for both environments.\n\n**Sandbox — complete API Options:**\n\n```yaml\n\npublic_key: \"YOUR_CLIENT_SIDE_ENCRYPTION_KEY\"\nthree_d_secure: true\nshow_wallets: true\nexpress_checkout_enabled: true\nmerchant_id: GPewaymerchantid\ngoogle_merchant_id: 'YOUR_GOOGLE_MERCHANT_ID'\nmerchant_name: 'Your Store Name'\napple_merchant_id: merchant.storeconnect.eway\napple_pay_private_key: |\n  -----BEGIN RSA PRIVATE KEY-----\n  (contents of apple_pay_merchant.key)\n  -----END RSA 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\npublic_key: \"YOUR_CLIENT_SIDE_ENCRYPTION_KEY\"\nthree_d_secure: true\nshow_wallets: true\nexpress_checkout_enabled: true\nmerchant_id: BCR2DN6T266KBHAD\ngoogle_merchant_id: 'YOUR_GOOGLE_MERCHANT_ID'\nmerchant_name: 'Your Store Name'\napple_merchant_id: merchant.storeconnect.eway\napple_pay_private_key: |\n  -----BEGIN RSA PRIVATE KEY-----\n  (contents of apple_pay_merchant.key)\n  -----END RSA 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:::"}