Take card payments inside your product
Run your Nevermined organization and drop a PCI-compliant iframe into your app so customers add a card and check out inline. Your org issues the widget keys; the raw card number never touches your servers.
One snippet. Card capture inside your own checkout.
Mount the widget where you collect payment. Your customer enters their card inline, it is tokenized inside a Nevermined-served iframe, and you get a payment method back, never a raw card number.
- Renders right inside your checkout
- Zero PCI scope: card data never touches your servers
- Tokenized by VGS, verified with 3DS or a passkey
Three flows, one integration
Mount what your product needs, where it needs it.
Card capture
Customers add a real card inline. Tokenized by VGS, verified with 3DS or a passkey.
Checkout
Take payment for a plan or a one-off inline, with the same session and iframe security model.
Saved cards
Let customers view and manage the cards on file, without you handling card data.
Your server is never in the card-data path
The card number only ever exists inside the Nevermined iframe and the VGS vault. Your code receives a token, never a PAN.
- The raw PAN lives only in the iframe and VGS, never your servers
- You stay at PCI SAQ-A scope: no card data to store or audit
- Your handler gets a token back: save it, charge it later, done
The organization behind the widgets
A widget key is issued by your org. Here is the rest of what the org runs.
Identity & access
Scoped widget keys with origin allowlists, role-based team seats, and every enrollment verified by 3DS or a FIDO2 passkey. You decide which domains, and which people, can transact.
Money movement
Settlement, Stripe Connect payouts, disputes, and refunds run through one billing surface, so reconciliation is a single ledger instead of five.
Visibility & control
A live customer list, webhook events, and revenue plus usage analytics broken down per plan, per agent, and per customer, with audit-ready logs.
How it works
From organization to a live, embedded checkout.
Create your org
Spin up an organization account, publish plans, and invite your team.
Generate a widget key
Create an organization widget key and set the origin allowlist.
Mint a session
Your backend exchanges the key secret for a short-lived session, server to server.
Mount the widget
Initialize the browser SDK with the session and mount capture or checkout into any container.
Organization tiers
Start on a personal account, upgrade when you are ready to scale.
Premium Org
Embedded payment widgets, auto-generated agent docs, customer list, webhooks, analytics, and multi-seat access. Everything to sell to agents out of the box.
Create an organizationEnterprise Org
Premium plus unlimited agents and plans, plus pilot, whitelist, and fee-waiver programmes for qualifying teams.
Talk to usWhere it fits
Part of the way you sell to and get paid by agents.
Frequently asked questions
Organizations and embedded payment widgets.
An organization is your merchant account. It holds your plans, agents, customers, and payouts in one place, with multi-seat team access, and it issues the widget keys you use to embed card capture and checkout. You publish what you sell, agents and customers pay for it, and the revenue settles to your org.
Run your org, embed the payments
Create an organization, generate a widget key, and embed card capture into your checkout.