emerchantpay

Card payments with 3D Secure v2. The shopper enters the card on the Mozarto hosted page. Your platform never handles card data.

Display name: Debit/Credit Card
Operations: Pay-In
Saved cards: Yes, when the user token carries a userId

Configuration (Mozarto back office)

These fields are in the locked API Credentials section of the account's Processing Scope tab. Unlock it with your 2FA code first - see Unlock API credentials.

Configure the emerchantpay account in Payments Module as described on the Redirect API emerchantpay page, and also set:

Field	Description
`apiKey` *	Required for the method to appear on the hosted page. Without it the method is not offered

Then enable Debit/Credit Card on the brand's Payment Page for each country.

Shopper data

Data	Source
Billing first and last name	`firstName` and `lastName` claims in the user token. Required - emerchantpay rejects payments without them
Email	`email` claim in the user token
Billing address	Collected on the page: `street`, `city`, `postalCode`, and `state` for US, CA, and AU

3D Secure

The issuer's challenge runs inside the hosted page and returns to it. Your returnUrls are not used for 3D Secure. A failed challenge ends with finalStatus: "Card verification failed".

Configuration (Mozarto back office)#

Shopper data#

3D Secure#

Configuration (Mozarto back office)

Shopper data

3D Secure