Product Types
Products (or sometimes referred to as Financial Products) represent the various types of Accounts that customers can create. When creating an account, you have to specify a Product Type and Asset Type. The combination of these two determines how the account works and features it supports.
We support 3 types of products today
All the products are supported by regulated entities, such as Layer2, banks, trusts, qualified custodians, money transmitters, licensed exchanges.
Crypto Deposit Products
Crypto Deposit products are used to hold, buy, sell, deposit, withdraw digital assets. All assets are held at qualified custody partners today such as banks, trusts. In fact the assets are traded directly from the custodial wallets with liqudiity partners.
While most qualified custodians operate more less the same way, there are slight variations in:
- blockchains/assets they support
- client types they can support.
We have 2 Crypto Deposit products today, with a 3rd one coming shortly:
-
DEPOSIT_ANCH_CRYPTO -
DEPOSIT_FORT_CRYPTO
We highly recommend that where possible that you spread your assets across various custodians. However, you can choose to spread assets across custodians or just keep it all in one.
NOTE: Sandbox will have both the Crypto Deposit Products enabled by default. As part of onboarding, we will guide you in deciding which one(s) make sense for your use cases.
Digital Asset Support
Production Environment
We support the following assets in our production environment, across the 2 deposit products. We are constantly adding new assets. Click here to learn more about assets.
| Assets | Asset ID | DEPOSIT_ANCH_CRYPTO |
DEPOSIT_FORT_CRYPTO |
|---|---|---|---|
| AAVE (ERC-20) | ETHEREUM_MAINNET_AAVE |
Yes | |
| APE (ERC-20) | ETHEREUM_MAINNET_APE |
Yes | |
| BAT (ERC-20) | ETHEREUM_MAINNET_BAT |
Yes | Yes |
| BTC | BITCOIN_MAINNET_BTC |
Yes | Yes |
| DAI (ERC-20) | ETHEREUM_MAINNET_DAI |
Yes | Yes |
| ETH | ETHEREUM_MAINNET_ETH |
Yes | Yes |
| MATIC (ERC-20) | ETHEREUM_MAINNET_MATIC |
Yes | Yes |
| MATIC (Polygon) | POLYGON_MAINNET_MATIC |
Yes | |
| SHIB (ERC-20) | ETHEREUM_MAINNET_SHIB |
Yes | |
| SOL | SOLANA_MAINNET_SOL |
Yes | Yes |
| USDC (ERC-20) | ETHEREUM_MAINNET_USDC |
Yes | Yes |
| USDC (Polygon) | POLYGON_MAINNET_USDC |
Yes | |
| USDP (ERC-20) | ETHEREUM_MAINNET_USDP |
Yes | |
| WBTC (ERC-20) | ETHEREUM_MAINNET_WBTC |
Yes | |
| WETH (ERC-20) | ETHEREUM_MAINNET_WETH |
Yes | |
| WETH (Polygon) | POLYGON_MAINNET_WETH |
Yes |
Sandbox Environment
Not all assets above have testnet support and as such as support in our Sandbox. Below is a list of assets supported in our sandbox, across the 2 Deposit Products.
NOTE: ERC-20 assets all work the same way. So, if you code for ETH (native) and USDC in sandbox, and you will be able to support any ERC-20 in production. Same is true for Polygon. If you code for MATIC (native) and USDC in sandbox, you can support any other Polygon asset in production.
| Assets | Testnet | Asset ID | DEPOSIT_ANCH_CRYPTO |
DEPOSIT_FORT_CRYPTO |
|---|---|---|---|---|
| BTC | Testnet | BITCOIN_TESTNET_BTC |
Yes | Yes |
| ETH | Goerli | ETHEREUM_GOERLI_ETH |
Yes | Yes |
| MATIC (Polygon) | Mumbai | POLYGON_MUMBAI_MATIC |
Yes | |
| SOL | Devnet | SOLANA_DEVNET_SOL |
Yes | Yes |
| USDC (ERC-20) | Goerli | ETHEREUM_GOERLI_USDC |
Yes | Yes |
| USDC (Polygon) | Mumbai | POLYGON_MUMBAI_USDC |
Yes |
Client Support
Layer2's money transmitter status, combined with the banking/trust charters of our partners allows us to support most clients segments across both crypto products. However there are some caveats when it comes to supporting non-accredited individual end users for unregulated fintechs.
| Customer Type | DEPOSIT_ANCH_CRYPTO |
DEPOSIT_FORT_CRYPTO |
|---|---|---|
| Unregulated with Corporate, Accredited End Users | Yes | Yes |
| Unregulated with non accredited individual end users | Yes (in some US states) | Yes |
| US Regulated Financial Institution | Yes | yes |
| Foreign Financial Institution | Yes | Yes |
| Institutional | Yes | Yes |
Supported Operations
Crypto Deposit Products support all the operations on our system.
| Operations | DEPOSIT_ANCH_CRYPTO |
DEPOSIT_FORT_CRYPTO |
|---|---|---|
| Deposit | Yes | Yes |
| Withdrawals | Yes (manual approval) | Yes (manual approval after limit) |
| Transfers | Yes, with DEPOSIT_ANCH_CRYPTO and PAYMENT_ANCH_CRYPTO accounts only of the same Asset ID |
Yes, with DEPOSIT_FORT_CRYPTO and PAYMENT_FORT_CRYPTO accounts only of the same Asset ID |
| Exchanges | Yes, with DEPOSIT_ANCH_FIAT accounts only |
Yes, with DEPOSIT_FORT_FIAT accounts only |
NOTE: To transfer between
DEPOSIT_ANCH_CRYPTO/PAYMENT_ANCH_CRYPTOandDEPOSIT_FORT_CRYPTO/PAYMENT_FORT_CRYPTOof the same Asset IDs, you have to do a Withdrawal.
Crypto Payments Products
Crypto payments products are used to generate invoices, deposit addresses, accept crypto payments from multiple payors into a single account and automatically attributed to the payor. The funds can then auto-traded into fiat and settled into a Fiat Deposit Account. The funds can also be auto-wired to am external counterparty.
All assets are held at qualified custody partners today such as banks, trusts. In fact the assets are traded directly from the custodial wallets with liqudiity partners.
While most qualified custodians operate more less the same way, there are slight variations in:
- blockchains/assets they support
- client types they can support.
We have 2 Crypto Payment products today, with a 3rd one coming shortly:
-
PAYMENT_ANCH_CRYPTO -
PAYMENT_FORT_CRYPTO
We highly recommend that where possible that you spread your payments across various custodians. However, you can choose to spread assets across custodians or just keep it all in one.
NOTE: Sandbox will have both the Crypto Payment Products enabled by default. As part of onboarding, we will guide you in deciding which one(s) make sense for your use cases.
Digital Asset Support
Production Environment
We support the following assets in our production environment, across the 2 payments products. We are constantly adding new assets. Click here to learn more about assets.
| Assets | Asset ID | PAYMENT_ANCH_CRYPTO |
PAYMENT_FORT_CRYPTO |
|---|---|---|---|
| AAVE (ERC-20) | ETHEREUM_MAINNET_AAVE |
Yes | |
| APE (ERC-20) | ETHEREUM_MAINNET_APE |
Yes | |
| BAT (ERC-20) | ETHEREUM_MAINNET_BAT |
Yes | Yes |
| BTC | BITCOIN_MAINNET_BTC |
Yes | Yes |
| DAI (ERC-20) | ETHEREUM_MAINNET_DAI |
Yes | Yes |
| ETH | ETHEREUM_MAINNET_ETH |
Yes | Yes |
| MATIC (ERC-20) | ETHEREUM_MAINNET_MATIC |
Yes | Yes |
| MATIC (Polygon) | POLYGON_MAINNET_MATIC |
Yes | |
| SHIB (ERC-20) | ETHEREUM_MAINNET_SHIB |
Yes | |
| SOL | SOLANA_MAINNET_SOL |
Yes | Yes |
| USDC (ERC-20) | ETHEREUM_MAINNET_USDC |
Yes | Yes |
| USDC (Polygon) | POLYGON_MAINNET_USDC |
Yes | |
| USDP (ERC-20) | ETHEREUM_MAINNET_USDP |
Yes | |
| WBTC (ERC-20) | ETHEREUM_MAINNET_WBTC |
Yes | |
| WETH (ERC-20) | ETHEREUM_MAINNET_WETH |
Yes | |
| WETH (Polygon) | POLYGON_MAINNET_WETH |
Yes |
Sandbox Environment
Not all assets have testnet support. Below is a list of supported assets in our sandbox.
NOTE: ERC-20 assets all work the same way. So, if you code with ETH (native) and USDC in sandbox, you will be able to support any ERC-20 in production. Same is true for Polygon. If you code with MATIC (native) and USDC in sandbox, you can support any other Polygon token in production.
| Assets | Testnet | Asset ID | PAYMENT_ANCH_CRYPTO |
PAYMENT_FORT_CRYPTO |
|---|---|---|---|---|
| BTC | Testnet | BITCOIN_TESTNET_BTC |
Yes | Yes |
| ETH | Goerli | ETHEREUM_GOERLI_ETH |
Yes | Yes |
| MATIC (Polygon) | Mumbai | POLYGON_MUMBAI_MATIC |
Yes | |
| SOL | Devnet | SOLANA_DEVNET_SOL |
Yes | Yes |
| USDC (ERC-20) | Goerli | ETHEREUM_GOERLI_USDC |
Yes | Yes |
| USDC (Polygon) | Mumbai | POLYGON_MUMBAI_USDC |
Yes |
Client Support
Layer2's money transmitter status, combined with the banking/trust charters of our partners allows us to support most clients segments across both crypto products. However there are some caveats when it comes to supporting non-accredited individual end users for unregulated fintechs.
| Customer Type | PAYMENT_ANCH_CRYPTO |
PAYMENT_FORT_CRYPTO |
|---|---|---|
| Unregulated with Corporate, Accredited End Users | Yes | Yes |
| Unregulated with non accredited individual end users | Yes (in some US states) | Yes |
| US Regulated Financial Institution | Yes | yes |
| Foreign Financial Institution | Yes | Yes |
| Institutional | Yes | Yes |
Supported Operations
Crypto Payments Products support the following operations
| Operations | PAYMENT_ANCH_CRYPTO |
PAYMENT_FORT_CRYPTO |
|---|---|---|
| Deposit | Yes | Yes |
| Transfers | Yes, with DEPOSIT_ANCH_CRYPTO and PAYMENT_ANCH_CRYPTO accounts only of the same Asset ID |
Yes, with DEPOSIT_FORT_CRYPTO and PAYMENT_FORT_CRYPTO accounts only of the same Asset ID |
| Exchanges | Yes, with DEPOSIT_ANCH_FIAT accounts only |
Yes, with DEPOSIT_FORT_FIAT accounts only |
Fiat Deposit Products
Fiat Deposit products are used to hold, deposit, withdraw fiat assets and exchange with crypto assets. All assets are held at banking partners and never comingled with Layer2's funds.
We have 2 Fiat Deposit products today, each offering slightly different capabilities, with 2 more coming shortly:
-
DEPOSIT_ANCH_FIAT -
DEPOSIT_FORT_FIAT
We highly recommend that where possible that you spread your fiat assets across various banks (products). However, you can choose to spread assets across custodians or just keep it all in one.
NOTE: Sandbox will have both the Fiat Deposit Products enabled by default. As part of onboarding, we will guide you in deciding which one(s) make sense for your use cases.
Fiat Asset Support
Production Environment
We support the following assets in our production environment, across the 2 fiat deposit products. We are adding new fiat assets, CAD coming shortly. Click here to learn more about assets.
| Assets | Asset ID | DEPOSIT_ANCH_FIAT |
DEPOSIT_FORT_FIAT |
|---|---|---|---|
| USD | FIAT_MAINNET_USD |
Yes | Yes |
Sandbox Environment
We support the following assets in our sandbox environment, across the 2 fiat deposit products. We are adding new fiat assets, CAD coming shortly. Click here to learn more about assets.
| Assets | Asset ID | DEPOSIT_ANCH_FIAT |
DEPOSIT_FORT_FIAT |
|---|---|---|---|
| USD | FIAT_TESTNET_USD |
Yes | Yes |
Client Support
Layer2's money transmitter status, combined with the banking/trust charters of our partners allows us to support most clients segments across both fiat deposit. However there are some caveats when it comes to supporting non-accredited individual end users for unregulated fintechs.
| Customer Type | DEPOSIT_ANCH_FIAT |
DEPOSIT_FORT_FIAT |
|---|---|---|
| Unregulated with Corporate, Accredited End Users | Yes | Yes |
| Unregulated with non accredited individual end users | Yes (in some US states) | Yes |
| US Regulated Financial Institution | Yes | yes |
| Foreign Financial Institution | Yes | Yes |
| Institutional | Yes | Yes |
Supported Operations
The biggest difference between the two deposit accounts
| Operations | DEPOSIT_ANCH_FIAT |
DEPOSIT_FORT_FIAT |
|---|---|---|
| Deposit via Fedwire | Yes | Yes |
| Deposit via ACH Push/Pull | Yes | |
| Deposit via SWIFT | Yes | Yes |
| Withdrawals via Fedwire | Yes | Yes |
| Withdrawals via ACH Push/Pull | Yes | |
| Withdrawals via SWIFT | Yes | Yes |
| Internal Transfers | Yes with DEPOSIT_ANCH_FIAT accounts |
Yes with DEPOSIT_FORT_FIAT accounts |
| Exchanges | Yes with DEPOSIT_ANCH_CRYPTO and PAYMENT_ANCH_CRYPTO accounts |
Yes with DEPOSIT_FORT_CRYPTO and PAYMENT_FORT_CRYPTO accounts |