diff --git a/skills/agentic-payments/x402.md b/skills/agentic-payments/x402.md
index 81623e78..56f509d9 100644
--- a/skills/agentic-payments/x402.md
+++ b/skills/agentic-payments/x402.md
@@ -429,6 +429,20 @@ The checklist above assumes OZ Channels: it is the mainnet facilitator Stellar's
 - Symptom: `op_no_trust` during settlement, even though the client has USDC
 - Fix: the `payTo` account needs a USDC trustline too. The SAC `transfer` settles the underlying classic asset, which the recipient cannot hold without a trustline. Add `changeTrust` to both accounts during setup.
 
+**Self-hosted facilitator: mainnet settlement times out after verify passes**
+- Symptom: on `stellar:pubnet`, `/verify` returns valid but `/settle` never completes, and no transaction from the facilitator account reaches the ledger. The same setup works on testnet.
+- Cause: `ExactStellarScheme` from `@x402/stellar/exact/facilitator` bids `BASE_FEE` (100 stroops) as the inclusion fee on the settlement transaction and on the fee bump unless told otherwise. Mainnet Soroban transactions often need more to be included. Check the going rate with the RPC's `getFeeStats` (`sorobanInclusionFee`). See [x402-foundation/x402#3491](https://github.com/x402-foundation/x402/issues/3491).
+- Fix: set `inclusionFeeStroops` (available from 2.27.0). It sets the bid on both the settlement transaction and the fee bump:
+  ```js
+  new ExactStellarScheme([signer], {
+    inclusionFeeStroops: 1000, // size it from getFeeStats
+    maxTransactionFeeStroops: 50_000, // default; raise it if the bid needs headroom
+  });
+  ```
+  `/verify` adds the bid to the simulated resource fee and rejects the payment (`invalid_exact_stellar_payload_fee_exceeds_maximum`) if the total is over `maxTransactionFeeStroops`. A high bid can therefore need a higher ceiling.
+  From 2.19.0 through 2.26.0 the bid is fixed at 100 stroops. Upgrade, or pass a `feeBumpSigner` that rebuilds the fee bump with a higher base fee before signing.
+  Hosted facilitators set their own fees, so this only applies when you run `ExactStellarScheme` yourself.
+
 **Trying to sign auth entries from a browser**
 - Symptom: bundling errors, or a browser wallet that has no API to sign contract auth entries
 - Fix: run the x402 client server-side (e.g. an Express route the browser calls), or use Wallets-Kit / Freighter with custom auth-entry signing. `@x402/fetch` + `createEd25519Signer` target Node and assume a raw secret key.