emerchantpay

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open emerchantpay in the provider directory and press Connect at emerchantpay Provider Overview page in the New connection section. Choose H2H Merchant account.

Step 2 - Fill in fields and select settings

• Username
• Password
• Terminal Token
• Recurring Terminal Token (optional, needed for recurring/instant payments)
• Non-3DS Terminal Token (optional, needed for the use_non3ds_fallback option below)
• Test Mode -> (enable if you are using sandbox credentials)

Choose Currency and Features. You can set these parameters according to available currencies and features for your emerchantpay account, but it is necessary to check details of the connection with your Corefy account manager.

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10.04,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "date_of_birth": "1990-05-14",
        "individual_tax_id": "123456789012",
        "address": {
          "country": "GB",
          "city": "London",
          "post_code": "SW1A 1AA",
          "full_address": "10 Downing Street"
        }
      }
    }
  }
}

emerchantpay's own terminal configuration requires customer_email, first/last name, and a full billing address by default. If you omit customer.email/customer.name/customer.address, Corefy sends the configured Constants instead (defaults: email travis@example.com, name John Doe, address 14, Nerazdelni str, city Salvador, country BR, zip 1407 - see Constants below) rather than leaving the request incomplete - send real customer data to avoid placeholder billing details reaching emerchantpay. Whether the sale is submitted as sale or sale3d (3-D Secure) is decided automatically per transaction (see Additional info). emerchantpay also supports USD, RUB, and JPY (use payment_card_<currency>_hpp as the service code, lowercase currency).

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow

Options

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (2)

• use_sca_checker - checks whether Strong Customer Authentication is actually required before deciding on 3-D Secure.
• use_non3ds_fallback - automatically retries a 3-D-Secure-declined sale without 3-D Secure.

Constants (fallback fields)

Constants are static values that Corefy can send to the provider instead of dynamic data from your API request, when those fields are missing in the request.

Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)

Currently available constants (constant -> Corefy API field)

• ADDRESS -> customer.address.full_address
• ZIP -> customer.address.post_code
• CITY -> customer.address.city
• COUNTRY -> customer.address.country
• EMAIL -> customer.email
• DEVICE_TYPE -> 3-D Secure v2 device type sent to emerchantpay (no per-request override - this is a fixed connection-level value)
• WINDOW_SIZE -> 3-D Secure v2 challenge window size sent to emerchantpay (no per-request override)
• CHALLENGE_INDICATOR -> 3-D Secure v2 challenge preference sent to emerchantpay (no per-request override)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

Open emerchantpay in the provider directory and press Connect at emerchantpay Provider Overview page in the New connection section. Choose Provider account.

Step 2 - Fill in fields and select settings

• Username
• Password
• Terminal Token
• API URL (optional, overrides the default gateway endpoint)
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "openbanking_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "DE",
          "city": "Berlin",
          "post_code": "10115",
          "full_address": "Unter den Linden 1"
        }
      }
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "openbanking_eur_hpp",
      "currency": "EUR",
      "amount": 10.04,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "DE",
          "region": "Berlin",
          "city": "Berlin",
          "post_code": "10115",
          "full_address": "Unter den Linden 1"
        }
      },
      "fields": {
        "bank_id": "TRL"
      }
    }
  }
}

Unlike the H2H Merchant account flow above, this Open Banking method has no placeholder fallback for customer data - emerchantpay requires a real customer.email, customer.phone, customer.name, and billing address by default for this method, so omitting them risks the payment being declined rather than a placeholder being substituted. fields.bank_id is optional: TRL is currently the only supported bank code for Open Banking (across all its supported countries), so it rarely needs to be set explicitly - see Constants below. This method currently supports EUR and GBP, across the UK, Ireland, Germany, France, Belgium, Finland, Spain, and Italy (use openbanking_gbp_hpp for GBP).

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow

Constants (fallback fields)

Constants are static values that Corefy can send to the provider instead of dynamic data from your API request, when those fields are missing in the request.

Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)

Currently available constants (constant -> Corefy API field)

• BANK_CODE -> fields.bank_id