USDC Settlement & Reconciliation
The precise conditions for funded, completed, paid and refundable work.
What the current pilot actually supports
The first commerce pilot is coded for USDC on Base using an explicitly configured receiver and a real worker binding. The current direct-transfer model is not a deployed escrow system; refund terms require a separate manual repayment process. The ARQANT parent token network is independently under buyer-fit evaluation and is not fixed by this service pilot.
Payment enablement, worker availability and confirmations require production runtime verification; do not infer them from files alone.
Exact proof tuple
{
"order_id": "sample_order",
"chain_id": "real_verified_chain",
"token_contract": "real_USDC_address",
"recipient": "configured_receiver",
"amount_atomic": "49000000",
"tx_hash": "verified_0x64_hex",
"log_index": 0,
"confirmations": "finality_policy",
"source": "independent_chain_readback",
"status": "VERIFIED_AND_MATCHED"
}Funding and settlement states
NOT_FUNDED → PAYMENT_SUBMITTED → CONFIRMING → VERIFIED → ORDER_FUNDED → DELIVERED → ACCEPTED → RECONCILED / SETTLED
Payment failures: WRONG_NETWORK | WRONG_TOKEN | WRONG_RECIPIENT | WRONG_AMOUNT | DUPLICATE_HASH | REORG | REFUND_DUEA buyer-pasted hash does not prove payment. A transaction cannot satisfy multiple orders simply by replaying the same log.
Three payment modes
- Direct USDC pilot: beneficiary verifies incoming payment; refund requires separate transfer and support.
- Future escrow: smart contract holds user funds and releases or returns them according to agreed acceptance and dispute rules.
- x402 paid API: atomic pay-per-request semantics for services with suitable output and price; not a replacement for milestone-based contractual escrow.
Customer funds and liabilities
Keep a customer deposit liability until earned or contractually settled; do not count refundable balances as unencumbered treasury. Confirm refunds with a new signed transfer receipt rather than pretending an onchain transaction was reversed. A paid job, executed task and token financing event are separate ledger categories.
Production settlement acceptance
- Correct chain and token contract verified.
- Sender/counterparty and recipient reconcile to order terms.
- Atomic amount, transaction hash and event are unique.
- Block confirmations and finality policy are satisfied.
- Artifact, acceptance receipt and financial entry are linked.
- Refunds and rejected jobs have explicit disposition.