Skip to main content
AiFinPay is multichain by design, but network inventory is not production readiness. A logo, contract address, historical transaction or merged source tree must not be presented as a live payment rail.

One economics model on every chain

Network gas is separate in both routes.

Readiness states

Current release boundary

  • Payment-live today: Polygon and Base, AIFP-1 on splitter v1.4, in native currency or USDC. The live list is the networks field of x402.json; it is built from the networks this backend serves and is the only place to check.
  • Other EVM networks with v1.4 deployments are deployed, not payment-live: the backend does not serve them yet, and a payment there would not earn a receipt.
  • Solana: disabled. The deployment registry marks Solana clusters settlement-enabled, but the backend does not serve Solana payments; the historical Solana Seat program is closed on mainnet and must not be paid.
  • Historical Polygon v1.1/v1.2 splitters are not canonical AIFP-1 or AIFP-2 payment routes (v1.2 remains only for the legacy B2B bridge).
  • NEAR, Aptos and Casper are not payment executors in the current clients.
  • AIFP-3 Agent Passport identity records are separate from AIFP-1/AIFP-2 settlement and do not make a chain payment-live.

Required release evidence

For each enabled chain publish the chain ID, canonical address/program ID, artifact version, runtime/code hash, on-chain profile, supported assets, audit commit, paid E2E transaction and activation date. If any field is missing, the route remains disabled. See Pricing, units and limits for the exact economic vectors.