Public preview
How the Embedded Components on-ramp works Public preview
Learn about the Embedded Components on-ramp.
Build an on-ramp flow native to your app or website with components that provide authentication and secure data collection, tailored to your design.
Customer flow
- A customer visits your app or website and wants to convert fiat to crypto or purchase crypto.
- Your app prompts them to onboard by signing up or logging in to Link .
- They sign up or log into Link without leaving your app or website.
- They grant your app permission to use their saved payment methods and wallets. If they’re missing required data (such as KYC information, payment methods or wallets) they complete account configuration in your app or website.
- They purchase or convert crypto in a CryptoOnramp session. Returning customers have the option for one-click checkout.
Features
| Merchant of record | When you use the onramp, Stripe acts as your merchant of record. A merchant of record is the legal entity responsible for facilitating the sale of products to a user. |
|---|---|
| The Stripe checkout infrastructure | Pre-populate transaction parameters (wallets, source and destination currencies, source and destination amounts, supported networks) Every session status change generates a webhook Returning users can check out faster with Link, the Stripe consumer account infrastructure |
| Customisation | Add real-time quotes, automated KYC and multi-chain support with minimal coding Implement using an embeddable widget, customisable to your brand |
| Disputes management | No platform fraud liability, Stripe handles all disputes. |
| Payment methods | Credit, debit, Apple Pay, Google Pay and ACH (US only). All of these payment methods are eligible for instant crypto delivery after KYC completion. American Express cards are only accepted in the EU. |
| Currencies | Available currencies are subject to change. the related setting (Solana) the related setting (Base) the related setting (Base) the related setting (Solana) the related setting (Ethereum) the related setting (Tempo) the related setting (Sui) the related setting.e (Tempo) the related setting (Ethereum) the related setting (Solana) USDsui (Sui) the related setting (Arbitrum) the related setting (World Chain) the related setting (Polygon) the related setting (Ethereum) the related setting (Celo) RipUSD (Solana) Phantom Cash (Solana) |
| Geographic availability | US and EU countries Not available in the state of New York. |
Integration overview
Choose how you want to get started with your integration, using one of the following:
- Quickstart : Provides minimal code that you can run to see the full flow and explore the integration.
- Integration guide : Provides step-by-step instructions for Web (JavaScript and React), React Native, Android and iOS apps.
Install the SDK
Install one of our Embedded Components Onramp SDK for Javascript, React Native, iOS or Android. You can customise the appearance (for example, colours and theme) so the minimal Stripe UI matches your app or website.
Authentication
A Link account is required to proceed with the on-ramp purchase flow. Your client checks for an existing Link account and registers the user if none exists. After sign-up or sign-in, your back end creates a LinkAuthIntent with on-ramp OAuth scopes and the client completes the consent flow. Your back end then calls the Stripe API to get an access token for all subsequent API requests.
Identity
The user must complete account setup before an on-ramp transaction. Your back end uses the Stripe APIs to check whether KYC and identity verification are complete. When something is missing, your client uses the SDK to collect KYC information, confirm existing KYC and complete identity verification before checkout.
Payment
The user needs at least one registered wallet and one payment token. You can design the flow in either of these ways: let the user choose which registered wallet to deposit to (for example, use the Stripe API to show a list of wallets), or abstract the wallet choice and always use a specific wallet (for example, the user’s primary or only wallet) so the user never sees or selects a destination.
For checkout, your back-end creates a CryptoOnrampSession with amount, currencies, network and wallet, then returns the session to the client. Your back-end calls the Stripe API to confirm and fulfil. When fulfilled, the client receives the session status and blockchain transaction ID.
Next steps
- Embedded Components onramp quickstart
- Integrate the Embedded Components on-ramp
- KYC tier system
- EU KYC integration guide
- Try our sample apps: iOS and Android