[Portal] Feature: Bridge page

apps/portal/src/app/bridge/faq/page.mdx

@@ -0,0 +1,135 @@
+import { createMetadata, Details } from "@doc";
+
+export const metadata = createMetadata({
+  image: {
+    title: "Bridge FAQs",
+    icon: "payments",
+  },
+  title: "Bridge FAQs | thirdweb documentation",
+  description: "Explore FAQs around bridging and swapping assets with thirdweb.",
+});
+
+# Payments FAQs
+
+### General
+
+<Details summary="What does Bridge use to operate under the hood?"> 
+Bridge is an asset router that combines thirdweb's own onchain infrastructure with existing bridging and swapping protocols to find the optimal route for any given transaction. 
+This can include intents, native bridges, third party bridges, cross-chain messaging protocols, thirdweb's custom bridges, and more. All routes are monitored and planned continuously for 
+health, price, and speed to guarantee the best path every time. 
+</Details>
+
+<Details summary="Am I able to use Bridge with other wallet infrastructure providers?"> 
+Yes, Bridge is designed to be agnostic to wallet infrastructure. You can use it with any wallet service. 
+</Details>
+
+### Fees
+
+<Details summary="What are the fees for Buy With Fiat?"> 
+thirdweb does not charge any fees for buy with fiat. Any fees on onramping are based on the onramp provider. 
+</Details>
+
+<Details summary="What are the fees for Buy With Crypto?"> 
+For buying with crypto or swap fees, thirdweb charges a 0.3% protocol fee. Developers may monetize their application by charging additional fees on swap transactions. To set a fee in your project page, navigate to Payments > Settings to set this fee. 
+</Details>
+
+<Details summary="What does the term “network fees” refer to?"> 
+Network fees, also referred to as miner fees, are paid to the miner for processing crypto transactions and securing the respective network. These fees do not go to thirdweb.
+</Details>
+
+<Details summary="Does thirdweb offer fiat payouts?"> 
+Fiat payouts are not currently available.
+</Details>
+
+### Token & Region Support
+
+<Details summary="How can I support a token?"> 
+We're able to support most tokens that meet the following criteria:
+
+- The token must have sufficient liquidity
+- The token must be on a [supported Payments Chain](https://thirdweb.com/chainlist?service=pay).
+
+To request support for a token, please visit the Payments tab in your project dashboard > Settings > "Don't see your token listed?" component and fill out the chain and token address information.
+
+The service will automatically kick off the token route discovery process. Please check back the Payments modal after 20-40 minutes for the requested token. 
+</Details>
+
+<Details summary="What countries does Buy With Fiat support?"> 
+**Buy With Fiat** is available 160+ countries. The following countries are _UNSUPPORTED_:
+
+- Afghanistan
+- Africa (All Countries)
+- Belarus
+- Bolivia
+- China
+- Cuba
+- Colombia
+- Haiti
+- Honduras
+- Iran
+- Iraq
+- Latvia
+- Lebanon
+- Myanmar
+- Pakistan
+- Qatar
+- Russia
+- Ukraine
+- United Arab Emirates
+- Venezuela
+- Yemen
+
+All United States are supported, excluding Hawaii.
+</Details>
+
+<Details summary="What cryptocurrencies does Bridge support?"> 
+Bridge can support any currency on our [supported chains](https://thirdweb.com/chainlist?service=pay).
+</Details>
+
+<Details summary="Does Bridge support Apple Pay or Google Pay?"> 
+Apple Pay and Google Pay are supported through the onramp providers depending on region. Coinbase, Stripe, and Transak currently support Apple Pay. Transak supports Google Pay.
+</Details>
+
+<Details summary="What are your transaction limits for Buy With Fiat?"> 
+We currently require a $1 minimum purchase for both stablecoin and non-stablecoin purchases through Buy With Fiat.
+
+Our transaction maximum starts from $1500 per week for new users and can increase over time to $10,000 per week.
+</Details>
+
+<Details summary="Does thirdweb offer direct onramping to tokens through Buy With Fiat?"> 
+We offer direct onramping **internationally** to the following tokens:
+
+- Mainnet (Ethereum)
+- Avalanche
+- Polygon
+
+We offer direct onramping to the following tokens in the **US only**:
+
+- ETH (Base)\*
+- USDC (Ethereum)
+- USDC (Polygon)\*
+- USDC (Avalanche)\*
+- USDC (Base)\*
+
+All other tokens will require an additional Buy With Crypto step.
+
+\* Not available in New York or the EU.
+</Details>
+
+<Details summary="How are cryptocurrency prices set in thirdweb Payments?"> 
+Prices are set depending on the liquidity provider used to route your transaction.
+</Details>
+
+### KYC & Compliance
+
+<Details summary="What are the KYC requirements?">
+Onramp options all require minimal KYC. This is done to comply with local regulations and to ensure the safety of our users.
+Please note: onramping with Coinbase does not require KYC for a purchase below $500 with debit card. 
+</Details>
+
+<Details summary="How does KYC work with Buy With Fiat"> 
+Users will be required to complete KYC verification for their first purchase using 'Buy with Fiat.' After that, no further KYC will be needed for future purchases on the same platform.
+</Details>
+
+
+

apps/portal/src/app/bridge/fees/page.mdx

@@ -0,0 +1,55 @@
+import { DocImage } from "@doc";
+import FeeShare from './assets/fee-dash.png';
+
+
+# Understanding fees
+
+Understand how protocol, developer, and onramp fees work with Bridge. 
+
+### Developer Fee
+
+To monetize applications or games, you are able to set a developer fee on each crypto-to-crypto or swap transaction. You may set this percentage
+through Project > Project Settings > Payments > Configure > Settings.
+
+<DocImage src={FeeShare} alt="Developer fee share" />
+
+### Protocol Fee
+
+Our protocol fee is a flat 30 basis points (0.30%) applied on the source token amount.
+This fee is independent of network gas fees and does not fluctuate.
+
+#### Setting fees using buy or sell
+
+You can configure who pays the protocol fee for buy or sell transactions by specifying the input amount `sell` or `buy`.
+
+See full reference for [`buy`](https://portal.thirdweb.com/references/typescript/v5/buy/prepare) and [`sell`](https://portal.thirdweb.com/references/typescript/v5/sell/prepare). 
+
+#### Setting fees on transfers or purchase mode
+
+You can configure who pays the protocol fee for transfers or purchase mode using the `feePayer` setting. This affects the 
+total amount paid by the user and the amount received by the destination (e.g., a seller, app, or partner).
+
+feePayer=buyer (Default) i.e. the user covers the protocol fee.
+
+Example: If the source token is 10 USDC, the user pays 10.30 USDC.
+
+- thirdweb receives: 0.30 USDC
+
+- Receiver receives: 10.00 USDC
+
+feePayer=receiver i.e. the receiver covers the protocol fee.
+
+Example: The user pays 10.00 USDC.
+
+- thirdweb receives: 0.30 USDC
+
+- Receiver receives: 9.70 USDC
+
+[See full reference.](https://bridge.thirdweb.com/reference#tag/transfer/POST/v1/transfer/prepare)
+
+### Onramp Fee
+
+A fee is charged by the third-party provider when onramping. This fee is determined by the provider and is typically a percentage 
+of the amount being onramped. This fee may vary based on the provider and payment method used.
+
+There are no protocol fees on onramp transactions. 

apps/portal/src/app/bridge/layout.tsx

@@ -0,0 +1,20 @@
+import { createMetadata } from "@doc";
+import { DocLayout } from "@/components/Layouts/DocLayout";
+import { sidebar } from "./sidebar";
+
+export default async function Layout(props: { children: React.ReactNode }) {
+  return (
+    <DocLayout editPageButton={true} sideBar={sidebar}>
+      {props.children}
+    </DocLayout>
+  );
+}
+
+export const metadata = createMetadata({
+  description: "Bridge and swap tokens across chains with thirdweb Bridge.",
+  image: {
+    icon: "payments",
+    title: "thirdweb Bridge Docs",
+  },
+  title: "thirdweb Bridge Documentation",
+});

apps/portal/src/app/bridge/onramp-providers/page.mdx

@@ -0,0 +1,40 @@
+import { createMetadata } from "@doc";
+
+export const metadata = createMetadata({
+	image: {
+		title: "thirdweb Payments - Onramp Providers",
+		icon: "thirdweb",
+	},
+	title: "thirdweb Payments - Onramp Providers | thirdweb",
+	description:
+		"Integrate onramp providers for any onchain transaction and set preferred providers",
+});
+
+# Onramp Providers
+
+**Onramp Providers** are services that allow users to buy crypto with fiat. Payments supports the following onramp providers:
+
+- **Coinbase**
+- **Transak**
+- **Stripe**
+
+## Provider Fees
+
+Each provider has different fees associated with their services which often depend on various factors. Onramp provider fees are set by the provider and are not controlled by thirdweb.
+
+| Provider | Fees |
+| -------- | ---- |
+| Coinbase | [Learn more about Coinbase Fees](https://help.coinbase.com/en/coinbase/trading-and-funding/pricing-and-fees/fees) |
+| Transak  |  [Learn more about Transak Fees](https://support.transak.com/en/articles/7845942-how-does-transak-calculate-prices-and-fees)|
+| Stripe | [Learn more about Stripe Fees](https://stripe.com/legal/crypto-onramp). |
+
+
+## Provider Regions
+
+Each provider has different regions they support. You can learn more about the supported regions for each provider in the links below.
+
+| Provider | Regions |
+| -------- | ------- |
+| Coinbase | [View Regions](https://docs.cdp.coinbase.com/onramp/docs/api-configurations) |
+| Transak  | [View Regions](https://transak.com/global-coverage) |
+| Stripe  | [View Regions](https://support.stripe.com/questions/crypto-supportability-and-availability-by-region) |