BlockSec and RedotPay Announce Strategic Partnership to Study Security and Compliance in Stablecoin Payments

September 09, 2026 — BlockSec and RedotPay, a global stablecoin-based payment fintech, have signed a strategic partnership framework agreement to advance Web3 payment security. Under the agreement, the two intend to explore long-term research and exchange on security and compliance in Web3 payments, working together to deepen understanding of how associated risks can be identified and defended against.

Payments grew up, and the security question changed shape

Stablecoin payments are no longer a proof of concept. They are everyday consumer spending and merchant settlement.

It is no longer only about whether a single smart contract contains a bug, but about how wallet keys are managed, whether signing logic holds up under adversarial conditions, where funds came from and went, and how quickly an anomaly can be located and contained. The crypto payment chain is longer than most Web3 businesses: users, wallets and exchanges, payment gateways, card issuers, payment networks and merchants, and a failure at any node may affect end users and partner banks.

Since 2021, BlockSec has provided smart contract and wallet security audits, on-chain compliance and incident response services to crypto payment providers, exchanges and custody platforms. The Phalcon Compliance address label database now covers more than 600 million addresses, and the team has worked through a large number of real security incidents. RedotPay knows best where the friction sits in a payment business, BlockSec has seen enough attack techniques and incident scenes to know how failures unfold, and it takes both to assemble a full picture of the risk along this chain.

What BlockSec and RedotPay intend to study together

The questions BlockSec and RedotPay intend to collaborate on together include where the security boundaries of wallet and payment systems should be drawn, which design choices in payment contracts and settlement logic most often lead to trouble, how threat intelligence and malicious address data can actually be put to work on the business side, and how on-chain transaction monitoring, KYT and anti-money-laundering requirements can be applied to payment flows without trading away user experience.

BlockSec and RedotPay are both watching AI-driven payment agents especially closely. The resulting risk model differs fundamentally from human-initiated payments, and the boundary conditions and safeguards deserve to be worked through as this kind of payment scales.

Stablecoin payments are turning from an emerging sector into real financial infrastructure, and how far that goes depends in large part on whether security and compliance can keep pace. Looking ahead, BlockSec and RedotPay will continue to deepen their collaboration on payment security and compliance, and will share what comes out of that work with the wider industry when the time is right.

This publication is for informational purposes only and does not constitute legal, financial, investment, or other professional advice. It does not represent an offer or solicitation to buy or sell any products, securities, or financial instruments. The information is provided on an “as is” basis as of the date indicated and is subject to change without prior notice. Rabbit7 Holding (BVI) Limited (“RedotPay”) makes no representations or warranties, express or implied, regarding the completeness, accuracy, reliability, or timeliness of the content. RedotPay, along with its directors, officers, agents, employees and affiliates, expressly disclaims any liability for any direct, indirect, special, incidental, consequential, punitive or exemplary damages, arising from the use of or reliance on this publication. Readers should seek independent professional advice before taking any action in relation to the matters concerned herein. This publication is strictly confidential and may not be reproduced, distributed or transmitted in any form or by any means without RedotPay’s prior written consent. The English version shall prevail in the event of any discrepancy or inconsistency between the various language versions hereof.