PROVIDER - In Administration · Discontinued

ePayments

ePayments (ePayment Systems Ltd) is discontinued: the domain now points to an Opus Restructuring & Insolvency notice stating the company entered Special Administration on 15 October 2026, with joint administrators handling enquiries.

Payment Platform United Kingdom 2026.11.19
1pts

Detailed Notes

Pros 4 items

Formerly a UK e-wallet and payments service for freelancers and cross-border sellers
The domain now redirects to an Opus special administration notice
The notice records entry into Special Administration on 2026-10-15
This entry is kept for brand identification and internal links

Cons 3 items

The company is in administration and no longer provides services
Account funds and follow-up must go through the joint administrators
No usable product, fee or support channel remains

Service Overview

Verified 2026-11: the entry's website_url https://opusllp.com/restructuring-insolvency/epayments-in-special-administration/ returned 200 with the title Case: ePayment Systems Ltd (in Special Administration) | Opus Restructuring & Insolvency and states the company entered Special Administration on 15 October 2026. Ranking forced to 1.0 under the discontinued rule.

Status: discontinued. ePayments entered special administration; epayments.com no longer serves normal operations and official updates are published by the appointed administrators at Opus. The following is historical information.

ePayments was an account-based payment platform provider: the payment account itself was the product, not merely a collection channel. Funds landed in an account balance first and then left through transfers, withdrawals or a prepaid card. Its historical products included multi-currency accounts and prepaid cards, and it was popular with freelancers, outsourcing teams and small cross-border recipients. In normal conditions the convenience is high, but the risk profile is fundamentally different from that of a gateway.

When a gateway fails, the symptom is a failed transaction and a switch to another provider. When an account-based provider fails, the symptom is restricted account functions and balances you cannot move, which affects money already received rather than the next transaction. Historically this model has seen account functions restricted, which shows that account availability is the core risk surface of an account-based provider, not technical integration.

This page is therefore not an onboarding recommendation. It sets out how to judge an account-based provider and how to manage funds: how long to hold money, how much, and what to do first when restriction signals appear.

Key Strengths

This section covers the product value of the account model and the judgement rules distilled from it, not an endorsement of a discontinued service.

  • Convenience of multi-currency accounts: One account collecting several currencies with fewer conversion steps genuinely reduces operating cost for individuals and small teams handling frequent small cross-border settlements.
  • Account and prepaid card in one: Balances can be spent or withdrawn directly, shortening the path from collection to usable funds, which is the main draw of the account model over a gateway.
  • Rule 1: is safeguarding verifiable? An account-based provider should explain whether client funds are held separately from its own money, which institution safeguards them, and how often reconciliation occurs.
  • Rule 2: account availability outranks fees: Judge whether the provider might restrict account functions under compliance review before judging its pricing. An account that saves fees but can become unusable at any time carries the highest real cost.
  • Rule 3: cap how long balances stay: Turn the question of how long operating funds sit in a third-party account into policy, for example withdrawal thresholds and cycles, so large balances do not accumulate.

Product Ecosystem

Multi-currency accounts and prepaid cards

The core of the account model is one account holding balances in several currencies, paired with a card for spending and withdrawals. The convenience comes from linking account and card, and so does the risk: once the account is restricted, balance and card fail together.

Where account-based providers hold funds

Three things must be clear: which type of account client funds sit in, whether they are separated from the company's own money, and who performs reconciliation. The safeguarding arrangement usually determines whether client funds can be ring-fenced when the provider runs into trouble. See payment account freeze response guide for the mechanics.

The three triggers of account-availability risk

First, compliance and identity reviews; second, contagion from counterparty risk; third, the provider's own financial and licensing status. These triggers typically appear first as slower withdrawals and tighter reviews, then escalate into restricted functions, so watch the early signals rather than waiting for a shutdown.

Criteria for choosing a replacement

Score candidates on 4 items: coverage of target markets and currencies, onboarding and identity review thresholds, withdrawal rails and arrival times, and how verifiable the platform's compliance is. Do not mistake "able to open an account" for "able to use it long term". See multi-currency payment account guide for cross-region comparisons.

Limitations

  • Account-availability risk: Restricted functions hit balance, withdrawals and card at once, a wider blast radius than a gateway.
  • Fund retention risk: Leaving operating funds in a third-party account hands your working capital to an outside institution, so cash flow suffers the moment access is restricted.
  • Identity review friction: The account model demands thorough identity and source-of-funds checks, and incomplete documents or unclear business descriptions easily trigger extra review.
  • Long cross-border settlement chains: Multi-currency accounts involve several clearing and conversion layers, and a problem in any layer delays arrival.
  • Limited transparency: Account terms, fund structures and risk disclosures are expensive to interpret, and small users rarely complete substantive review before opening an account.
  • Single-account dependency: Collecting and paying through one account-based provider puts both directions in one place with no backup path.

