diff --git a/arbitrum-docs/launch-orbit-chain/02-configure-your-chain/advanced-configurations/03-aep-fee-router/03-calculate-aep-fees.mdx b/arbitrum-docs/launch-orbit-chain/02-configure-your-chain/advanced-configurations/03-aep-fee-router/03-calculate-aep-fees.mdx
index fb25944b62..256cec860c 100644
--- a/arbitrum-docs/launch-orbit-chain/02-configure-your-chain/advanced-configurations/03-aep-fee-router/03-calculate-aep-fees.mdx
+++ b/arbitrum-docs/launch-orbit-chain/02-configure-your-chain/advanced-configurations/03-aep-fee-router/03-calculate-aep-fees.mdx
@@ -98,6 +98,12 @@ Certain Orbit configurations and customizations require special handling of AEP
 
 If you are an L3 or higher chain with a custom gas token, your custom gas token contract might be deployed on L2. If this L2 is not an Arbitrum chain, then the L2 token can't be transferred via the AEP Fee Router, as this would first require bridging down to Ethereum (impossible for L2-based tokens). In this instance, we recommend your chain pay fees in `ETH` by manually sending fees to an `ETH`-configured routing system.
 
+If you've agreed with the Arbitrum Foundation to send your Custom Gas Token as payment you can use the following formula:
+
+```
+AEP_FEES = [ (L2BaseFee) + (L2SurplusFee) + (L1BaseFee * Daily_price_L1_to_L2_gas) + (L1SurplusFee * Daily_price_L1_to_L2_gas) - ((L1BaseFee * Daily_price_L1_to_L2_gas) + (AssertionCosts * Daily_price_L1_to_L2_gas) )] \* 0.1
+```
+
 ### Non-Ethereum L1
 
 If your Orbit chain is deployed on a non-Ethereum L1 (e.g., Solana, BNB Chain), your fees must be manually transferred to a Foundation-controlled address.