Secure event delivery for China-connected businesses
Receive critical payment and platform callbacks through a stable public endpoint, process them in a regional Traffic Plane, and deliver them to public or private systems without centralizing payloads in the SaaS control plane.
The China Market Challenge
Payment providers in China require reliable, fast callback delivery into regional or private network systems. Direct connections often fail behind NAT, firewalls, or without proper routing configuration.
Firewall headless
Most Chinese providers require inbound connections or specific firewall rules that are difficult to maintain.
Regulatory restrictions
Data localization and cross-border requirements complicate direct connections.
Provider-specific requirements
Each payment provider has unique technical requirements and integration patterns.
Limited public ingress
Few options for reliable inbound connections from Chinese payment providers.
Payment Callback Wedge
Zen Mesh provides a stable public callback endpoint that receives webhooks from Chinese payment providers (Antom/Alipay, WeChat Pay, UnionPay) and delivers them to your regional or private systems without requiring inbound firewall changes.
Receive webhook
Public endpoint receives provider notification
Local processing
Validate, verify, and transform in regional Traffic Plane
Deliver privately
Route to your internal services without inbound ports
Payload Locality: Hard Architectural Commitment
Customer event payloads are received, verified, transformed, routed, retried, and delivered inside the regional or customer-owned Traffic Plane where they enter Zen Mesh. The Zen Mesh control plane does not proxy, replicate, or retain those payloads. A payload crosses a regional boundary only when the customer explicitly configures a destination across that boundary.
Bounded operational metadata may reach the Control Plane: resource identifiers, policy versions, cryptographic digests, health, delivery outcomes, audit receipts, evidence metadata.
Regional Architecture
Canadian control plane receives metadata only and governs delivery policies. Regional China-market Traffic Plane processes payloads locally. Hong Kong and mainland AWS China options are under evaluation for account and ingress feasibility.
Control Plane
Canadian-based
- Receives only metadata
- Governs delivery policies
- Manages resource allocation
- Delivers evidence and audit logs
Traffic Plane
Regional China-market
- Receives customer payloads
- Processes locally
- Validates and transforms
- Delivers to destinations
Provider Roadmap
Antom / Alipay
OFFICIAL DRAFT PLANNED- Asynchronous payment notifications
- Signature verification
- Acknowledgement
- Retries and duplicate handling
- Active inquiry/reconciliation
- Private or regional delivery
WeChat Pay
OFFICIAL DRAFT PLANNED- Payment-success callbacks
- Signature and encryption requirements
- HTTPS endpoint posture
- Firewall/IP considerations
- Retries and duplicate notifications
- Idempotent processing
UnionPay
PLANNED- Backend notification URL
- Asynchronous transaction results
- Signature verification
- Response deadline handling
- Retry behavior
- Reconciliation support
Secondary Candidates (Research Only)
- Feishu (Research)
- DingTalk (Research)
- WeCom (Research)
- Chinese commerce platforms (Research)
Private and Public Delivery Targets
Deliver to public HTTP endpoints without deploying infrastructure, or deploy Edge Lite or Kubernetes Edge Plane for private targets behind NAT/firewall. Outbound-only — no inbound ports required.
Security and Evidence Posture
Regional Traffic Plane ensures payload locality. Control plane processes only metadata. Provider Pack templates provide structured defaults for verification, event classification, and operational visibility.
Design Partner Recruitment
Building with Antom/Alipay, WeChat Pay, or UnionPay? Zen Mesh is recruiting design partners that need reliable callback delivery into regional, Kubernetes, or private-network systems. Design partners help validate provider requirements, operational workflows, and regional deployment needs.
Apply as a Design PartnerCurrent Maturity and Non-Claims
Explicit Non-Claims
- Chinese Provider Packs are not generally available yet
Development in progress, not GA
- Zen Mesh is not claiming AWS program acceptance
No mention of AWS in any capacity
- Zen Mesh is not claiming AWS partnership
No partnership language anywhere
- Mainland China hosting is not yet production-live
Account feasibility review only
- ICP recordal is not complete unless separately proven
Not addressed, not claimed
- Chinese regulatory compliance is not claimed
Explicitly not claimed
- Payload-locality production enforcement is scoped by current evidence
Architectural commitment, not production evidence
- Provider sandbox fixtures are not provider production validation
Sandbox testing, not production validation
- No guaranteed or exactly-once delivery claim
Standard retry/recovery, not exact-once guarantee