Metaverse Trading Ltd
UK-incorporated · Non-custodial · Audit-ready

We write the rails. Money stays yours.

We build non-custodial, white-label infrastructure for businesses that want to accept and move stablecoins, without us ever holding their funds or keys. Two products carry the work: Sardium, a live crypto checkout, and OB Wallet, a self-custody wallet.

Two rails · the money stays with its owner
moneyour software
Sardium For businesses · white-label crypto checkout ● Live
  1. 01
    Customer pays

    By card or a local method in the merchant's own checkout. A licensed provider handles the payment and KYC.

    100.00 USD
    fiat + KYC
  2. 02
    Customer's own wallet

    The stablecoin lands in the customer's self-custody wallet, and the customer signs the payment.

    100 USDC
    USDC / USDT
  3. 03
    Merchant wallet

    The merchant receives it in its own wallet and holds the keys.

    +100 USDC
    signed
OB Wallet For people · self-custody wallet ● Live on Google Play
  1. 01
    Keys on the phone

    Generated on the device and never leave it. There is no copy on our servers.

    0 keys
    on our servers
  2. 02
    Buy by card

    Through licensed payment providers, under their own licences. The crypto is sent to the user's address.

    100 USDT
    fiat + KYC
  3. 03
    Your own wallet

    Held, sent and spent by the user, who signs every move. EVM, Bitcoin, Tron, Solana, TON.

    +100 USDT
    self-custody
Metaverse Trading Ltdwe write the software for both rails
software only · no funds pass through us
Never in the money path
Entity
Metaverse Trading Ltd, United Kingdom
Custody
NoneWe hold no fiat, no crypto
Settlement
USDC & USDT, four EVM chains
Source
Shared with merchants and auditors
Products

Two products, one rule.

In both products we never hold customer funds or private keys. Regulated services (card payments, identity verification and currency conversion) are provided by licensed payment providers under their own licences. That single constraint decided the architecture of both products.

SardiumWhite-label crypto checkout

Your customer pays by card. The stablecoin reaches their wallet, then yours.

A licensed provider handles the fiat leg and the KYC and delivers the stablecoin to the customer's own self-custody wallet; the customer then signs and sends the payment to your wallet. No exchange account, no middleman holding the money, and no moment where the funds sit with us.

● LiveSource on requestPolygon · Base · Arbitrum · Optimism
Read more about Sardium
OB WalletSelf-custody wallet

A wallet where the keys are generated on the phone and never leave it.

Hold stablecoins, buy with a card through licensed payment providers and pay shops straight from the wallet. The Rust signing core will be published open source. Live on Google Play in 20 countries; an iPhone version is coming to the App Store, and an NFC card follows.

● LiveRust core, auditableGoogle Play · 20 countries
Read more about OB Wallet

New merchants

Sardium is live and used by businesses. We work closely with every new merchant through integration. If stablecoin payments are on your roadmap, an early conversation costs you nothing.

Custom infrastructure

Need a non-custodial flow that does not fit either shelf product? We take a handful of custom engagements per year. Reach out with the shape of the problem rather than a spec.

What the merchant receives

Not the money. A signed message that it arrived.

  • 1
    Orchestration, never custodyWe coordinate the provider, the customer's wallet and your wallet. The funds move between them, not through us.
  • 2
    Signed webhook, HMAC-SHA256Every delivery carries a signature, a timestamp and an event id, so your server can verify it and ignore replays.
  • 3
    Verifiable on the chainThe payment itself is a transaction to your own wallet. You do not have to trust our message; you can check it.
POST /webhooks/sardiumorder.completed
// headers
X-Sardium-Event-Type: order.completed
X-Sardium-Event-Id: evt_…
X-Sardium-Timestamp: 1760601600
X-Sardium-Signature: ••••••••••••••••••••••••

// body
{
  "eventId": "evt_…",
  "order": {
    "amount": "100.00", "asset": "USDC", "chain": "polygon",
    "recipient": "0xYOUR_WALLET",
    "txHash": "0x…"
  },
  "testMode": false
}
How we think

Five design choices we do not trade away.

These are how we make sure we never hold customer funds or private keys. Regulated services are provided by licensed payment providers under their own licences.

  1. 01

    The server never holds private keys.

    Production code is grep-gated in CI. Any function that could create or sign a transaction on a user's behalf is blocked from merging.

  2. 02

    Every fund movement is user-signed.

    No automatic sweeps, no batch crons, no session keys. The user clicks a button or nothing happens.

  3. 03

    We do not custody fiat or crypto.

    Fiat lives with the licensed payment provider. Crypto lives in the user's own wallet. Master wallets belong to the merchant, not to us.

  4. 04

    Every change is auditable.

    Append-only audit log, OFAC SDN screening before broadcast, configurable AML thresholds. Two-party approval for anything that affects fund flow.

  5. 05

    Users can always export their key.

    Wherever we touch user wallets, the user can export their private key at any time. Sovereignty is technical, not promised.

Plainly

Three things we are not.

Most fintech websites list what they are. For a business doing due diligence on us, what we are not is the more useful list.

01

Not a bank.

We hold no deposits and open no accounts. Nobody's balance lives with us.

02

Not a payment institution.

Card payments are processed by licensed providers. We never take possession of fiat.

03

Not a custodian.

Only the user controls their wallet and holds its keys; our servers never hold private keys. We could not move the funds if we tried.

Compliance & security

Built to survive due diligence.

We expect every merchant, licensed payment provider and bank we deal with to run business verification (KYB) on us. Here is what they find.

Legal entity

Metaverse Trading Ltd, registered in England and Wales, company no. 16644748.

Custody posture

None. We do not hold fiat or cryptocurrency on behalf of users or merchants.

Sanctions screening

OFAC SDN list refreshed daily. Pre-broadcast checks on user and destination addresses.

AML monitoring

Per-user 24-hour and 7-day threshold logging. Merchants receive alerts; suspicious activity is escalated to our MLRO, who reports to the UK National Crime Agency where the law requires.

Data privacy

GDPR Art. 15 and 17 and KVKK Art. 11 endpoints in our API. Only what a payment needs: the sign-in email and public wallet address, the payer's name and email as verified by the payment provider, and the IP address of the last device that opened the payment link.

Cryptography

AES-256-GCM at rest with KMS envelope, HMAC-SHA256 for webhooks, scrypt for API keys.

Vulnerability reporting

Coordinated disclosure. Write to us and we respond within one working day.

Source code

Source, runbooks and threat model are shared with merchants and auditors on request.

The full compliance page →

The names

Both named after the birth of money.

Sardis · about 600 BC

Sardium

The world's first coin was struck in Sardis, in Anatolia, from electrum: value you could verify by holding it. Sardium moves value the same way, from the customer's own wallet to yours, verifiable on the chain.

Obolos · 8th century BC

Obolium

Before coins, money was an iron spit you held in your hand: the obol. Six made a drachma, a handful. Obolium keeps to that definition. Your keys, on your device, in your hand.

Get in touch

Tell us what you're building.

Merchant integrations, partnerships, security reports, or plain curiosity: we reply to every serious enquiry within one working day.

kyb@metaversetradingltduk.com