TL;DR
- Request Network launched a dashboard centralizing merchant onboarding, branding, fees and wallet screening for payment platforms, gateways and marketplaces from a single interface.
- Merchants configure settlement networks and stablecoins through branded links. Platforms customize payment pages, set merchant-specific fees and receive margins onchain without holding merchant funds.
- Wallet screening uses Hypernative or Merkle Science, blocking payments that fail checks. Super administrators control sensitive settings while teams manage routine merchant operations.
Request Network has launched a unified dashboard for platforms managing multiple merchants, bringing onboarding, payment branding, fees and wallet screening into one interface. The official announcement dated October 29 confirms that the orchestrator dashboard is already live. Designed for gateways, marketplaces and payment platforms, the tool extends Request Network’s onchain payment infrastructure by allowing operations teams to manage merchant configurations without repeatedly involving developers.
Unified Merchant Operations With Custom Fees and Wallet Screening
Merchant onboarding now runs through branded links generated directly by platform operators. Merchants connect a wallet, choose their preferred settlement blockchain and stablecoin, and configure screening providers when permitted. The process comprises four steps, while platforms can alternatively automate onboarding through an API. A consolidated merchant list displays client identifiers, onboarding status and configuration details, with CSV exports and deactivation controls available.
The dashboard also enables white-label payment pages with configurable branding. Operators can apply either their own identity or a merchant’s name, colors and logo without additional development. For platforms serving several businesses, this keeps customer-facing payment pages consistent with the relevant brand while centralizing administration behind the scenes.
Fee management is another central feature, with operators able to establish default charges and override them for individual merchants. Collections and payouts can carry separate fees, paid by either the customer or merchant. Request says these fees are split onchain during the payment transaction and routed directly to the platform’s wallet, without requiring the operator to custody merchant funds.
For transaction controls, wallet screening can be configured per merchant through Hypernative or Merkle Science. Platforms may select primary and backup providers, use standard checks or apply custom know-your-transaction rules through their provider accounts. A failed screening check prevents the payment from initiating. Administrative permissions also distinguish routine merchant management from sensitive settings reserved for the super administrator, including fee destinations and screening policies.
This operational focus complements established approaches to multisignature payment approvals and simplified stablecoin transactions. The new release targets payment intermediaries rather than individual merchants alone, giving them a single interface for running merchant programs. Request says platforms can create an orchestrator identifier through one wallet-based API call, after which the dashboard appears on their next connection. Its effectiveness will ultimately depend on adoption by payment operators, not merely feature availability. The development also fits the broader operational challenge of crypto-denominated invoice payments.
