Invoice-first
One invoice, supported balances
Unified Invoice Pay should help a payer complete a specific invoice. It should not turn Arqis into a generic multi-chain wallet or bridge interface.
Roadmap notice: Unified Invoice Pay is a coming-soon / experimental roadmap module. It is not active in the current Arc Testnet MVP.
Unified Invoice Pay
Pay one Arqis invoice using USDC balances across supported chains. Arqis creates a payment plan, the payer reviews it, and settlement is verified before the invoice is marked paid.
Settlement
Clean USDC received
The seller should see a simple result: the invoice is paid, USDC settled on the selected chain, and a receipt with verification details is available.
Future flow
How Unified Invoice Pay should work
Scan supported USDC balances
Arqis reads supported chain balances and calculates how much USDC is available to pay the invoice.
Create a payment plan
The plan shows source chains, amounts, estimated fees, estimated time, and destination settlement chain.
Payer signs payment intent
The payer must review and approve the plan. Arqis should never auto-spend or auto-route funds.
Settle and verify
Settlement completes on the destination chain, backend verification confirms it, and only then is the invoice marked paid.
Concepts
- Unified balance: total USDC available across supported chains.
- Payment plan: source chains and amounts used to pay the invoice.
- Pending spend: USDC waiting for settlement or verification.
- Settlement chain: chain where the seller receives USDC.
- Receipt: proof that the invoice was paid and verified.
Important clarification
Unified balance is not one shared wallet balance. Each chain has its own balance. Arqis only creates a payment plan and verifies settlement before marking the invoice as paid.
Gateway fit: Circle Gateway and Forwarding Service can support future cross-chain USDC spend and gasless destination mint flows. Arqis should present this as payment UX, not as a bridge product.