Skip to content

E-PRO

Welcome to EPRO!

Supports in this guide: Payments

Provider website: empcorp.com

What you need to do for start processing transactions (brief summary)

  1. Get your credentials (from E-PRO)
  2. Connect in Dashboard
  3. Send an API request

Prerequisites: get from E-PRO

Send a connection request at empcorp.com or contact your E-PRO account manager directly to get your account verified and receive the following credentials.

  • API key -> Corefy field api_key.

USD, EUR, PLN, NOK, JPY, BRL, AUD, NZD, VND, CAD, CLP, ARS, CHF.

Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open E-PRO in the provider directory and press Connect at E-PRO Provider Overview page in the New connection section.

Step 2 - Fill in fields and select settings

  • API key
  • Test Mode -> (enable if you are using sandbox credentials)
  • Currency / Features -> choose values available for your account

Success

You have connected E-PRO H2H Merchant account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice; card data itself is collected and submitted separately by Corefy's checkout/SDK layer, not as part of this request. E-PRO may return a 3D Secure challenge depending on the transaction.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "3fda3ea3-7353-4e43-b734-94818eb9a3ea",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Wick",
        "email": "johnwick@example.com",
        "date_of_birth": "1990-07-23",
        "address": {
          "country": "AO",
          "post_code": "123123"
        }
      }
    }
  }
}

Important

customer.name (first and last name), customer.email, customer.date_of_birth, customer.address.country, and customer.address.post_code are all required for this connector - the request fails immediately if any of them (or the matching Constant) is missing.

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "3c6ecb04-7623-43b7-88c9-99e656fbec7a",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_124",
        "name": "John Doe",
        "email": "test@example.com",
        "phone": "+380999999999",
        "date_of_birth": "1990-09-03",
        "address": {
          "full_address": "123 Main street",
          "country": "DE",
          "city": "Berlin",
          "post_code": "10115"
        }
      }
    }
  }
}

Important

customer.name, customer.address.full_address, and customer.address.city are transliterated to Latin before being sent to E-PRO.

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 -> the request fails, since these fields are required

Currently available constants (constant -> Corefy API field)

  • EMAIL -> customer.email
  • BIRTH_DATE -> customer.date_of_birth
  • COUNTRY -> customer.address.country
  • POST_CODE -> customer.address.post_code
  • FULL_ADDRESS -> customer.address.full_address
  • CITY -> customer.address.city

Refunds

E-PRO supports refunds for the full amount only (no partial or multiple refunds).

Additional info

  1. Active reconciliation is available - an active status request can be used to retrieve the current payment status.
  2. No recurring - this connector does not support saving/charging a token through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the API key for the selected environment (test_mode)
  • Payment rejected for missing customer details -> customer.name, customer.email, customer.date_of_birth, customer.address.country and customer.address.post_code (or their matching Constants) are all required
  • Currency or service is not supported -> confirm allowed currencies/features in your E-PRO account and in Corefy
  • Refund fails with multiple attempts -> only one, full-amount refund per payment is allowed

Question

Still looking for help connecting your E-PRO account? Please contact our support team!