Justin O'Brien

Hi,

After researching this we discovered that it’s due to an edge case that we didn’t expect to encounter in the wild. We made a change in our system to support USDC such that for all new accounts we generate unique ETH addresses sequentially for every charge but skip over the first ETH address. It happens that since your account was first created a few months ago, the ETH address we’ve generated is the first ETH address which happens to be the one we’re ignoring. So the payment has indeed gone through but our system is ignoring it.

We’re implementing a fix so that going forward this shouldn’t happen to users with older accounts. Note subsequent payments will work. You can also use the seed phrase to see that the payment has gone through by importing the seed phrase into MetaMask or Coinbase Wallet. I will also follow up once this fix has gone through which will show the payment in CBC.

Thanks,
Justin

Thanks! Looking into this now.

You mentioned funds being withdrawn but cryptocurrencies must be sent for a transaction to occur. In other words there is no way for ETH to be withdrawn from your wallet without your consent. If you’re able to send your ETH address it should be easy to check whether funds were withdrawn on a block explorer since all balance are public.

Hi,

Can you tell me what address you sent funds to?

The ETH address associated with the order was: 0xb00c1d91cdd9853ce620fa7

There do not appear to be any transactions on Etherscan at this time: https://etherscan.io/address/0xb00c1d91cdd9853ce620fa7

Also may I ask what you used to send the ETH?

Thanks,
Justin

Indeed blockchainpending is equivalent to seeing the transaction in the mempool (zero confirmations) and processing is when we’ve seen a sufficient number of confirmations (1 confirmation for BTC).

I can’t think of any potential caveats.

Hi,

We’re looking into a fix for this. Thanks for reporting!

Thanks,
Justin

Hi,

Are you still experiencing this issue? I believe this was fixed a version or two ago and can’t repro the issue.

Thanks,
Justin

Hi,

Would you be able to update to the latest version to see if the issue persists?

Thanks,
Justin

Hi,

We’re looking into a fix!

Thanks,
Justin

@whallify have you upgraded to version 1.1.2?

You’ll need to activate the plugin first before seeing it under the Payments tab. Hope this helps!

Hi,

This was fixed in the Github repo and we’ve updated this plugin with the latest changes! Hope this helps.

Thanks,
Justin