On May 20, 2026, what should have been an ordinary workday dedicated to regulatory documents and technical updates was connected by two seemingly unrelated announcements into a new coordinate axis: at one end, Plume's subsidiary obtained a Class M license issued by the Bermuda Monetary Authority (BMA), becoming the first regulated on-chain treasury management company in Bermuda, seen locally as the first type of entity to receive formal regulatory recognition; at the other end, MoneyGram announced its integration into the Tempo mainnet, which focuses on payment and high-frequency payment scenarios, serving as the Anchor Remittance Validator. In its statement, it described this as the starting point for bringing its global payment network, compliance experience, and operational capabilities into a more open and interoperable payment network. The former actively positioned itself alongside large compliant entities like Circle and Coinbase after obtaining its license, boasting that "illegal transaction block rate is only 0.000005%" as a single source narrative to shape its risk control image; the latter chose to directly engage at the public chain verification layer, connecting the cross-border flow of real-world funds with on-chain assets, and under the framework of collaboration with Tempo and Stripe, aimed at piloting settlement solutions based on on-chain assets in real clearing scenarios, although the specific settlement paths are yet to be disclosed. The significance of this combination lies in the fact that traditional financial institutions and payment agencies are no longer just "customers using the chain," but are beginning to enter roles of on-chain treasury management, cross-border clearing nodes, and even verifiers under the constraints of licenses and compliance obligations. The compliance framework built around KYC/AML and on-chain transparency globally is being forced down to the underlying public chain; this round of descent will directly reshape the regulatory landscape of cross-border payments and on-chain treasury management.

Plume Obtains BMA License: On-Chain Treasury Regulation

When the Bermuda Monetary Authority (BMA) wrote Plume's subsidiary's name on the license list, on-chain treasury management was clearly written into the regulatory landscape of this jurisdiction for the first time. The core meaning of the Class M license is not just a letter, but that the BMA officially recognizes "on-chain treasury management" as a financial service form that requires permits, complies with KYC/AML, and is subject to on-chain transparency requirements, incorporating it into the existing digital asset regulatory framework and regulatory sandbox. For Plume, this means that the scope of treasury operations is locked within the approved business, and its on-chain operations, customer access, and risk control must be accountable to regulatory authorities, rather than just to protocol users or DAO communities; the self-reported data of "the illegal transaction block rate is only 0.000005%" quoted in Plume's external communication is essentially also a way to prove to the BMA and potential institutional clients that its on-chain treasury can be viewed as a "clean custody account" in the traditional financial sense.

More importantly, after obtaining the license, Plume actively aligned itself with large compliant entities such as Circle and Coinbase, trying to convey to the market that on-chain treasury is no longer just a "DeFi tool," but a compliant infrastructure that can follow the traditional licensing path. Thus, this Class M license became a model—it sends a signal to other prepared or already operational on-chain treasury companies: as long as they are willing to hand over their business boundaries, anti-money laundering processes, and on-chain auditing capabilities for regulatory examination, the BMA is willing to include such entities into the formal licensing system, rather than exclude them from regulatory visibility. The next variable is not whether Plume is compliant "enough," but how many similar institutions are willing to accept similar licensing constraints, betting on the long-term path under a licensed framework for on-chain treasury business that originally straddled the gray area.

MoneyGram Joins Tempo as Remittance Validator

On the same day Plume obtained its license, MoneyGram announced its joining of the Tempo mainnet, focused on payments and high-frequency scenarios, where it is defined as an "Anchor Remittance Validator." In Tempo's narrative, this role serves as both a technical transaction verification node and an "anchor point" between the real-world remittance network and the on-chain settlement layer: MoneyGram will leverage its global payment and remittance network, compliance experience, and operational capabilities to participate in transaction validation and operations on the Tempo network, connecting on-chain asset channels with offline payment and collection systems, allowing on-chain accounting results to be realized in real fund flows.

Once a traditional cross-border remittance giant is not merely "accessing a new channel," but directly positioned at the public chain verification layer, the focus of KYC/AML and fund monitoring begins to shift. The globally emphasized real-name identification, risk screening, and traceability in the digital asset realm now have the opportunity to be "embedded" in on-chain infrastructure through compliant entities like MoneyGram: rather than allowing unregulated nodes to record transactions and then have banks conduct post-facto checks, it is better to place long-regulated remittance companies in verification positions, using their existing identity verification processes and suspicious transaction monitoring logic to conduct more meticulous screening of on-chain paths related to their businesses. Official statements have noted that this collaboration is "a further step towards a more open and interoperable payment network," supporting the cross-border flow of real-world funds based on on-chain asset channels; together with Tempo, MoneyGram, and Stripe's plans to introduce on-chain asset-based settlement solutions in real clearing scenarios (specific paths have yet to be disclosed), this step does not merely expand a technical option but officially pushes on-chain assets into the position of underlying settlement channels in the highly regulated cross-border remittance scene, forcing regulators to begin answering a new question: when compliance standards are directly written into node roles, will future cross-border clearing regulation focus on traditional intermediaries or regard the public chain verification layer itself as a new regulated infrastructure.

Traditional Payment Compliance Embedded in Public Chains

When MoneyGram appears on the Tempo mainnet as an "Anchor Remittance Validator," it is no longer just a part of the settlement chain but stands directly at the public chain consensus layer. It simultaneously emphasizes to the outside world that it will bring its global payment network, compliance experience, and operational capabilities onto the chain to participate in transaction validation and operations on the Tempo network, which means extending some responsibility for KYC, anti-money laundering, and sanctions screening from offline to the node itself. For regulators, this role is no longer just a “technical service provider” but more resembles a new type of settlement node: when on-chain verification rights are tied to real-world fund flows, the approval or rejection of suspicious transactions by nodes could be seen as compliance actions subject to licensing, rather than mere computational or staking decisions.

