A company announces it is entering Vietnam. The release names a strategic partner, describes a large market and promises to launch soon. A few months later, I ask a simpler question: what can a customer in Vietnam actually buy or use today?
Sometimes there is a clear answer. Sometimes there is a memorandum, an event photo and a website with a Vietnamese language selector. Those are different stages of work, yet they often travel under the same headline.
I see this from both sides of the table. At 43to.one, I work on the local groundwork foreign technology, fintech and Web3 companies need before they can operate in Vietnam. At BlockPR, I work on communications and the trust that a credible market presence requires. That makes me sympathetic to companies testing the market. It also makes me wary of communications getting ahead of execution.
The Vietnam Red Flag Index starts with a basic rule: describe the stage you can prove. An intention to enter, a signed agreement, regulatory permission, a usable product and paying customers are five different claims.
The announcement is the first document, not the verdict
Take Airwallex's March 2025 announcement. The company said it had signed definitive agreements to acquire CTIN Pay, a licensed Vietnamese intermediary payment provider, and explicitly said the transaction remained subject to closing conditions. That wording mattered. A signed acquisition agreement was a strong entry signal, but it was not, on that date, evidence that every Airwallex product was available locally.
There is now more to check. Airwallex identifies CTIN Pay as a group member in its Vietnam customer case study, and the State Bank of Vietnam's provider list names CTIN Pay and its licence. The case study names a customer using Airwallex products to manage funds between Singapore and a Vietnam operation. That is a stronger public evidence trail than the original acquisition release. It still leaves a question for any specific product: which entity provides it, to whom, and under what permission?
Compare that with Sumsub's January 2026 memorandum with the Global On-chain Economy Alliance. The announcement describes a proposed compliance role in crypto and stablecoin payments for international tourists. It is specific about the intended use case. The announcement itself does not identify a live merchant network, transaction volume or a date when tourists can use the service. The accurate description is a proposed collaboration. Its later operating status requires a separate check.
These examples make a point about language, not a judgment on either company. A well written release can accurately describe an early step. The trouble begins when readers, investors or potential partners treat that step as evidence of a finished business.
Five questions behind every Vietnam launch
I would test each announcement against five questions.
What exactly is available? Name the product, eligible user and action that user can complete. An app listing or translated landing page may show interest in Vietnam. It does not establish that a Vietnamese customer can be onboarded, pay, transact and obtain support through an approved route.
Who has permission to do what? For payments, identify the licensed Vietnamese entity and the service covered by its licence. For crypto assets, identify the applicable activity and the responsible operator. Resolution 05/2025/NQ-CP created a controlled pilot and ties service provision and related marketing to an operator licensed by the Ministry of Finance. A partnership with a potential applicant does not transfer that status to a foreign platform. Permission must be checked against the product and the legal entity making the offer.
What does the partner actually do? "Strategic partnership" can mean a referral channel, a technology integration, a pilot, an investment or an agreement to explore. I want to know what each party must deliver, who pays for the work and what milestone triggers the next stage. A memorandum is useful evidence of access. A completed integration or active distribution agreement is evidence of execution.
Who owns the Vietnam outcome? Which legal entity signs with the customer? Who handles complaints, compliance decisions, settlement, partner escalation and local support? A country representative can create meetings. A local operating owner needs the authority and resources to resolve what happens after the meeting.
Who has paid? A named customer case, with consent and a defined scope, is much stronger than a launch event. Revenue figures may be confidential, so the test should allow other evidence: a live integration confirmed by both sides, a repeatable onboarding path, or a customer willing to describe the use case. When commercial evidence cannot be disclosed, the finding should say so rather than assume there is none.
The score must follow the evidence
For the first index, I would select 20 public entry, partnership or "launching soon" claims made by foreign fintech and Web3 companies. Each record would preserve the exact wording and date of the original claim, link to that source, then separate what is confirmed from what remains unverified. Company statements, partner statements, official registers, product terms and documented customer use would be kept distinct. A source published later would update the status, not rewrite what the original announcement said.
The score should measure public evidence, not whether a company is good or bad. My proposed ladder runs from announced intent to named counterpart, documented operating route, usable product and verified customer activity. A case can occupy different stages for different products. Someone may be operating a cross border business account route while still exploring a domestic payment product. One headline cannot settle both questions.
"Unverified" is an important category. A company may have a private pilot or confidential customer contract. Public research cannot prove its absence. Before publishing an adverse finding, I would send the company the exact claim, sources, questions and proposed wording, then allow a reasonable response window. Its substantive answer and any correction would appear with the record. If the evidence changes, the index should show when and why the status changed.
This is also why I would not publish a neat league table of 20 companies based on press releases alone. The work is in checking the route between the announcement and the first real transaction. That route can include a licence, an acquisition, a local partner, a product integration, a customer contract and a person with authority to keep it running.
Vietnam is moving quickly, but regulatory change makes precision more necessary. Circular 39/2026/TT-NHNN, effective 19 September, clarifies an international payment route through accounts held by foreign credit institutions at Vietnamese banks. It creates a specific route for a specific class of institution. It does not answer the entry question for every nonbank payment startup. The crypto pilot raises a different set of questions about licensed operators, ownership and the activities a foreign partner can perform.
If I were spending money on a Vietnam launch, I would welcome that level of scrutiny. It can reveal a missing contract or licensing assumption before a campaign pushes customers toward a service that is not ready. If I were evaluating a potential partner, I would ask for the same evidence before repeating its "Vietnam launch" claim in my own materials.
The eventual Red Flag Index should make that evidence visible, one claim at a time. Until then, the most useful question remains the least glamorous one: what can a real customer do in Vietnam today, and who is accountable when they do it?
Share this post