Launch stablecoin accounts in your app, one release at a time.
For neobank and fintech product teams
With the Venly Finance API, your first release gives every user a USDC balance of their own. A personal IBAN, paying a friend and top-ups from their bank follow when your roadmap is ready for them, on your own screens.
Plan your launch with us
Read the documentation
The launch
Four releases, and the first user who signs up.
In this story, your team ships accounts first and adds one feature each release. Maria is the first user on launch day. Each release shows what changes for your users and what it needs before it can go live.
Plan
Choose what goes live first
You don’t have to use everything on day one. Accounts come first; the other three can follow in the order your users ask for: a personal IBAN when they want to fund their balance by bank transfer, payments between users when they want to pay each other, top-ups when you want a bank payment inside the app.
Release 1
Launch day: Maria signs up
Your first release is accounts. Maria is the first of 2,400 people who sign up on launch day. Each account opens at sign-up while the identity check runs: by the evening 2,180 are verified, 196 are still pending and 24 are rejected. Your app decides what pending and rejected users see; only the verification itself can clear someone.
Release 2
An IBAN for everyone already verified
When the IBAN release ships, you don’t start from zero: every verified user can be issued EUR receiving details of their own, the 2,180 from launch day included. The 196 still pending get theirs once they are verified. A SEPA transfer to a user’s IBAN arrives in their account as USDC.
How each deposit lands in the right user’s account
Release 3
Maria pays Mira at the market
The third release lets your users pay each other. A transfer needs a verified account, so your app shows the feature to verified users and tells the others what is missing. At a Saturday market Maria pays Mira, another user of the app, for a bowl, and both see the payment as it moves from sent to completed.
How Mira gets paid out as a marketplace seller
Release 4
Maria tops up from her bank
The fourth release adds a bank payment to the flow. Maria taps top up, authorizes the payment at her own bank on a hosted page, and the money converts into USDC in her account. That one page is hosted; every other screen stays yours.
Available assets, chains and routes depend on your configuration.
The objects and calls behind each release are on the Finance API page.
What each release uses in the Finance API
Before each release
What each release gives your users, and what it needs to go live
One row per release. Read it as a readiness list for your roadmap: what your users can do, what has to be in place first, and which screens are yours.
Release
Your users get
Ready when
Screens
Available assets, chains and routes depend on your configuration.
What your team does not have to build, in the Finance API
Launch-day checks
What do users see while their identity check is pending?
Your app decides. The account exists from sign-up and its verification status, pending, verified or rejected, is available to your app, so you can show a waiting screen, limit features or explain a rejection in your own words.
Can users who joined before a release get the new feature?
Yes. Receiving details are issued per account, so verified users who joined in an earlier release can be issued theirs in the same way as new users.
Which screens are ours?
All of them except the hosted bank-payment page used for top-ups.
Do we need our own KYC provider?
No. KYC and KYB verification is handled by Venly as part of the party creation flow.
How does pricing work?
Quotes are built per contract, from your product, use case, volume and rails. The pricing page shows what one contains.
Next step
Plan your first release with us
Bring your roadmap. The conversation starts from your first release and what each later one needs before it can go live.
- Your first release and its launch market
- The features your users ask for next
- Where you want your own screens and where a hosted page is fine
What to bring
Plan your launch with us
Read the documentation
Who can clear a user at sign-up
Only the verification can clear a user. Every user goes through KYC as their own customer record. Your app shows the pending state, and cannot mark a user as verified itself.
SOC 2 Type 2 certified. Our own licences are in flight and flows run on licensed partner rails today.