---
title: Payments on EmpoorioChain
description: The payment pallets (escrow, logistics, subscription, paymaster), DUSD, and the eoonia:// request flow — at their real stage.
---

# Payments on EmpoorioChain

## Unit

DUSD (`pallet-emp-assets` asset #1) is the native stable unit; gas may be paid in DUSD through `pallet-paymaster` at 1.538462 DMS per DUSD (from TOKENOMICS.json, derived from the $0.65 canonical price). DMS pays fees otherwise: ~0.000025 DMS per transfer on the testnet; 80 % of fees burned, 20 % to treasury.

## Rails

- `pallet-escrow` — holds the buyer's DUSD; released on a delivery record
- `pallet-logistics` — dispatch and custody handoffs as events
- `pallet-subscription` — recurring charges
- `pallet-paymaster` — the merchant sponsors the customer's fee
- `pallet-sbt` — non-transferable loyalty credentials

All in runtime 220; no merchant transaction has used them yet.

## Request flow

1. The app builds an `eoonia://pay?...` link (or QR) with recipient, asset and amount.
2. Eoonia decodes it, quotes the fee with `payment_queryInfo`, and asks the user to sign.
3. The wallet returns submitted → included → finalized; the merchant reads the runtime event from its own node.

Live today for account linking and NFT minting (Empoorio Warehouse); the payment button is designed and not yet wired in Square Sellers / Eats.

## What does not exist

A fiat on/off ramp into DUSD, a merchant dashboard, and any regulatory answer for holding customers' stablecoins. The five commerce apps in production (Eats, Manager, Riders, Square Sellers, Warehouse) settle in fiat.