Ares.Pay

Crypto checkout that
settles in 8 seconds.

Ares Pay is the payment backend for Ares Studio. Customers pay with BNB or ETH (and USDT/USDC on each chain); merchants receive a license key the instant the on-chain transaction confirms. No custodial hot wallets, no chargeback risk.

BNB Smart Chain Ethereum Sepolia (testnet) USDT & USDC Multisig-owned
Read the docs Operator dashboard

How it works

1. Create intent

Ares Core calls POST /intents with the order ID, chain, and asset. The Worker signs a createIntent transaction with a low-privilege hot key.

2. Customer pays

The checkout page shows the contract address, exact amount, and a QR code. The customer pays from any wallet — the contract emits PaymentReceived.

3. Webhook fires

A Durable Object polls every 8 seconds, decodes the event, and POSTs a signed webhook to Ares Core with the intent ID and tx hash. License is issued.

4. Owner sweeps

Funds accumulate in the contract. The Gnosis Safe owner calls sweep() or sweepToken() at any time to withdraw.

Why intent-based

Every payment is bound to a pre-created intent, identified by a 32-byte ID. This is what makes the gateway fast and safe:

  • Sub-second settlement UX. The price is locked at quote time, not at block time. Customers don't get re-quoted as the price wiggles.
  • 1% overpayment tolerance. Wallets and aggregators often round or pad. Native overpayments up to 1% are accepted; the difference is swept with the rest.
  • Source of truth = chain. If the Worker is down, the contract still accepts payment. When it comes back, D1 is reconstructable from PaymentReceived logs.
  • Hot key cannot move funds. Even if the Worker is fully compromised, the worst an attacker can do is create fake intents.

Security

Owner

Gnosis Safe
M-of-N multisig. Sweeps and config changes require multiple signers.

Hot key

intents only
A separate Worker-held key. Create/cancel intents — never moves funds.

Source of truth

on-chain
D1 can be rebuilt from PaymentReceived events at any time.

Deployed contracts

Both contracts are verified on their respective explorers.

ChainContractExplorer
BNB Smart Chain 0x171b0E75613954a82780973546dA87f3aD9FCB06 BscScan ↗
Ethereum 0x171b0E75613954a82780973546dA87f3aD9FCB06 Etherscan ↗

Same address on both chains by design — the deployer and nonce match, so CREATE2-style deterministic deployment produces identical addresses.