At a glance
Supported payment methods
Ecommpay uses Primer’s standard card form and Primer’s native Apple Pay and Google Pay integrations, so no Ecommpay-specific SDK code is required.
Supported capabilities
3D Secure
Primer performs 3D Secure authentication using the Perform 3DS action and passes the result to Ecommpay. Ecommpay does not run its own 3D Secure for payments processed through Primer.Get started with Ecommpay
Before you begin
If this is your first connection, make sure to follow the Get started guide to begin processing payments with Primer. You need an Ecommpay account with a test project for sandbox and a production project for live payments. Contact Ecommpay to get your test project credentials.Only users with the Merchant Admin role and two-factor authentication (2FA) enabled can view a project’s Secret Key in the Ecommpay Dashboard. Please ensure that someone with these permissions is available to retrieve the Secret Key during the integration setup.
Credentials
In your Ecommpay Dashboard, go to Management > Projects, open your project and stay on the General tab.Configure in the Dashboard
1
Add Ecommpay to your Dashboard
Go to Integrations, select New integration, search for Ecommpay and enter your Project ID and Secret Key.
2
Add a callback in Ecommpay
In your Ecommpay Dashboard, go to Projects, open Callbacks and select Add new. Enter the callback URL shown in the Primer Dashboard and save. Primer uses this callback to receive payment updates from Ecommpay.
3
Activate the payment methods on the Checkout
Go to Checkout and activate Card, Apple Pay and Google Pay.
4
Route payments with Workflows
In Workflows, select Ecommpay in the Authorize payment action for the payment methods you want to route to it. Add the Perform 3DS action before authorization for card payments.
Prepare the client session
In addition to the parameters required by each payment method, Ecommpay requires the following:Considerations
- CVV required. Ecommpay requires a CVV for card payments, including payments with saved cards. Merchant-initiated transactions do not need a CVV when the initial payment included one.
- 3D Secure required. Ecommpay requires 3D Secure for GBP and EUR card payments. Payments routed to Ecommpay without a 3D Secure result may be declined.
- Asynchronous processing. Ecommpay completes some transactions asynchronously. Use the PAYMENT.STATUS webhook to get the final status of a payment.
Test in sandbox
Connect your Ecommpay project to your Primer Sandbox environment. In the Ecommpay sandbox, the result depends on the amount, the currency and the card you use.- Card
- Apple Pay
- Google Pay
- Merchant-initiated
Test a 3DS challenge. Use EUR or GBP with one of these cards, and enter the OTP when the challenge appears.
Test without a 3DS challenge. Use a currency such as AUD or USD. The payment is authorized without a challenge.Test a saved card. Include the CVV when you pay with a saved card.
Go live
Before switching to production, confirm that:- Your Ecommpay production project is active for Card, Apple Pay and Google Pay.
- You have added Ecommpay in your Primer production environment using your production Project ID and Secret Key.
- You have added a callback to your production Ecommpay project using the callback URL from your Primer production Dashboard.
- Your 3D Secure configuration is ready for production. See 3D Secure.
- You have tested Google Pay on the web in production.
- You handle the payment.status webhook and fulfil orders only on a final status.