Test the awkward cases
The sandbox simulates partial, late and overpayments, risk holds and reorgs. Same API and event pipeline as live mode.
YOUR INFRASTRUCTURE. YOUR PAYMENT RAILS.
From the first address to the final ledger entry. A self-hosted gateway with a considered checkout and the tools to run it yourself.
Access by invitation · hello@morepay.tech
Own the keys. See every movement. Build with a real sandbox.
A clear amount. The right network. One address.
1BoatSLRHtKNngkd XEeobR76b53LETtpyT
01 / THE PAYMENT LIFECYCLE
An API call, a payment link or an invoice from the dashboard.
A dedicated address and exact instructions on the chosen network.
Automatic detection, chain confirmations and risk screening.
A signed webhook when the payment succeeds and credit is recorded.
Keep the asset, convert after release, or pay out from treasury.
02 / BUILT FOR DEVELOPERS
Decimal strings for amounts. Idempotent requests. Separate test and live keys. The details that make a payment integration dependable.
import { MorePay } from '@morepay/sdk';
const morepay = new MorePay(
process.env.MOREPAY_API_KEY,
{ baseUrl: process.env.MOREPAY_BASE_URL },
);
const payment = await morepay.payments.create({
amount: '25.00',
currency: 'usd',
asset: 'usdt',
network: 'tron',
order_id: 'order-payment-42',
}, { idempotencyKey: 'order-payment-42' });
Server-side examples. Set baseUrl to your deployment. Keep API and webhook secrets on your backend.
import { constructEvent } from '@morepay/sdk';
const rawBody = new Uint8Array(
await request.arrayBuffer(),
);
const event = await constructEvent(
rawBody,
request.headers.get('MorePay-Signature') ?? '',
env.MOREPAY_WEBHOOK_SECRET,
);
// event.type === 'payment.succeeded'
// event.data.object is the payment.
// Verify mode, order, currency and amount.
// Commit a deduplicated inbox before 2xx.
Verify the exact raw request bytes. Persist and deduplicate the event and business operation atomically before acknowledging. Fulfil only after a verified payment.succeeded event and order checks.
The sandbox simulates partial, late and overpayments, risk holds and reorgs. Same API and event pipeline as live mode.
Use the hosted page or embed the widget as a modal or inline sheet. Browser status is a display hint; your backend verifies settlement.
TypeScript SDK, OpenAPI, cursor pagination and a CLI for local webhook delivery and scenario testing.
03 / MADE TO OPERATE
Create invoices and payment links by hand. Follow a payment from detection through review, fees and refunds, with a timeline that explains what happened.
| Amount | Asset / network | Status | UTC |
|---|---|---|---|
| 25.00 USD | USDT / Tron | Succeeded | 12:04:32 |
| 0.00042000 BTC | BTC / Bitcoin | Processing | 12:03:18 |
| 50.00 USD | USDC / Solana | In review | 12:01:06 |
payment.succeeded
200 OK
Signed payload · delivery history · retries
Risk and AML signals feed a review queue. Held funds stay on their deposit address until an authorized decision.
The operator configures fees and who pays them. Fee splits, balances and refunds are recorded in the ledger.
Follow sweeps, automatic gas top-ups, payouts and settlement rules. Reconcile the ledger against on-chain balances.
04 / ACCEPT BROADLY. SETTLE DELIBERATELY.
Accept a payment in one asset and convert released funds into your treasury asset. Compare eligible quotes across configured venues, with guards for slippage and fixed costs.
Instant swaps, exchange adapters and intent or bridge routes share one routing model. Availability depends on the enabled adapter, pair and operator configuration. A venue can hold funds during conversion; the dashboard keeps that exposure visible.
BTC / Bitcoin → USDT / Tron
Illustrative routes, not live quotes
05 / A CLEAR CUSTODY MODEL
Keys are generated on the operator’s server. Seeds are encrypted at rest. The API works with public derivation data; signing is checked against policy.
Balance changes use a double-entry ledger. Payment transitions record events in the same database transaction. Reconciliation can freeze signing on a mismatch.
Signed webhooks, scoped keys, two-factor authentication, sanctions and token blacklist screening, and manual holds. These controls do not replace an operator’s legal obligations.
BTC, LTC, DOGE, ETH, TRX, SOL, TON and supported USDT / USDC rails. Token availability follows the registry and your deployment configuration; not every token exists on every network.
06 / RUN IT YOURSELF
Deploy with Docker Compose. Bring your domain, RPC connections, mail service and keys. Own the database, backups and operating policies.
More Pay is currently an internal product. Public sign-up is closed; self-hosted source distribution is planned.
MORE PAY
Evaluating More Pay for your business? Get in touch for an invitation.
Access by invitation · hello@morepay.tech