Payments and milestone release

This is a preparation schedule, not an invitation to send funds. The proposed flow is buyer funding into an account administered by Merco through Airwallex, followed by supplier payouts as agreed milestones are reached. Whether that flow is permitted depends on the provider contract, account model, funds ownership and applicable regulatory rules. An ordinary Merco wallet must not be described as protected escrow solely because Airwallex provides it.

Contracted payment-provider entity: To be confirmed with Airwallex.

Approved funds structure: Pending written provider approval and regulatory assessment; no approved structure is asserted.

Before activation, each payment schedule must state who legally receives and owns/holds each balance, the account structure and relevant provider terms. Instructions must identify the beneficiary, currency, amount and order reference. Paying an invoice for Merco’s own software is distinct from funding a supplier’s goods order.

The final schedule must explain segregation/safeguarding, reconciliation, insolvency treatment, any interest or deposit-protection position and limitations. No bank deposit guarantee, insurance, trust or bankruptcy remoteness is promised by this draft. Customer funds may not be used to finance Merco’s operating expenses.

The accepted buyer–supplier order states each milestone, release amount, required evidence, approving party and dispute procedure. A status label or uploaded file alone is not proof that every release condition is met. Parties must agree how an approval is authenticated, corrected or challenged.

Automatic release, deemed acceptance, inspection deadlines and silent-approval rules apply only if expressly agreed before funding and permitted by the provider arrangement. The final terms must specify maximum holding periods and the procedure for delayed manufacturing, failed delivery or missing evidence.

Disclose Merco fees, provider charges, FX basis and the person bearing them before funding. A refund follows the agreed order outcome, lawful dispute resolution and provider constraints. The final schedule must identify who bears chargebacks, transfer reversals, shortfalls and mistaken funding.

A payout request is not a completed payment. Provider failure, missing verification or blocked transfers must be recorded and communicated; records must reconcile the remaining balance and responsibility for resolving it. No party may silently mark a supplier paid when funds have not arrived.

Report a disputed release promptly to Contact email to be confirmed before publication with the order reference and evidence. Merco coordinates the agreed process; binding ownership disputes are not resolved merely by changing a dashboard entry. The final schedule must identify when funds are paused, who can direct release/refund, how unresolved disputes proceed and which law/forum governs.

Paid order funding is conditional on a documented permissible structure, active provider capabilities, counterparty verification and accepted final terms. The payment schedule must be revised to the approved arrangement before activation.