Crypto payment infrastructure for brokers, prop firms, stores and PSPs

Crypto payments, with the back office built in.

DDXPay takes a payment from the customer’s wallet to your ledger: it watches the chain, screens the sender, books the money in a double-entry ledger and tells your systems. The people who run the money — operators, approvers, compliance, sales — work in the same platform.

  • Tron, Ethereum, Base and Bitcoin
  • Non-custodial by default
  • Test mode on public testnets
  • Every operation is an API call
The DDXPay back office: the Payments list with credited, quarantined and reversed payments in USDT, USDC, ETH, TRX and BTC across Tron, Ethereum, Base and Bitcoin. The DDXPay back office in the dark theme: the Payments list.
The hosted payment page on a phone: the buyer sees the exact USDT amount, the network and the deposit address. The hosted payment page on a phone, dark theme.

Accept on

Tron USDTTRX Ethereum USDCUSDTETH Base USDCETH Bitcoin BTC

Why DDXPay

Three things other providers sell separately.

A payment provider, a back office and a CRM usually come from three vendors and an integrator in between. Here they share one database and one ledger.

01

Accept crypto without the headache

  • Hosted payment page, embeddable widget or plain API
  • Price in a fiat currency; the buyer pays in crypto at a locked rate
  • Underpaid, overpaid, late and wrong-network payments handled, not lost
  • Optional automatic conversion to stablecoins on arrival
02

Run the business from one place

  • Back office with roles: operator, approver, compliance, manager
  • Four-eyes payouts, address allowlists and limits
  • CRM whose funnel is built from real deposits, not typed-in numbers
  • Reports, audit trail and reconciliation with your custodian
03

Ask instead of clicking

  • An AI assistant that uses the same operations as the menu, within your rights
  • It reads on its own; anything that changes data waits for a person
  • Connect your own Claude or other MCP client with an API key
  • Off until you turn it on, with your own model key

How a payment flows

From the customer’s wallet to your ledger — and nothing counted twice.

Every deposit takes the same path, in test mode and in live mode. Each step records what it decided and why, so a person can always see where a payment is and what it is waiting for.

  1. Customer pays

    On your page, our hosted page or by invoice link. The buyer can choose the coin and network you accept.

  2. The chain is watched

    Confirmations are counted per amount. A transaction is recorded exactly once, and a reorganised block is reversed by a compensating entry.

  3. The sender is screened

    Sanctions first, always. Then a risk score against your thresholds: clear, review by a person, or quarantine.

    ClearReviewQuarantine
  4. Money is booked

    A balanced double-entry transaction credits the merchant and takes the fee. Money held for review is booked too, outside the spendable balance until a person releases it.

  5. Your systems know

    A signed webhook reaches your server, retried if it fails; e-mail and in-app notifications reach your people.

Want stablecoins, not volatility? An auto-conversion rule turns an incoming ETH, TRX or BTC deposit into the stablecoin you choose right after it is credited, within a slippage limit you set.

Conversions

The platform

Everything between “paid” and “paid out”.

One platform, one ledger, one set of permissions. Use all of it, or start with the gateway and add the rest later.

Payment gateway & checkout

Payment intents, deposit addresses, a hosted payment page and a 3 KB embeddable widget. Prices in fiat, branded with your name, logo and colour.

Gateway

KYT, sanctions & Travel Rule

Every deposit is screened. Thresholds live in a versioned jurisdiction profile, and every decision records the version that judged it.

Compliance

Custody your way

Connect your own custodian account or bring addresses from your own wallets. DDXPay holds no private keys.

Custody

Double-entry ledger

Append-only, balanced to zero, reconciled with the custodian. Every balance is two numbers: free and total.

Ledger

Payouts & refunds

Four eyes on every withdrawal, allowlisted addresses with a cooling-off period, daily limits and batch payout runs.

Payouts

Conversions & fiat

Swap balances by hand or by rule. Off-ramp to a bank account and on-ramp from one through a fiat-rail provider.

Conversions

Invoices & subscriptions

