Skip to main content
Payment platforms need three things crypto rails rarely deliver: predictable settlement, multi-asset acceptance, and a compliance story. Eco’s vault model and dual-mode execution were designed around these constraints.

​
The pain you’re solving

  • Customers want to pay with the stablecoin they already hold; you only want to receive USDC on Polygon
  • Bridge failures in the middle of a payment flow create unrecoverable customer-service incidents
  • Invoice flows need a deterministic destination address with pre-programmed actions
  • Compliance team needs address screening and AML before funds settle

​
What Eco gives you

​
Patterns

​
Customer pays an invoice with any stable

Generate a Programmable Address per invoice, derived from (merchantAddress, invoiceId). Show the address to the customer. Customer transfers (or signs ERC-3009 for gasless). The address publishes an intent that delivers the merchant’s preferred stablecoin on the merchant’s preferred chain. → Recipe: Gasless USDC into Gateway

​
Refunds without operational risk

Eco’s refund path is permissionless and runs independently. If a payment fails to settle within the deadline, the refund service returns funds to the customer automatically. You don’t operate a refund service; you don’t hold customer funds.

​
End-to-end compliance

Route through Verified Liquidity (closed access), the permissioned fulfillment lane built on a KYB’d solver network with OFAC screening built in. Every user requesting a quote is KYC/AML/OFAC-screened, and every transfer produces a structured audit record. The flow is identical to Routes, with the participant set constrained to verified parties on both sides.

​
Get started

→ Programmable Addresses overview, the primary product for invoice and checkout flows