Payment does not appear in Electrum wallet - not sure why?

[NectarM]

We're using a bitcoin payment plugin in WordPress to receive BTC payments from customers.

We did a BTC test payment to make sure it's working ok.  The payment did come through to the xpub that we use to receive payments, but not into the electrum wallet.  The plugin support say that they do not receive the BTC on our behalf that it goes into the wallet.

The sending wallet has recorded the payment as being sent successfully - but it seems not to have arrived in the electrum wallet.

The plugin support have said we could increase the gap limit on the electrum wallet (https://help.blockonomics.co/support/solutions/articles/33000215760-gap-limit-faq) - is this worth doing and could it solve the issue? (seems a bit complex).

Can anyone help as to what the issue could be? Or if we're not understanding this correctly?

Thanks

[NeuroticFish]

The sending wallet has recorded the payment as being sent successfully

Then, if not a big issue, please post the tx ID and/or the sending address.
Based on that we can see what's the actual recipient address (on any public block explorer for Bitcoin).
And then we can check if the recipient address is part of the intended recipient wallet.
And also can check the fee, or if it was actually confirmed.

[NectarM]

Ok thanks, the txid is

aa691e3ed347136deef52d9264546654df20ca38869d23260835b4cc495d26fe

[hosseinimr93]

The default gap limit in Electrum is 20.
This means that Electrum stops looking at addresses once it reaches 20 consecutive unused addresses.
It's possible that many people have generated BTC addresses but haven't used them and caused Electrum to reach the gap limit before reaching that receiving address.
If that's the case, increasing the gap limit should solve the problem.

[BitMaxz]

Did you setup the blockonomics plugin properly with your Master public key from your Electrum?

If you didn't set it properly you won't receive any Bitcoins to your Electrum wallet.

I'm using Blocknomics plugin for a long time without any issue so maybe you didn't configure the plugin properly that's why you didn't receive it to your Electrum.

Gap limit only works if there are many used addresses that are not showing on the Electrum wallet.

Did you send it to xPub?
That look like this below?

Code:

xpub661MyMwAqRbcEYS8w7XLSVeEsBXy79zSzH1J8vCdxAZningWLdN3
zgtU6LBpB85b3D2yc8sfvZU521AAwdZafEz7mnzBBsz4wKY5e4cp9LB

So this is your address "13ZyV3ZNvG9DqwiYCpyP2hSv9ZHEM4RaUf" generated from Blockonomics?

Can you follow the guide from here "How can I tell if an address belongs to my wallet?"
If it shows false try to increase the gap limit to 50 or 100 then repeat the procedure above let's see if that address belongs to your wallet.

[bob123]

We're using a bitcoin payment plugin in WordPress to receive BTC payments from customers.

We did a BTC test payment to make sure it's working ok.  The payment did come through to the xpub that we use to receive payments, but not into the electrum wallet.

Could you please elaborate the bolded part?

How can you confirm that the payment came through to the xpub (you can't send coins to an xpub, only to addresses derived from it) but it didn't arrive in your wallet?
So, how can you be sure that it indeed went through to your address properly?

Did you use the correct master public key (xpub, ypub, zpub) of your wallet?
With what character do the addresses in your wallet start with (1.., 3.. or bc1..)?

[Abdussamad]

the amounts involved in that transaction are so small that it's possible you didn't notice it hitting your wallet. it's possible the sender has confused mbtc with btc.

if the transaction does not show up at all on the history tab then you should confirm that the address shows up in your wallet and that you are connected to an electrum server. for the former go to view menu > show addresses, switch to addresses tab and press ctrl+f to search for the address in question. for the former you should be seeing a balance in the bottom left and a green orb in the bottom right.

[NeuroticFish]

With what character do the addresses in your wallet start with (1.., 3.. or bc1..)?

This is imho the main question to answer to.
From the tx shown I think that OP is expecting to receive funds to a bc1* address, but they were sent to a legacy 1* address.
The derivation path is not as expected.

[NectarM]

Thanks for all the responses. In answer to some of them - the setup of the the payments was done by the plugin / plugin support - I just added the master public key and sent a BTC payment from Trust Wallet via the ecommerce cart.  I do believe the electrum address was a legacy address as the other one (begins with seg??) wasn't compatible with the plugin system. 

What I will do is send the url of this thread to the plugin support team, and ask them to advise. 

I think the last comment about the wrong derivation path could be the issue.

Thanks again.

[bob123]

Thanks for all the responses. In answer to some of them - the setup of the the payments was done by the plugin / plugin support - I just added the master public key and sent a BTC payment from Trust Wallet via the ecommerce cart.  I do believe the electrum address was a legacy address as the other one (begins with seg??) wasn't compatible with the plugin system. 

What I will do is send the url of this thread to the plugin support team, and ask them to advise. 

I think the last comment about the wrong derivation path could be the issue.

Well, you could just answer the questions here. There is probably no reason to contact any support team.

Your address definitely didn't start with "seg". It either starts with 1.., 3.. or bc1...
And depending on the generated address of your electrum wallet, you need to import different master public keys (xpub, ypub, zpub).

If you could tell us how your address start and how your master public key starts, we could tell you whether this is the issue.

[bL4nkcode]

If you input your xpub on blockonomics payment setup page then address should be legacy address that start with 1, ypub start with 3 and zpub start with bc1.

And that's true that blockonomics can't access your fund since xpub, ypub and zpub will only be used to generate payment address on your site.

Now, based on the txid, the payment address generated was a native segwit address, p2pf£d%t. And choose native segwit ..... when importing your seed, just make sure that you check the BPIP39 option, choose native segwit with derivation path of m/44'/0'/0'

[hosseinimr93]

Now, based on the txid, the payment address generated was a native segwit address,......

The receiving address is probably legacy.
There are two addresses in outputs of the transaction. One of them is legacy and another one is segwit
The segwit address in outputs of the transaction is probably the change address. Because that's same as the input.

[NectarM]

Ok will try to answer all questions myself here:

We're not using blockonomics, we're using Triple A plugin to receive payments.  We just provided the public address and were told it was set up successfully.

Because Triple A don't allow segwit we used a legacy address to receive (electrum).  It began xpub...

The sending address started with 1 (trust wallet)

If you need to know anything else please let me know.

Also should we disable the bitcoin payments on the website for now, as the BTC could be getting lost until we identify the issue?

Thanks

[hosseinimr93]

The sending address started with 1 (trust wallet)

If you are referring to the transaction you already posted, the sending address starts with bc1 not 1.

Did you try given suggestions?
Did you increase the gap limit? That's not difficult to do.
For increasing the gap limit you need to go to "console" tab. (If the "console" tab is not available, click on "View" at top of the window and select "Show Console".
In the console tab, you need to paste the code below.

Code:

[wallet.create_new_address(False) for i in range(50)]

Using this code Electrum will generate 50 addresses. You can change 50 to any other number.

[BitMaxz]

Ok will try to answer all questions myself here:

We're not using blockonomics, we're using Triple A plugin to receive payments.  We just provided the public address and were told it was set up successfully.

Because Triple A don't allow segwit we used a legacy address to receive (electrum).  It began xpub...

The sending address started with 1 (trust wallet)

If you need to know anything else please let me know.

Also should we disable the bitcoin payments on the website for now, as the BTC could be getting lost until we identify the issue?

Thanks

That's bad if it's not Blockonomics actually I never heard about Triple-A payment gateway. I just confused by your post above because you didn't mention the name of the plugin than posting the link of blockonomics gap limit.

Anyway, it seems it's not a legit payment gateway for Bitcoin most of the reviews from here "Triple A BTC Payment gateway" seems fake.

You're lucky that it's just a small amount I think it's better to remove that plugin and switch to any of these well-known payment gateways below that work on WordPress Woocommerce(Guide added).
- BTCpayserver - Guide on installing BTCpay plugin
- Blockonomics - The Easy Way To Accept Bitcoin On Your WordPress Site with Blockonomics

You can both try them with testnet so you don't need to worry about wasting your real Bitcoin for testing.

[bL4nkcode]

The receiving address is probably legacy.
There are two addresses in outputs of the transaction. One of them is legacy and another one is segwit
The segwit address in outputs of the transaction is probably the change address. Because that's same as the input.

Ah, yes, this is correct my bad.

Also should we disable the bitcoin payments on the website for now, as the BTC could be getting lost until we identify the issue?

Yes, you should, to avoid your funds getting lost.

Try the suggestions above, about the gap limit and..

Because Triple A don't allow segwit we used a legacy address to receive (electrum).  It began xpub...

You should avoid using bitcoin payment that don't accept segwit address if you're concern of your clients, its a pain in the ass paying higher fees in every transaction y'know.

[nc50lc]

For increasing the gap limit you need to go to "console" tab. (If the "console" tab is not available, click on "View" at top of the window and select "Show Console".
In the console tab, you need to paste the code below.

Code:

[wallet.create_new_address(False) for i in range(50)]

That will do, but take note that the said command will just generate 50 more addresses instead of increasing the wallet's gap limit.
After the last address was used, your wallet will only generate a number of addresses depending on the gap limit.

@NectarM To set the gap limit, use this command instead:

Code:

wallet.change_gap_limit(50)

Change '50' depending on your preference.

[TripleA Team]

Hi @NectarM , hi all who have been assisting

We are the TripleA team. We have been assisting via email and thought it best to share here as well given the generous help you all gave NectarM.

@NectarM,

We did a BTC test payment to make sure it's working ok.  The payment did come through to the xpub that we use to receive payments, but not into the electrum wallet.  The plugin support say that they do not receive the BTC on our behalf that it goes into the wallet.

We imported the master public key you provided, into Electrum. The colleague that did so did not mention having to change the gap limit.
The address which received the funds showed up right away (with the funds .
(screenshots shared via email, not sharing here to respect your privacy)

So both the electrum wallet (v4.0.3) and the blockchain explorer see you funds arriving on that address which belongs to your public key.
It could be that some of the options you choose when setting up the Electrum wallet changed the derivation path used to calculate the addresses.
We could share the screenshots of each step, let us know via email reply.

Because Triple A don't allow segwit we used a legacy address to receive (electrum).  It began xpub...

Please note that TripleA does support segwit wallets too. Public keys starting with xpub, ypub and zpub (and also tpub) are all supported. Not sure what gave you the impression that this was not supported.


@BitMaxz

Anyway, it seems it's not a legit payment gateway for Bitcoin

Hey now ;-)  It pays to be careful in the bitcoin space. We understand. But may I suggest reading our support section to see that we are an honest and sincere company working hard to earn the trust of our merchants.
We are headquartered in Singapore, regulated and are pending a license. We are 100% legit. We have 800+ happy merchants for our WooCommerce plugin. Is it so hard to believe that we would get positive reviews?
(It's an open question, feel free to open a new topic or reach out at support@triple-a.io ;-)

Regards,
TripleA Team

[Abdussamad]

If it's an electrum generated seed then the derivation path does not come into question. You don't get the option to change it at all as it's automatically set by the software. Besides if it was a different derivation path the xpub would also be different. So really the OP should just answer the questions above especially the ones i posed in post #7 about whether the address is in the wallet and whether the wallet is connected or not.