Skip to main content
If you’re already using another payment platform, you rarely rip-and-replace. Sly is additive for most of the common paths — you keep what works on the old stack and add Sly primitives where they fill real gaps (agent-native auth, multi-protocol routing, KYA verification, mandate flows).

​
Start here based on your current stack

From Stripe

You use Stripe Connect / Payments / Issuing. Sly adds agent-scoped wallets, KYA tiers, and multi-protocol agentic commerce (ACP, UCP, AP2, x402).

From Circle

You use Circle for USDC accounts + payouts. Sly adds the agent layer (Ed25519 auth, wallet policies, kill-switch) while you can keep Circle as an underlying rail.

From direct card networks

You integrated directly with Visa VIC or Mastercard Agent Pay. Sly abstracts both under one API + adds non-card rails (stablecoin, ACH, Pix).

Greenfield

No prior platform. Skip these guides — start with the quickstart.

​
What Sly adds that most platforms don’t

​
What Sly doesn’t try to replace

  • Card issuing / processing — partner with Stripe, Adyen, or Issuing providers; Sly sits in front
  • Merchant onboarding for cards — Stripe Connect is a better onboarding surface; Sly uses your Stripe Connect account via OAuth
  • Full-stack KYC providers — Persona handles KYC; Sly orchestrates but doesn’t replace them

​
Migration paths are usually additive

The fastest path for most partners:
  1. Keep your existing card processing (Stripe, Adyen) as-is
  2. Connect it to Sly via OAuth in your e-commerce or agent-commerce onboarding wizard
  3. Add Sly agent primitives (KYA tiers, wallet policies, Ed25519 auth) for your AI features
  4. Gradually migrate non-card rails (stablecoin, ACH, international) where Sly is cheaper or faster
You rarely rebuild your whole stack — you compose.

​
Two-way compatibility

Going forward: add Sly without removing your existing integration. Going back: Sly transfers are logged in your existing processor’s dashboard when using Stripe/Adyen/Circle as the underlying rail — audit trails stay in one place.

​
Common migration timeline

Full cutover is rarely the right move — some flows (card-only merchants, existing subscriptions) are better left alone until natural renewal.