Use Cases

  • Account-based provider selection framework (★★★★★): Turn the three rules into a pre-onboarding checklist for evaluating any account-based provider.
  • Historical research and risk case study (★★★★☆): A typical sample of account-availability risk, useful for internal fund-safety training.
  • Backup account strategy design (★★★★☆): Pair primary and backup accounts with withdrawal thresholds for multi-currency collection to soften a single-point restriction.
  • Fund retention policy design (★★★★☆): Write balance caps and withdrawal cycles as enforceable rules rather than relying on someone remembering to withdraw.
  • Mainland China entity onboarding (★☆☆☆☆): Not applicable. Account-based cross-border services impose heavy entity and identity review, making direct onboarding for mainland China entities unlikely, and this page describes no onboarding path.
  • Least suitable: keeping operating funds in a third-party account long term: Whichever account-based provider you pick, parking payroll, goods payments and taxes in an account balance for months is high risk.

Pricing

Account-based pricing differs from gateway pricing: you pay a combination of account, deposit, withdrawal, conversion and card fees rather than a single transaction rate. Exact amounts are negotiated per contract and the current quote on the official site prevails.

Item Billing basis Notes
Account opening and maintenance Monthly or free Per contract; some tiers carry a monthly fee
Inbound transfer fee Per item or percentage Depends on source channel and currency
Withdrawal fee Per item plus percentage Depends on destination bank and currency
Currency conversion Spread on the rate Conversion cost usually sits inside the exchange rate
Prepaid card fees Per card or per item Issuance, top-up and spending may each be charged
Dormancy and inactivity fee Per account Subject to the current terms

Cost judgement points: The most underestimated cost in the account model is not the fee but fund float and availability risk. Add average balance days multiplied by your cost of capital to the comparison, then layer on conversion spread and withdrawal fees. If one account's fees are clearly below peers, check whether the gap comes from slower arrival, tighter withdrawal conditions or a worse exchange rate.

FAQ

  • How does an account-based provider differ from a gateway? A gateway only routes transactions to the acquirer, while an account-based provider also holds your balance. A gateway failure affects the next transaction; an account failure freezes money you already received.
  • How do I judge the risk of an account-based provider? Check three things: whether client funds are safeguarded, whether licensing and regulatory status are verifiable, and whether account functions have ever been restricted. If all three are unclear, lower your retention cap.
  • How much balance should I keep? A cap covering one to two weeks of normal spending is safer, with the excess withdrawn to a bank account on a cycle, and the threshold written into policy.
  • What should I do first when an account is restricted? Confirm whether the restriction covers collection, withdrawal or everything, preserve statements and transaction evidence, and activate a backup account to keep collecting so the business does not stop.
  • How should a mainland China entity handle multi-currency collection? Go through licensed institutions and compliant channels, verifying licensing, safeguarding and settlement paths, and avoid depending on a single overseas account-based provider.

Code Examples

Migration prep: normalise historical settlement records

# Service shut down (special administration): historical statement migration only
import csv

# Normalise exported statements into shared fields for the new provider
FIELDS = ["txn_id", "created_at", "currency", "amount", "fee", "status"]

def normalise(src: str, dst: str) -> int:
    rows = 0
    with open(src, newline="") as fin, open(dst, "w", newline="") as fout:
        reader = csv.DictReader(fin)
        writer = csv.DictWriter(fout, fieldnames=FIELDS)
        writer.writeheader()
        for r in reader:
            writer.writerow({
                "txn_id": r["Transaction ID"].strip(),
                "created_at": r["Date"].strip(),
                "currency": r["Currency"].strip().upper(),
                "amount": f'{float(r["Amount"]):.2f}',
                "fee": f'{float(r["Fee"]):.2f}',
                "status": r["Status"].strip().lower(),
            })
            rows += 1
    return rows

Scripts like this only process your own statement files locally with no network calls; dry-run on a sample and reconcile the totals before a full run.

Migration check: compare totals before and after

import csv
from collections import defaultdict
from decimal import Decimal

def totals(path: str, key: str = "currency") -> dict[str, Decimal]:
    out = defaultdict(Decimal)
    with open(path, newline="") as f:
        for row in csv.DictReader(f):
            out[row[key]] += Decimal(row["amount"]) - Decimal(row["fee"])
    return dict(out)

def reconcile(old_file: str, new_file: str) -> list[str]:
    old, new = totals(old_file), totals(new_file)
    problems = []
    for cur in sorted(set(old) | set(new)):
        if old.get(cur, Decimal(0)) != new.get(cur, Decimal(0)):
            problems.append(
                f"{cur}: old={old.get(cur, 0)} new={new.get(cur, 0)}")
    return problems

if __name__ == "__main__":
    issues = reconcile("statement_old.csv", "statement_new.csv")
    print("\n".join(issues) or "totals match")

Reconcile net amounts per currency and clear every difference before the old account closes, otherwise it becomes untraceable later.

Community & Resources

Communities and official channels

Learning resources and tools

Visit ePayments Website → https://opusllp.com/restructuring-insolvency/epayments-in-special-administration
Visit Website ↗