Transak Docs
Searchโ€ฆ
Transak One
Transak One lets Transak Partner apps enable their users to on-ramp directly from fiat into an on-chain protocol in just one step.
This means users don't need to do multiple separate transactions or worry about the underlying blockchain complexity to use a dApp.
Integrating Transak One makes it even easier for DeFi, crypto games or any dApp using on-chain protocols to be accessible to mainstream users.
If your app could benefit from users directly on-ramping to a protocol and want to integrate Transak One please contact us: [email protected].

Overview

Quick demo

Transak One demo of integration with Cask protocol

Problem

Usually if a user wants to use a dApp they have to make five transactions:
  1. 1.
    Purchase the specific token required for the dApp with either fiat or another cryptocurrency
  2. 2.
    Purchase the native cryptocurrency with fiat to pay for transaction fees
  3. 3.
    Send both cryptocurrencies to their personal wallet
  4. 4.
    Trigger an approval transaction to give the dApp permission to use their tokens
  5. 5.
    Then, finally, interact with the dApp protocol using their wallet
Each of these steps requires technical understanding, takes time, and charges transaction fees. This complexity unfortunately makes a lot of dApps user unfriendly.

Solution

Transak One is a direct to protocol fiat on-ramp solution that hides the blockchain complexity from the user and combines all five transactions into just one step.
The user just needs to go through our quick and simple KYC one time, then each time they want to on-ramp to a supported dApp they only need to complete a payment using their preferred fiat payment method. Thatโ€™s it.
Behind the scenes we combine and perform all of the required transactions, transferring the crypto as well as initiating and interacting with the dApp protocol smart contracts on behalf of the user.
The user can then interact with the dApp via their wallet as normal, as if they had interacted with the smart contracts themselves.
Transak One can be integrated into any website or app for users to on-ramp directly to supported dApps.
We can add support for a new dApp on request. This is a straightforward process that can be done in just a few days, see Integration.

Use cases

Transak One direct to protocol on-ramp can improve the user experience of any dApp that requires users to deposit crypto with its protocol. Itโ€™s particularly helpful for dApps that are targeting mainstream users.
Some example use cases:
  1. 1.
    DeFi apps, for example where the user gets a return for providing liquidity or staking
  2. 2.
    Crypto games, for example where the user needs to first purchase and then send the in-game currency to a smart contract
  3. 3.
    NFT dApps, for example, a protocol that mints an NFT when you send it sufficient funds
  4. 4.
    DEXes, for example where the user can buy an NFT by paying the current price to the DEX
  5. 5.
    Protocols that convert or modify tokens, for example, to add additional functionality on top of common tokens
  6. 6.
    Almost anything you can think of!

Integration

If you would like us to integrate a protocol please reach out to our team.
Integrating a protocol for Transak One support is a straightforward process:
  • Each protocol needs to be reviewed by our team for technical validation and bespoke integration.
  • Transak One will be available for any supported EVM blockchain:
    • Ethereum
    • Polygon
    • Arbitrum
    • Optimism
    • Avalanche
  • The protocol transaction must use one of our supported cryptocurrenciesโ€‹
  • It is quicker to integrate a dApp if its smart contract protocol directly accepts deposits on behalf of another wallet address
    • To be precise, when the smart contract has a function that takes the userโ€™s wallet address, token amount, and (if required) the ERC-20 contract address, e.g. depositTo(userWalletAddress, tokenAmount, tokenAddress)
    • If this is the case we just need the smart contract address and deposit method name to perform the integration.
  • Protocols must also comply with our Acceptable Use Policy.
Copy link
On this page
Overview
Quick demo
Problem
Solution
Use cases
Integration