Skip to content

Logo

EPX (North Enterprise)

Supports in this guide: Payments

Provider website: epx.com

Note

OFT lists this provider under the operating company name "North Enterprise"; the connection itself is branded "EPX", which is also this doc's epx slug.

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

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

Prerequisites: get from EPX

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

  • Customer Number -> Corefy field customer_number.
  • Merchant Number -> Corefy field merchant_number.
  • DBA Number -> Corefy field dba_number.
  • Terminal Number -> Corefy field terminal_number.
  • Acquirer BIN -> Corefy field acquirer_bin.
  • Acquirer Merchant ID -> Corefy field acquirer_merchant_id.
  • Acquirer Country Code (optional) -> Corefy field acquirer_country_code.
  • Acquirer Country Code Source (optional) -> Corefy field acquirer_country_code_source.

USD, CAD, EUR.

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Customer Number
  • Merchant Number
  • DBA Number
  • Terminal Number
  • Acquirer BIN
  • Acquirer Merchant ID
  • Acquirer Country Code (optional)
  • Acquirer Country Code Source (optional)

Success

You have connected EPX 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. EPX may return a 3D Secure challenge depending on the card - the payment is completed in two steps (an initial authentication step, then a completion step) handled automatically by Corefy.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "85af8385-d00e-4f58-ab1f-3a527fdf2d3b",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "96bf9496-e11f-4f69-bc2f-4b638ef8e3cc",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "customer-123",
        "address": {
          "full_address": "123 Main Street",
          "post_code": "10001"
        }
      }
    }
  }
}

Important

No Options or Constants are configured for this connector - customer.address fields are sent when present, otherwise simply not sent.

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

Refunds

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

Recurring

EPX supports saving and charging a card token through Corefy (standard tokenize/token-charge flow).

Additional info

  1. No reconciliation - EPX does not support an active status request (neither automatic nor manual); the final payment status is always returned synchronously as part of the two-step authentication/completion flow.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify Customer Number, Merchant Number, DBA Number, Terminal Number, Acquirer BIN and Acquirer Merchant ID
  • Currency or service is not supported -> confirm allowed currencies/features in your EPX account and in Corefy - only USD, CAD, EUR are available
  • Refund fails with multiple attempts -> only one refund per payment is allowed

Question

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