Skip to content

Industry solution · Sourcing & supply chain

Secure Crypto-to-Fiat Bridges for Sourcing Agents

Your buyers want to settle in stablecoin. Your factories want RMB in a bank account and will not touch anything else. You are the one holding both ends — and the one whose account is exposed if either end is undocumented.

For Hong Kong-registered sourcing and trading agents. Not tax, legal or accounting advice.

Get early access

The position you are actually in

  • You absorb the risk both sides refuse

    The buyer will not send a wire and the factory will not take crypto. The only way the order happens is if you stand in the middle and carry the part neither of them will — which means the exposure lands on your entity, not theirs.

  • Your margin is thin enough to be wiped out

    Sourcing commission is a few per cent. One frozen inbound payment is not a bad quarter; it is several orders of profit gone, and possibly the working capital you had already committed to the factory.

  • You cannot vouch for a wallet you did not check

    A new buyer sends USDT from an address you have never seen. You have no idea what it touched three hops ago, and neither does the buyer. Your bank will form its own view later.

  • The factory has heard the horror stories

    Suppliers who took payment through informal channels have had cards frozen. A factory that has been burned once wants to know exactly where the money is coming from before it books the production slot.

The Sourcing Trap: Buyer Crypto vs. Factory RMB

The trap is not that the two sides use different money. It is that the agent is the only participant who touches both, and therefore the only participant whose bank sees a flow it cannot explain. The buyer sees an outgoing payment for goods. The factory sees an ordinary domestic RMB receipt against a contract. You see both, and so does your relationship manager.

That asymmetry gets worse the better you are at your job. A sourcing agent consolidating orders across several buyers and several factories generates exactly the pattern monitoring is tuned to notice: many inbound payments from unrelated parties, followed by outbound settlements to unrelated parties, in a company whose stated business is a commission on other people’s trade. Every one of those flows is legitimate. None of them explains itself.

The wrong response is to go quieter — to move the crypto leg further from the paperwork, use an informal broker, keep the two halves of the transaction in separate places. That makes the pattern harder for your bank to reconstruct, not easier, and it is the reason a routine review turns into a closure. The thing that resolves the asymmetry is the opposite: make the connection between the two legs explicit and produce it before anyone asks.

What follows describes an arrangement in which your own Hong Kong company receives, documents and settles onward through its own bank. Nothing here routes money around a rule, and nothing here puts a third party in the payment path.

Build a Compliant Bridge Without Custodial Risks

The word "bridge" does more harm than good if it suggests a service that takes money at one end and releases it at the other. That is not this. Your Hong Kong entity is the bridge: it receives the buyer’s settlement into a wallet it controls, converts through its own licensed channels, and pays the factory in RMB from its own bank account, under its own contracts.

What sits beside that arrangement is screening and documentation. Before the buyer sends anything, the wallet is checked. As the transfer happens, the invoice, the purchase order and the transaction hash are bound together. When your bank or your factory asks what a payment was for, the answer already exists.

That distinction matters commercially as well as legally. A software vendor that never holds your funds cannot fail in a way that loses them, cannot be the party that freezes your settlement, and does not add a licensing question to a business that already has enough of them.

Where each leg sits

Buyer settles in USDT
Overseas buyer pays your Hong Kong entity’s wallet against your invoice.
Screened before it moves
The buyer’s wallet is checked for sanctions and inherited risk while you can still decline.
Your entity converts
Your own Hong Kong company converts through its own channels. We are not in the path.
Factory paid in RMB
A domestic bank transfer against a contract, documented like any other trade payment.

Accept Client USDT Safely with Pre-Transfer KYT

Screening before the transfer is the only version of screening that gives you a decision to make. Once the funds are in your wallet, learning that they came through a mixer four hops back does not help you — it tells you what your bank is going to find. Checked beforehand, the same information is a choice: accept, ask the buyer for context, or decline the order.

For an agent onboarding buyers you have not worked with before, this is also a commercial filter rather than only a compliance one. A buyer who will not identify the wallet the payment will come from has told you something useful about the order before you commit a factory slot to it.

  • Sanctions and risk-exposure check on the buyer wallet, before funds move
  • Provided by third-party blockchain analytics vendors — indicative, not determinative
  • A result you can act on: accept, question or decline

Document the Flow for Factory Assurance

Factories are not asking for a compliance certificate. They are asking a much simpler question: is this money going to arrive as a normal RMB bank transfer against our contract, and is anyone going to come asking about it afterwards. An agent who can show the shape of the arrangement — buyer contract, screened settlement, your entity, domestic payment — answers that question in a way "trust me, I have done this before" cannot.

The same file does double duty with your own bank. Because it is generated per transaction rather than assembled per enquiry, the connection between an inbound settlement and the outbound payment it funded is already recorded, which is precisely the link a reviewer is otherwise asking you to reconstruct from memory.

  • Each inbound settlement linked to the invoice and order it belongs to
  • A record you can share with a factory before it books production
  • Generated as the trade happens, not assembled after a query

Frequently Asked Questions

Do you convert the crypto or move money for us?

No. We never receive, hold, convert or transmit funds, and there is no LiLianMao wallet anywhere in the path. Your Hong Kong company receives the settlement into its own wallet and converts through its own channels. We screen the counterparty and document the trade beside that arrangement — we are not part of it.

Our buyers are in the UAE, Central Asia and Africa. Does that change anything?

It changes what screening is for, not whether you need it. Those corridors are where stablecoin settlement is most common precisely because correspondent banking works poorly there, and buyers in them are ordinary businesses. Screening tells you about a specific wallet and its transaction history, which is the relevant question about a counterparty regardless of where they bank.

Can we use this for the payment to the factory as well?

The payment to the factory is an ordinary RMB bank transfer from your own account and does not involve us. What we do is document it as the outbound leg matched to a screened inbound settlement, so the pair reads as one trade rather than as two unrelated flows. The factory receives money the way it always has.

We run dozens of small orders a month, not a few large ones. Does that work?

That is the shape screening helps most with, because the reconstruction problem scales with transaction count rather than with value. Fifty small settlements from fifty counterparties is a far harder file to assemble after the fact than three large ones. Pricing is per invoice volume, so this is a question of tier rather than of fit.

What do we tell a buyer who does not want their wallet screened?

That the check is on the wallet address and its on-chain history, which is public, and not on them personally — it is not a KYC file and we are not asking them for documents. A buyer who still objects after that has raised the more important question, which is why they would rather you did not look.

Screen the Wallet Before You Commit the Factory Slot

We are onboarding a small founding group, and sourcing agents are the users who feel the middle-position problem most sharply. Four questions and we will get in touch personally.

Get early access

Non-custodial software service. Screening is indicative, not determinative. No service can guarantee a bank’s decision.