Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions integration/referral.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,8 @@ Each bridging method within the Mayan protocol has its own referral fee behavior
**Fee Collection**

- Fees are collected on the **source chain** once the bridge is successfully completed.
- Fees are collected in the fee manager contract and can be withdrawn using this tool:\
[https://explorer.mayan.finance/withdraw-fee-swift](https://explorer.mayan.finance/withdraw-fee-swift)
- Collected via the **locked assets** (e.g., USDC, ETH).

**Fee Rate**
Expand Down Expand Up @@ -99,7 +101,7 @@ Each bridging method within the Mayan protocol has its own referral fee behavior

You must prepare a referral address for each VM type:

```
```text
const referrerAddresses = {
solana: 'VALID_SOLANA_WALLET_ADDRESS',
evm: 'VALID_EVM_WALLET_ADDRESS',
Expand All @@ -113,7 +115,7 @@ const referrerAddresses = {
- Set your desired referral fee (in bps) as `"referrerBps"`.
- **Note:** Always use the Solana address as your referrer, regardless of source or destination chain (even for EVM → EVM routes).

```
```text
const quote = await fetchQuote({
...
referrer: referrerAddresses.solana,
Expand All @@ -126,7 +128,7 @@ const quote = await fetchQuote({

All transaction or bridge functions in the SDK accept an optional `referrerAddresses` parameter:

```
```text
type ReferrerAddresses = {
solana: string;
evm: string;
Expand Down