Skip to content
Search Articles/

less than a minute read • Updated 2 hours ago

ePayments

Connect Foxy to ePayments for secure payments.

Features
  • Multi-Currency

The company behind this gateway has shut down entirely. ePayments connects Foxy to ePayments.com (ePayments Systems Ltd), a UK-regulated electronic money institution. The UK Financial Conduct Authority suspended its operations in 2019/2020 over anti-money-laundering compliance concerns, and in September 2022 the company announced it was permanently closing the business. Its website today shows only a closure notice telling former customers to withdraw any remaining funds — there is no indication it is processing payments for anyone, merchant or consumer.

This is not a "closed to new signups" situation, which is common enough among legacy gateways — it's a defunct vendor. You cannot sign up for ePayments today, and if you are somehow still nominally connected to it in Foxy, there is very likely no live service on the other end to process a transaction. This article exists to document the integration for historical/troubleshooting reference, not as setup instructions for anyone to follow today. If you have a payment method set using this gateway, treat migrating off it as urgent, not routine maintenance.

Setting up ePayments (historical reference only)

These are the steps the Foxy wiki documented while ePayments.com was operating. We are not recommending anyone follow them — start here only if you're trying to understand or unwind an existing connection.

  1. 1

    An ePayments.com merchant account would have been required, created directly with ePayments.

  2. 2

    In the ePayments account, a CallbackUrl setting pointed at your Foxy store's IPN endpoint: https://YOUR-STORE.foxycart.com/ipn.php, substituting your store's own domain (or your custom store subdomain's /ipn.php, if you used one).

  3. 3

    In the Foxy administration at https://admin.foxy.io, under Settings > Payments, a payment method set would have an ePayments entry added via Add payment method +.

  4. 4

    The panel's three fields are Shop ID and Secret Key (there is no third credential field for this gateway — the pack records no label for it).

  5. 5

    Click Create.

Testing

Foxy's records show shared test credentials exist for ePayments (foxy_supplies_test_credentials: true in the underlying configuration), so the Test setup fields in the Foxy panel are still pre-filled. Given that the vendor no longer operates, we would not expect a test transaction against this gateway to complete meaningfully — there's no live ePayments sandbox left to answer. Don't spend time debugging a failed test transaction here; it's not something a credentials fix will solve.

Obtaining a test account

Not possible. ePayments.com no longer operates a business of any kind, sandbox or otherwise.

Test card numbers

The wiki records the following test cards from when the integration was live. They're included for historical reference only — we have no way to verify them against a live sandbox, because none exists:

  • Approved — Card number: 4314220000000049 — Expiry: 01/22 — CVC: 589

  • Bank declined — Card number: 5142905574265797 — Expiry: 01/20 — CVC: 221

  • Transfer provider declined — Card number: 2200774546102058 — Expiry: 04/21 — CVC: 986

The wiki notes none of these test cards exercised 3D Secure.

Advanced features

None. The pack records no additional fields for this gateway beyond Shop ID and Secret Key, and no card verification, auth-only, or 3D Secure support (supports_auth_only: false, supports_3d_secure: false, supports_card_verification: false).

Important notes and caveats

  • The vendor is gone, not just legacy. Unlike an old brand that merged into a bigger one (as with Vantiv or Ogone), ePayments.com ceased operating as a company. There is no successor product to point merchants toward.

  • Foxy still lists this gateway as active (is_deprecated: false in the underlying configuration), and it still appears selectable in the admin. That's a mismatch worth fixing at the product level — a merchant who stumbles onto "ePayments" in the payment method picker today has no way to know, from Foxy's admin alone, that the company behind it doesn't exist anymore.

  • No subscription support, per the wiki. We could not independently verify this against the API pack, which records no subscription-support flag for any gateway type — treat it as a wiki claim, not pack-confirmed.

  • Countries the wiki lists (28 EU nations plus GB) describe ePayments.com's former market, not a currently operating service.

Troubleshooting

There is no vendor support channel to escalate to — ePayments Systems Ltd does not operate customer or merchant support anymore. If you're seeing failures on this gateway, that's almost certainly why. The only real fix is migrating your payment method set to a currently operating gateway.

Need Help?

Did this article answer your questions? Need help with anything? Please click below to contact us.