Connect orders, payment approvals and reconciliation.

For cross-border trade platforms and Agent development teams. From Hong Kong, we are designing the workflow between a business request and a verified payment result — with digital renminbi channels and open payment protocols as integration research directions.

Exploration & planning stage. This site does not process payments.

One intent. A controlled path.
  1. Payment intent
  2. Authorization policy
  3. Payment orchestration
  4. External channel · future evaluation
  5. Receipt & reconciliation

Exceptions → human review

Illustrative architecture · no live settlement

HONG KONGCROSS-BORDER TRADEAGENT ECONOMYAIRDB.HK

01 / Our direction

Hong Kong as the starting point. Cross-border workflows as the focus.

Our Hong Kong focus connects the needs of trade involving China with software built for global businesses. Digital renminbi channel research addresses the payment-rail layer; Agent authorization and x402 research address how software requests and approves a payment. We are exploring how these layers can work together, without assuming they are already connected.

02 / Platform

Four capabilities. One shared foundation.

Order context, authorization decisions and payment receipts: four proposed capabilities to keep the handoffs connected.

Planned

Payment orchestration

Connect an order, an approval and an external payment result in a traceable workflow.

Order & intent Coordinated workflow

Planned

Authorization & risk controls

Define who may act, for what purpose, within which limits — with human review for exceptions.

Identity & mandate Policy decision

Planned

Records & reconciliation

Link business events and external receipts so teams can investigate differences.

Events & receipts Reconciled business record

Exploring

Agent transaction interfaces

Translate machine requests into bounded transaction intents and explore protocol adapters.

Service request Authorized intent

03 / Solutions

Built around real workflows

For cross-border platforms and trade technology teams first. For Agent and paid-API developers next. Start with one workflow and a clearly defined owner.

04 / Research perspective

AI reshapes cross-border payments: efficiency, risk and the Agent economy

When software begins to initiate transactions, efficiency, authorization and responsibility must evolve together. An AirDB research perspective, not a product availability announcement.

Read the research x402 · Developers →

05 / Autonomy needs accountability.

A measured path forward

Autonomy needs accountability. ↗

Product exploration → no-funds prototype → conditional partner evaluation → platform expansion. Each step depends on evidence, not a promised launch date.

Platform →

Bring one workflow. Find the next practical step.

Describe your trade-payment process or Agent purchase use case. We will start by discussing the inputs, decision owner and result you need.