After changing the gap limit from 20 to 30, I saw it appear in the address and history.
Take note that if the platform that you're using generated 31 or more unused address next time, you'll experience the same issue again.
So it's important to know that the "
gap limit" is what dictates Electrum to search for N number of unused addresses before giving-up to search.
For eCommerce Platform-connected wallet, it's recommended to set hundreds to a thousand gap limit, but read my important notes below:
-snip- Yes, I am using an eCommerce platform to sell products, and they automatically generate a BTC address for buyers. The funds are then sent directly to my Electrum wallet address.
There's also a very important note that you may want to consider: Once Electrum created thousands of addresses, it will start to fail to sync with almost all of the public Electrum servers.
Means that it'll not be able to check for transactions and update its balance once it generated a lot of addresses.
That can be workaround by setting-up your own Electrum Server that doesn't have a higher-limit for DDOS protection that a typical server has...
But once it generated tens of thousands of addresses, it might freeze its entire process entirely at some point.
(
at least your funds will still be safe with your seed phrase)
What I'm telling is: Electrum isn't the best wallet for that use-case if you're expecting to receive thousands of payments within the next few years.
Also, since the platform has to prevent re-issuing unused addresses when users do not proceed to send (
thus the issue in the default gap limit): that will even cause Electrum to generate more addresses than your expected amount of payments.
You may consider using Bitcoin Core for that, for starters, use
listdescriptors command to check one of your descriptor's extended public key (
xpub) that can be used in the platform.