Platform Integration
You own the experience. Your backend calls Gnosis Pay server-to-server. You keep your own authentication, user data, and onboarding flow.
Embedded Integration
Gnosis Pay runs the backend. Users sign in with their wallet, and Gnosis Pay handles sessions, identity, and onboarding. You ship the frontend.
Which one fits your product
One question decides it: Does your product already have a backend with its own user accounts?- Yes: use Platform Integration. You already have identity, sessions, and onboarding, so you add Gnosis Pay calls to the systems you have.
- No: if your product runs on wallets, private keys, or passkeys with no user database of its own, use Embedded Integration. Gnosis Pay provides the backend layer you don’t have.
The choice depends on your architecture, not your industry. A crypto company that runs its own backend and user accounts should use Platform Integration.
Comparison
What’s the same in both
Whichever path you choose, your users get the same underlying capabilities: KYC, accounts with on-chain balances, virtual and physical cards, card controls and limits, 3D Secure, secure card data and PIN flows, deposits, withdrawals, and statements. See Accounts and Cards for how these work.Start building
Platform Integration guide
Authenticate your backend, onboard users, and issue cards through the Partner API.
Embedded Integration guide
Add wallet sign-in and the ready-made onboarding flow through the User API.