Security & Testnet Notice: Arqis currently runs on Arc Testnet. Testnet assets have no real-world value. Do not send mainnet funds. This prototype is not audited.
Future vision

Future Roadmap

Arqis is an invoice-first stablecoin payment app. The core product is sending invoices to Arqis names, paying in the payer inbox, verifying settlement, and keeping receipts clear for sellers and payers.

Product direction

Invoice inbox first

Seller sends an invoice to an Arqis name. The payer sees it inside Pay Invoice, reviews amount, memo, expiry, and status, then pays from wallet. This keeps invoice lifecycle, receipts, and status inside Arqis instead of relying on copied external checkout flows.

Direct receive

Wallet QR stays separate

Wallet QR remains useful for direct receives, faucet testing, and manual transfers. Tracked invoice payments should live in the Arqis inbox, status, and receipt flows.

Next product layer

Inbox experience

After payment confirmation is reliable, improve the Pay Invoice inbox: invoice detail, receipt view, payable invoice badge, due-soon indicators, and in-app notification history.

Trusted record

Receipts and detail

Give each invoice a clear detail view and receipt so payer and seller can inspect status, memo, expiry, transaction hash, paid time, and Arcscan proof.

Coming soon

Swap to USDC

Swap should be an invoice payment helper, not a trading product. If a payer does not have enough USDC, Arqis may offer a reviewed quote to convert supported assets into USDC before paying the invoice.

Open Swap guide
Coming soon

Unified Invoice Pay

Unified payment should be invoice-first: use USDC balances across supported chains, create a payer-reviewed payment plan, settle cleanly in USDC, then verify before marking the invoice paid.

Open Unified guide
How it should behave

Payer-controlled payment helpers

Keep invoice context first

Every helper starts from a payable invoice: amount, seller, memo, expiry, status, and settlement preference.

Show a reviewable plan

For swap or unified payment, show source assets/chains, fees, slippage or forwarding fee, estimated time, and settlement chain.

Require explicit confirmation

Never auto-spend, auto-swap, or auto-route. The payer must review and approve the plan before any transaction.

Verify before paid

The seller sees a simple result only after verification: invoice paid, USDC received, receipt and transaction proof available.

Future utility

Dust-to-USDC

When wallet assets are worth less than a threshold, for example under $5, Arqis can ask whether the payer wants to hide small balances or convert eligible balances into USDC.

Example prompt

Small balance cleanup

“You have 7 small balances under $5. Hide them, or convert eligible balances to USDC?”

Dust conversion: Only useful when fees and slippage are lower than the recovered value. Arqis should warn when conversion is not worth it.
Security roadmap: RLS tightening, backend payment verification, and richer invoice states are tracked in Security & Verification.

Other future ideas

  • Seller settings for settlement wallet, notifications, and invoice preferences
  • Quote lock window before confirming a swap or payment plan
  • Payment fallback if a swap or unified payment route fails
  • Receipt archive and export for small businesses
  • API + webhooks for invoice created, pending, paid, failed, or expired states

What stays simple for MVP

The current MVP should stay focused on the USDC invoice inbox flow on Arc Testnet: Create Invoice, Pay Invoice, Seller Console, and Circle Faucet / Setup. Keep the main UI centered on invoice records, receipts, and inbox clarity.