Reusing MatchingVietnam as the commerce engine

MCV Network should not maintain two parallel buying and selling flows. MatchingVietnam already has stronger ecommerce, vendor dashboard, product management, cart, checkout, and order management capabilities. It should become the commerce engine for product publishing, selling, buying, storefronts, and commerce order handling.

MCV Business OS at app.mcv.network becomes the operating back-office: operations, finance, accounting, wallet, reconciliation, compliance, invoices, payouts, subscriptions, and aggregated dashboards.

Decision principles

• MatchingVietnam owns seller products, stock, storefronts, orders, checkout, and commerce fulfillment.
• MCV Business OS owns wallet, ledger, top-up, escrow, payout, tax artifacts, invoices, roles, SSO, and internal operations.
• mcv.network is the corporate, marketing, SEO, and investor site. It does not run checkout.
• Public sellable items should be published through MatchingVietnam.
• Business OS displays synchronized commerce data for operations; it should not become a second checkout/order engine.

Ownership Boundaries

Workflow	System of record	Notes
Public storefront	MatchingVietnam	Product listing, category, SEO, detail page
Seller product management	MatchingVietnam	Reuse Botble ecommerce vendor/product module
Cart, checkout, order	MatchingVietnam	Buyers place orders on MatchingVietnam
Vendor commerce dashboard	MatchingVietnam	Products, orders, stock, fulfillment status
SSO and user profile	MCV Business OS	Central identity and profile
Wallet, top-up, escrow	MCV Business OS	InfoCMS, Stripe, ledger, reserve/release
Accounting, invoices, payout	MCV Business OS	MISA meInvoice, tax artifacts, reconciliation
MCV admin operations	MCV Business OS	Approval, finance, compliance, metrics
Corporate marketing	mcv.network	About, roadmap, investors, corporate SEO

Target Flow

flowchart LR
  Buyer["Buyer"] --> MV["MatchingVietnam storefront"]
  Seller["Seller / Vendor"] --> MVAdmin["MatchingVietnam vendor dashboard"]
  MVAdmin --> MV
  MV --> Checkout["Cart / Checkout / Order"]
  Checkout --> Order["MatchingVietnam order"]
  Order --> Sync["Order sync / webhook"]
  Sync --> OS["MCV Business OS"]
  OS --> Ledger["Wallet ledger"]
  OS --> Escrow["Escrow reserve / release"]
  OS --> Invoice["Invoice / tax artifact"]
  OS --> Payout["Seller payout"]
  OS --> Admin["MCV admin operations"]

Seller Flow

sequenceDiagram
  participant S as Seller
  participant OS as MCV Business OS
  participant MV as MatchingVietnam
  participant A as MCV Admin

  S->>OS: SSO login / update profile
  S->>OS: Submit proof of seller ownership
  A->>OS: Approve seller capability
  OS->>MV: Provision vendor access via SSO/sync
  S->>MV: Manage products, pricing, stock, storefront
  MV-->>OS: Sync product/order summaries for operations

Buyer Flow

sequenceDiagram
  participant B as Buyer
  participant MV as MatchingVietnam
  participant OS as MCV Business OS
  participant Pay as Payment providers

  B->>MV: Browse products / services / inventory
  B->>MV: Add to cart and create order
  MV->>OS: Send order intent / payment request
  OS->>OS: Check wallet or request top-up
  OS->>Pay: Create QR/Stripe payment when needed
  Pay-->>OS: Payment callback
  OS-->>MV: Confirm payment / escrow reserved
  MV->>B: Update order status

Synchronized Data

MatchingVietnam should send these data groups to MCV Business OS:

• Product summary: product id, seller id, slug, title, category, type, price, currency, stock, status.
• Order lifecycle: order id, buyer, seller, line items, gross amount, currency, status, timestamps.
• Fulfillment events: accepted, shipped/delivered, buyer accepted, cancelled, disputed.
• Financial events: payment required, paid, escrow reserved, release requested, refund requested.
• Seller store data: store id, owner account, public URL, status.

MCV Business OS should send back:

• SSO identity token.
• Seller capability status.
• Wallet/payment status.
• Escrow reserved/released status.
• Invoice/payout/compliance status.

Implementation Steps

1. Freeze new checkout development inside app.mcv.network.
2. Point public buy buttons on mcv.network to MatchingVietnam product/checkout URLs.
3. Turn Business OS seller product management into launch links to the MatchingVietnam vendor dashboard.
4. Standardize SSO between MatchingVietnam and Business OS.
5. Build order webhooks/sync from MatchingVietnam to api.mcv.network or app.mcv.network.
6. Replace Business OS order handling screens with operations/read-model screens backed by MatchingVietnam data.
7. Attach wallet, escrow, invoice, and payout to synchronized order lifecycle events.
8. Hide or disable legacy marketplace checkout routes after migration.

Route Direction

User action	New destination
Buy on mcv.network	MatchingVietnam product detail or checkout
Seller / Products in Business OS	MatchingVietnam vendor product dashboard
Seller / Orders in Business OS	Business OS operations view, synchronized from MatchingVietnam
Billing / Top-up	Business OS
Admin / Transactions	Business OS
Admin / Users / Roles	Business OS

Business OS Menu After Restructuring

The app.mcv.network menu is now organized by system ownership:

• Commerce Engine: links to MatchingVietnam for products, orders, vendors, and public storefront.
• MCV Operations: seller capability approval, compliance cases, affiliate reconciliation, users, and marketing languages.
• Finance & Accounting: transactions, service contracts, wallet, subscriptions, invoices, and payouts.
• Seller on Matching: vendor dashboard, product management, add product, store settings, seller orders, and Matching revenue.
• Buying on Matching: storefront, buyer orders, and buyer invoices.
• Legacy Data: guest post, agency service, and old inventory modules are kept only for reconciliation/migration, not for new checkout development.

Merchant Onboarding and eKYC

When a merchant/customer registers on MatchingVietnam, MatchingVietnam sends a signed server-to-server request to app.mcv.network/integrations/matching/merchants. Business OS automatically creates or updates the matching user, account, wallet, and external source mapping.

Current anti-spam and eKYC controls:

• Customer registration has a hidden honeypot field and minimum form timestamp to block instant bot submissions.
• Customer registration is rate limited by IP + email.
• Vendor registration is rate limited by IP + customer.
• Vendors must provide legal company name, tax/business registration number, and registered business address.
• When document verification is enabled, vendors must upload business registration and representative ID documents.
• Business OS creates seller accounts as pending until eKYC is approved, and only enables can_sell_products after vendor verification.

Advanced eKYC layers to build next:

• Disposable email, domain, and IP reputation checks.
• Mandatory email/phone OTP before vendor submission.
• OCR for business registration documents, with tax code/legal name matching against VietQR Business API.
• Duplicate tax code, document, phone, and device fingerprint checks.
• Face match/liveness for individual merchants or higher-risk categories.
• Risk scoring so admins can prioritize suspicious submissions.

Operations Note

During the transition, guest post, agency service, and software slot modules currently inside Business OS are treated as legacy marketplace modules. They should be used for reconciliation or migration into the MatchingVietnam product/order model, not expanded as separate checkout flows.