Skip to content

Logo

EPayGlobal

Supports in this guide: Payments

Provider website: not reliably reachable at the time of writing (the two domains associated with this provider - eskaypay.com and epayglobal.com - currently resolve to an expired-domain parking page and an empty default WordPress install respectively; confirm the current website with your account manager before sharing it with anyone)

Note

This provider has also traded under the name Eskaypay - if you're looking for it under that name, it's the same connector (code epayglobal).

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

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

Prerequisites: get from EPayGlobal

Contact your EPayGlobal account manager to get your account verified and receive the following credentials.

  • Public Key -> Corefy field public_key.
  • Terminal Number -> Corefy field terminal_number.

Note

There is no Test Mode toggle and no API URL field for this connector - EPayGlobal exposes a single fixed endpoint, with no separate sandbox environment.

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Public Key
  • Terminal Number

Choose Currency / Features; check with your Corefy account manager which are enabled for your account.

Success

You have connected EPayGlobal 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. This connector does not support 3D Secure.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "FR",
          "region": "IDF",
          "city": "Paris",
          "full_address": "1 Main street",
          "post_code": "75000"
        }
      }
    }
  }
}

customer is entirely optional - everything you don't send falls back to the Constants below. The customer's name is not taken from customer.name for this connector - it's always sent as the name embossed on the card.

Important

This connector sends a hardcoded placeholder address/phone/email when the matching customer field is missing, and the exact placeholder depends on the payment's currency:

  • USD -> a US-based placeholder (Los Angeles, California)
  • CNY -> a China-based placeholder (Wuhan, Hubei)
  • any other currency -> a Singapore-based placeholder

In practice this means a sale can technically succeed even without real customer data, but the receiver may see implausible customer details for most currencies if you don't send your own - always send real customer data when you have it.

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

No Options are configured for this connector.

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. For this connector, the fallback used when both the request value and the constant are empty depends on currency - see the important note above.

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 currency-dependent placeholder described above is used

Currently available constants (constant -> Corefy API field)

  • EMAIL -> customer.email
  • PHONE -> customer.phone
  • COUNTRY -> customer.address.country
  • STATE -> customer.address.region
  • CITY -> customer.address.city
  • ZIP -> customer.address.post_code
  • FULL_ADDRESS -> customer.address.full_address

Refunds

EPayGlobal supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).

Additional info

  1. Callback routing is automatic - Corefy generates the callback/return URLs per transaction, nothing to configure in EPayGlobal's own back-office.
  2. No payouts - this connector does not support payouts through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify Public Key and Terminal Number
  • Card sale declined / implausible customer data on the provider's side -> send real customer data; otherwise a currency-dependent placeholder is used - see the important note under Payments above
  • Currency or service is not supported -> confirm allowed currencies/features in your EPayGlobal account and in Corefy
  • Looking for "ePay" instead? -> that's a different, separate connector (code epay) - make sure you're connecting the right one

Question

Still looking for help connecting your EPayGlobal account? Please contact our support team!