Traditional cross-border remittances rely on multi-level intermediary banks and clearing systems, with regulatory focus concentrated on offline account KYC, counterparty identification, and tracking fund flows through messaging; now the collaboration between Tempo and MoneyGram attempts to move part of the settlement process onto a public chain focused on payments and high-frequency scenarios, further enhanced by collaboration with Stripe to introduce on-chain asset-based settlement solutions in real clearing scenarios. Although the specific technical mechanisms and incentive structures of MoneyGram as a validator in Tempo remain undisclosed, as do the specific settlement paths of Stripe's funds between on-chain and offline accounts, what is certain is that once the "timestamp" and "path" of the clearing process are written into the public chain ledger, the regulatory perspective must shift from focusing solely on interbank messaging to viewing the public chain verification layer itself as a new infrastructure that requires entrance standards and compliance obligations to be defined.

Compliance Signals from Circle to Stripe

By placing Plume, MoneyGram, Tempo, and Stripe in the same picture, the direction of this change becomes apparent: at one end are Circle and Coinbase, which have already received licenses in multiple jurisdictions, making the issuance and custody of on-chain assets standardized financial products; at the other end is the Class M license issued by the BMA, for the first time formally including on-chain treasury management companies like Plume under local regulation; meanwhile, MoneyGram enters the Tempo mainnet with its global payment network and compliance experience as an Anchor Remittance Validator, collaborating with Tempo and Stripe to directly embed asset-based settlement based on on-chain assets into actual cross-border clearing scenarios. Plume, after obtaining its license, deliberately positioned itself alongside Circle and Coinbase, and MoneyGram bridges the typical on-chain functions of “verification” and “settlement” with traditional remittance business; these actions collectively communicate to regulators that licensed entities no longer view public chains as marginal testing grounds but are proactively assuming key financial functions such as treasury management, cross-border clearing nodes, and transaction validation on-chain.

For regulatory agencies, the globally emphasized parallel advancement of KYC/AML and on-chain transparency is now beginning to materialize into a more straightforward question: when licensed banks, payment companies, and approved on-chain treasury managers themselves occupy positions within on-chain infrastructure, who is responsible for the entrance standards, review obligations, and risk control boundaries of these nodes? Once rules concentrate on licensed entities, spillover effects can hardly be contained solely within themselves—unlicensed DeFi projects and small-to-medium platforms, if they continue to place critical liquidity and clearing paths on networks involving compliant entities like MoneyGram and Plume, will struggle to maintain the narrative of being a “pure technology provider.” The likelihood of being required to connect with stricter identity verification, transaction monitoring, list screening, and even registration and filing will increase. The series of coordinates from Circle, Coinbase to Plume, MoneyGram, and Stripe is pulling the industry towards a new baseline of "licensed on-chain," which will truly squeeze the survival space of small platforms and DeFi projects that do not obtain licenses and cannot sever connections with these compliant nodes’ funding paths.

Next Steps in Regulatory Games and Platform Opportunities

From Plume's acquisition of the BMA Class M license to MoneyGram's role as a remittance validator on-chain, regulatory boundaries have been quietly rewritten: on-chain treasuries and cross-border clearing are no longer seen as “gray testing grounds” but are pulled under the frameworks of licensing and KYC/AML standards. Bermuda uses segmented licenses and dedicated frameworks for digital assets to place on-chain treasury management into an auditable and revocable "box"; MoneyGram demonstrates that traditional institutions can also assume key node functions on the public chain by moving their compliance capabilities on-chain. Next, other jurisdictions are likely to compete along three pathways: either imitate the BMA by creating segmented license categories for treasury custody, on-chain payments, and node operations; or operate in regulatory sandbox formats, first locking in pilot scales and risk exposures, then deciding whether to solidify the rules; or directly require local licensed entities to include national anti-money laundering, reporting, and data retention obligations when operating public chain nodes, participating in validation or settlement. For platforms and projects, compliance lines will need to be front-loaded: first, they must sort and disclose their connections with licensed entities, including on-chain addresses, fund flows, and responsibility boundaries, leaving “interfaces” for regulators to hold accountable; second, they need to enhance on-chain monitoring capabilities, using transaction screening, list rules, and risk control feedback to meet the requirements of compliant nodes like MoneyGram and Plume; third, they must prepare for more detailed information disclosures, such as regularly publishing treasury structures, cross-border channel usage, and mechanisms for handling anomalies. The specific verification mechanisms of MoneyGram in Tempo and the settlement paths with Stripe are still undisclosed; once these technical details come to light, regulators in various countries will recalibrate the risk weights of “on-chain treasury managers” and “cross-border clearing nodes,” which will also determine who can truly remain at the table in the next round of cross-border compliance restructuring.

Join our community to discuss and grow stronger together!
Official Telegram community: https://t.me/aicoincn
AiCoin Chinese Twitter: https://x.com/AiCoinzh
OKX Benefits Group: https://aicoin.com/link/chat?cid=l61eM4owQ
Binance Benefits Group: https://aicoin.com/link/chat?cid=ynr7d1P6Z

免责声明：本文章仅代表作者个人观点，不代表本平台的立场和观点。本文章仅供信息分享，不构成对任何人的任何投资建议。用户与作者之间的任何争议，与本平台无关。如网页中刊载的文章或图片涉及侵权，请提供相关的权利证明和身份证明发送邮件到support@aicoin.com，本平台相关工作人员将会进行核查。