Merchants / Websites0
Providers0
Wallets0
Active Wallets0
➕ Add Merchant / Company Request
New companies first enter the approval queue. They become active only after Admin approval.
🏢 Merchant / Company Requests
No requests loaded.
🔑 Merchant API Keys
The full API secret is shown only once when created. Store it securely.
Hierarchy & Controls
SMS isolation: every Wallet has its own sms_wallet_<wallet_id> table. New SMS is synced automatically from the canonical SMS table.
Provider name is completely free-form (e.g. IRAN01, IRAN02, RUSIA05). The bKash/Nagad/Rocket/Upay values belong to the Wallet Type field, not Provider Name.
Connect first.
🔗 Link Merchant Device
The merchant device must be registered first. This does not expose your Admin Devices to the merchant.
🔐 Provider Device Permission Requests
A new wallet device can request access to a specific Provider. The request can include Device ID, internal UUID, Wallet Number and Wallet Type. Credential secrets are never shown; only credential status is shown. Wallet creation stays blocked until Admin approves the request.
No requests loaded.
Quick Add Provider (custom name only)
Quick Add Wallet (Provider ≠ Wallet Type)
Enter the registered wallet/SMS Device ID (IPAY-...). The server resolves its internal UUID automatically. You do not need to know the UUID.