Venly company primary sources — 2026-08-09

Project status in this pass

• This pass was for a taxonomy split: keep projects/venly.md on the product surface and add companies/venly.md for the named operator boundary.
• No standalone company whitepaper is the important artifact here.
• The decisive primary materials were the official homepage plus the docs pages that make Venly’s credentialing, identity, custody-mode, support, and payments workflow unusually explicit.

Primary-source snapshots

1) Homepage

• URL: https://www.venly.io/
• Key excerpt:
  • Venly now frames itself as Infrastructure for products and money movement.
  • The homepage separates Digital wallets, NFT API, Token API, and Venly Finance.
  • It says Venly Finance is Stablecoin payment infrastructure to collect, convert, hold, route and pay out globally.
  • It also foregrounds docs, SDKs, security posture, uptime claims, and integrations with products like Stripe, MoonPay, Transak, Shopify, Unity, Unreal, Beamable, PlayFab, and Zapier.

2) Docs introduction / what is Venly

• URL: https://docs.venly.io/docs/what-is-venly
• Key excerpt:
  • Venly describes itself as a complete developer platform for building on blockchain and simplifying digital-asset management.
  • The docs say the platform has three pillars: Digital Wallets, Digital Assets, and Payments.
  • The wallet section says Venly offers SSS-based wallets and two WaaS products: the Widget and the Wallet API.
  • The payments section still describes PAY as a low-code payment integration that can embed or host payment collection.

3) Wallet API vs Wallet Widget

• URL: https://docs.venly.io/docs/wallet-api-vs-wallet-widget
• Key excerpt:
  • The Wallet API is documented as a backend-to-backend integration using a clientId and secret, while the Widget uses a clientId linked to a whitelisted domain.
  • The page explicitly says Wallet-API calls are done in the customer’s name, while Widget users are known and authenticated at Venly and actions are done in the user’s name.
  • The comparison makes support workflow explicit too: API users contact the integrator first, while Widget users can contact Venly support directly.
  • The same page also makes the custody split explicit: Wallet-API integrations can be custodial or non-custodial depending on the customer’s setup, while the Widget is framed as non-custodial and requires user interaction plus PIN-based confirmation.

4) PAY API overview

• URL: https://docs.venly.io/docs/pay-api-overview
• Key excerpt:
  • PAY is described as a Venly-run onboarding and compliance shell around Stripe checkout creation for NFT-related payments.
  • The page says onboarding includes Venly’s own forms plus KYB review, and that acceptance is required before credentials are issued.
  • It publishes sandbox and production PAY API endpoints, which is useful evidence that the payment workflow is not just a marketing page but a credentialed operator surface.
  • Even though the homepage now emphasizes broader stablecoin and cross-border money movement, this older docs page is still valuable because it shows the company-shaped onboarding and payment-control pattern clearly.

Working conclusion

Venly clears the bar for a company/entity split because the useful question is not only what wallet, token, NFT, or payment features exist? but which named operator issues the credentials, whitelists the frontend origins, decides whether users are known directly to Venly, packages custody and support workflow, and runs the onboarding shell around payments and money movement? That is a company-layer control surface, not only a product description.