Numbered invoices with VAT by rate and PO numbers, payment links that last until the due date, and recurring billing.

Invoicing

Card payments

Take cards next to crypto through your own Stripe account, with webhooks for your shop when a card payment is paid, refunded or disputed.

Cards

Back office & CRM

Client cards, desks, kanban boards, tasks and a conversion funnel — first deposit, qualified first deposit, net deposit — computed from the money that actually moved.

Back office & CRM

AI assistant & MCP

AI & MCP

The product, not a mock-up

This is what your team works in.

Real screens of the DDXPay back office, running in test mode with sample data. Light and dark, like the rest of this site.

Payments list: status of every payment as a colour and a word, expected and received amounts, asset, chain and confirmations. Payments list in the dark theme.
Status is a colour and a word: an operator scanning twenty rows finds the ones that need a person without reading them all.
One payment: the transaction, sender, block, risk check and every recorded step from creation to credit. One payment in the dark theme.
One payment, start to finish: the transaction and its explorer link, the risk check, the deposit, the webhooks and the refunds — each with the moment it was recorded.
Counterparty screenings: each check with its outcome, score, threshold, profile version and provider. Counterparty screenings in the dark theme.
Every screening shows its score, the threshold it was read against, the profile version that judged it and a sentence a person can repeat to a client.
The CRM client board: a column per status, a card per client, with owner, next task and last contact. The CRM client board in the dark theme.
A column per status, a card per client. Drag a card to change its status; the history records who moved it and from where.
The sandbox: take a test payment and choose what happens to it — paid, underpaid, overpaid, held for risk and more. The sandbox in the dark theme.
Take a test payment and choose its fate. It runs through the same pipeline as a real one, so what you see here is what you get in live mode.
AI settings: the assistant and MCP channels, the personal data an agent may see, and which operations it may use. AI settings in the dark theme.
Everything is off until you turn it on: which channels, which operations, and which categories of personal data reach the model.

For developers

An API you can build a business on.

Every operation in the platform is an API call with the same permissions as the screen. Test keys and live keys never see each other’s data.

  • Idempotent writes. Send an Idempotency-Key and retry safely; one order number is one payment.
  • Signed webhooks. HMAC-SHA256 over the timestamp and the raw body, retried with back-off.
  • A real sandbox. Nine scenarios, from paid to reorganised to sanctioned, through the real pipeline.
  • Node.js SDK and a WooCommerce plugin with zero runtime dependencies.
# Price in euros; the buyer pays USDT on Tron at a locked rate.
curl https://api.example.com/api/v1/checkout-sessions \
  -H "X-Api-Key: $DDXPAY_API_KEY" \
  -H "Idempotency-Key: order-10482" \
  -H "Content-Type: application/json" \
  -d '{
    "reference": "order-10482",
    "fiatAmount": 149.00,
    "fiatCurrency": "EUR",
    "assetSymbol": "USDT",
    "chainName": "tron"
  }'

Security & compliance

Built to the strictest standard. Configured for yours.

The compliance features are engineered to the level of the strictest regime we know — the EU — so that whatever applies to you can be switched on and tuned, not built later.

Isolation in the database

Data is tagged with its tenant and, for money, its mode. PostgreSQL row-level security refuses everything else — and fails closed.

Test can never touch live

The mode comes from the key, never from the request. A test key cannot reach a live adapter — checked on every build.

Four eyes on money

The person who requests a withdrawal cannot approve it, and nobody can grant rights they do not hold themselves.

An audit trail that cannot be edited

The application can only add audit rows, never change them. Refused attempts are recorded too.

Secrets stay secret

Provider keys are encrypted at rest and never returned by the API — a screen shows the last four characters, nothing more.

Frozen funds are a state

Stablecoin issuers can freeze an address at any time. A freeze is a ledger state: free and total balances stay honest.

Let’s look at your flows together.

Fees are agreed per client. Tell us what you sell, which chains your customers use and roughly what volume you expect — we will show you the platform on your own scenarios.