Payment orchestration
Connect an order, an approval and an external payment result in a traceable workflow.
Order & intent Coordinated workflow
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.
Exceptions → human review
Illustrative architecture · no live settlement
01 / Our direction
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
Order context, authorization decisions and payment receipts: four proposed capabilities to keep the handoffs connected.
Connect an order, an approval and an external payment result in a traceable workflow.
Order & intent Coordinated workflow
Define who may act, for what purpose, within which limits — with human review for exceptions.
Identity & mandate Policy decision
Link business events and external receipts so teams can investigate differences.
Events & receipts Reconciled business record
Translate machine requests into bounded transaction intents and explore protocol adapters.
Service request Authorized intent
03 / Solutions
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.
For trade platforms coordinating buyers, finance teams and suppliers: connect an invoice to its approval and payment receipt.
See the proposed workflow →For Agent and paid-API teams: turn a service request into a budgeted purchase with an accountable authorization decision.
See the proposed workflow →04 / Research perspective
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.
Product exploration → no-funds prototype → conditional partner evaluation → platform expansion. Each step depends on evidence, not a promised launch date.
Platform →Describe your trade-payment process or Agent purchase use case. We will start by discussing the inputs, decision owner and result you need.