Wert

• Name: Wert
• URL: https://wert.io/
• Category: embedded-ramp and smart-contract checkout operator / compliance-and-onboarding company / widget and webhook lifecycle company
• Tags: ethereum-ecosystem
• Summary: Wert belongs in companies/, not only projects/, because the durable dependency is a named company that onboards partners, issues sandbox and production credentials, signs agreements, whitelists live domains, provides API keys, controls smart-contract verification and key exchange for NFT checkout integrations, defines service availability by country and product mode, and acts as the source of dashboard and webhook truth for order and verification state. The useful question is not only can users buy crypto here? but which company controls the compliance, onboarding, domain-admission, and lifecycle surfaces the host app inherits by default?
• What it does:
  • Operates two main partner solutions — Fiat Onramp for card-based crypto purchases and NFT Checkout for smart-contract-driven purchases — while framing both as native-feeling embedded payments rather than obvious third-party redirects
  • Issues sandbox partner IDs and dashboard access during onboarding, then requires a signed agreement before granting production dashboard credentials and the live Partner ID used for go-live integrations
  • Controls live deployment posture through domain whitelisting, with the docs stating the production widget will not open unless Wert has approved the partner’s domains or subdomains
  • Provides the partner-facing control plane around session creation, API-key auth, dashboard-based module tuning, listeners / data APIs, webhook setup, and operational event logs
  • Extends the commercial relationship beyond a basic checkout widget by selling token-listing help, custom blockchain connectivity, priority support, custom dashboards, and feature reprioritisation
• Key claims:
  • The introduction docs say Wert offers two partner solutions — Fiat Onramp and NFT Checkout — both intended to integrate seamlessly into the partner product so users get a unified experience
  • The Fiat Onramp docs say integrations are session-based, authenticated with an X-Api-Key, and depend on API keys provided exclusively by Wert during onboarding; they also say sessionId values are valid for 30 seconds and single-use only
  • The Going Live docs say partners must contact Wert to sign an agreement and receive production Partner Dashboard credentials and a production Partner ID before launch
  • The same go-live docs say all production domains or subdomains must be shared with Wert for whitelisting and that the widget will not open for users if those domains are not approved
  • The Webhooks docs say partner endpoints must return 2xx within 5 seconds on all events, failed deliveries are retried on a fixed schedule, and repeated failure disables webhook delivery until manually re-enabled in Wert’s dashboard
  • The pricing / partner materials explicitly market bespoke token listing, custom blockchain connectivity, priority support, custom dashboards, and backlog reprioritisation, which makes the company boundary more important than a generic on-ramp SDK label
• Whitepaper: No classic standalone company whitepaper appears to matter here. The clearest primary materials are the current docs, partner-facing marketing pages, and go-live / webhook guidance; the broader source bundle remains ../whitepapers/wert-primary-sources-2026-04-27.md.
• Sources:
  • https://wert.io/
  • https://wert.io/for-partners
  • https://wert.io/pricing
  • https://docs.wert.io/docs/introduction
  • https://docs.wert.io/docs/integration-steps
  • https://docs.wert.io/docs/fiat-onramp
  • https://docs.wert.io/docs/going-live
  • https://docs.wert.io/docs/service-availability
  • https://docs.wert.io/docs/webhooks
  • https://docs.wert.io/llms.txt

Internal linkages

• Product-layer note: wert.
• Useful adjacent company reads: transak, moonpay, and crossmint.
• Routing-layer contrast above any single provider: onramper.

Protocol / company boundary

• wert is the product-layer note for the embedded widget, session-based checkout flow, smart-contract payment wrapper, and partner integration surface.
• This company note is the operator boundary: onboarding, agreement and credential issuance, production cutover, domain whitelisting, country / product availability, smart-contract-verification workflow, support routing, and dashboard / webhook truth all sit with Wert as a named company.
• That split matters because integrators do not only depend on a checkout component. They inherit a company-managed workflow spanning partner admission, compliance, launch approval, lifecycle events, and commercial escalation.

Control surface

• Practical leverage sits in sandbox-to-production admission, API-key issuance, session creation authority, domain whitelisting, supported-country and product coverage, NFT-checkout verification workflow, webhook delivery policy, dashboard-managed recovery, and the support / feature-prioritisation channel tied to named partners.

• The sticky dependency is operational memory: once an app hardens around Wert-issued credentials, approved domains, signed checkout flows, webhook event handling, and Wert-specific production procedures, the real lock-in is to the company-run onboarding and payment-operations shell rather than only to a widget.

• Read Wert as a company-operated partner onboarding and payment-control plane first, and as an embedded checkout product second.

• Last reviewed: 2026-08-09 UTC