Features

IDNWallet is not “another ordering tool”. We help merchants build their own digital entry:

• Domain = merchant identity and brand URL
• Browser = universal access without an app
• Receipt → Photos = the customer’s own return door and commerce memory

Portal, coupons, listen modules, and Apps are operating capabilities on that entry.

Merchants sign in at merchant portal with country code + phone to:

• Bind their business domain (CNAME — see CNAME guide) to claim digital identity
• Bind their domain-wallet ID
• Enable coupon / card / listen modules

Visitors claim coupons on your domain; the coupon App redeems them. See Merchant Apps.

One electronic card per domain in the portal. Ask visitors to screenshot — the image is also a return entry.

Visitors submit info on your domain:

• The platform forwards information only — no payment collection
• The wallet does not store order history — ask customers to screenshot the receipt (domain URL + QR for return visits from Photos)
• Merchants use the unified merchant App

The Listen / merchant App is the operating tool on top of the entry — not the product hero. See Merchant Apps.

Publish in the portal so the entry goes live on your domain. See the publishing guide.

Global static config at /config.json for the offline App. See App config docs.