Skip to main content
Emerchantpay is a payment service provider and acquirer for online businesses. Connect Emerchantpay to Primer to process Card, Apple Pay and Google Pay payments, and route them using Workflows.

​
At a glance

​
Supported payment methods

Emerchantpay uses Primer’s standard card form and Primer’s native Apple Pay and Google Pay integrations, so no Emerchantpay-specific SDK code is required. Card networks: Visa and Mastercard.

​
Supported capabilities

​
3D Secure

Primer performs 3D Secure authentication.

​
Get started with Emerchantpay

​
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 Emerchantpay staging account for sandbox and a production account for live payments. Ask Emerchantpay to configure both accounts with the following settings:
  • Smart Routing enabled
  • 3rd-party MPI enabled, so Primer can perform 3D Secure
  • authorize and authorize3d transaction types enabled
  • Credential on file enabled, including merchant_unscheduled for merchant-initiated transactions
  • Scheme-tokenized transactions enabled, for Apple Pay and Google Pay
  • The currencies and card networks you plan to accept

​
Configure in the Dashboard

1

Add Emerchantpay to your Dashboard

Go to Integrations, select New integration, search for Emerchantpay and enter your Login and Password.
2

Activate the payment methods on the Checkout

Go to Checkout and activate Card, Apple Pay and Google Pay. Primer decrypts Apple Pay and Google Pay tokens, so you do not need to upload wallet certificates to Emerchantpay.
3

Route payments with Workflows

In Workflows, select Emerchantpay in the Authorize payment action for the payment methods you want to route to it.

​
Saved cards and merchant-initiated payments

Save the payment method on the first customer payment, then charge it later without the customer present. Primer links each merchant-initiated payment to the first payment automatically.
  1. First payment. In the client session, set paymentMethod.paymentType to FIRST_PAYMENT, set paymentMethod.firstPaymentReason to Recurring, Unscheduled or CardOnFile, and set paymentMethod.vaultOnSuccess to true.
  2. Merchant-initiated payment. Create a payment with the saved payment method token and set paymentMethod.paymentType to UNSCHEDULED or SUBSCRIPTION. A paymentType sent inside metadata is ignored.
By default, Emerchantpay requires the following fields on merchant-initiated payments:

​
Test in sandbox

Enter the below cards with a future expiry date. When the 3D Secure challenge appears, enter the OTP shown.

​
Go live

Before switching to production, confirm that:
  1. Emerchantpay has configured your production account with the same settings as your staging account. See Before you begin.
  2. You have added Emerchantpay in your Primer production environment using your production Login and Password.
  3. Your 3D Secure configuration is ready for production. See 3D Secure.
  4. Your merchant-initiated payments include customer.emailAddress and metadata.remote_ip.
  5. You handle the PAYMENT.STATUS webhook and fulfil orders only on a final status.