Bitcoin Forum
November 07, 2024, 08:35:51 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Rec ivied payment into wallet showing as unpaid  (Read 105 times)
mjch12000 (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
December 09, 2020, 01:56:08 PM
 #1

Bitcoin Client Software and Version Number: Electrum 4.0.6
Operating System:windows 10
System Hardware Specs:
Description of Problem:showing as unpaid in received payments screen
Any Related             Addresses:bitcoin:17vuGhKi7f3khhHeXaJysUr7Gwhkz2c4HD?amount=0.006623&time=1607512999
Any Related Transaction IDs:
Screenshot of the problem:
Log Files from the Bitcoin Client:

i generated a address to revive payment the address is showing correct on senders details
but my wallet is showing as unpaid in received screen and im not sure why it wont update in history careen and balance
Rath_
aka BitCryptex
Legendary
*
Offline Offline

Activity: 1876
Merit: 3139



View Profile
December 09, 2020, 02:00:15 PM
 #2

but my wallet is showing as unpaid in received screen and im not sure why it wont update in history careen and balance

Can you see a red/green dot or blue arrows in the bottom-right corner of Electrum? If you can't see a green dot then it's a connectivity problem; in such a case, try restarting Electrum; it should connect to a different server automatically.
nc50lc
Legendary
*
Offline Offline

Activity: 2590
Merit: 6344


Self-proclaimed Genius


View Profile
December 09, 2020, 02:00:35 PM
 #3

According to blockexplorers, there's a transaction received through that address: 17vuGhKi7f3khhHeXaJysUr7Gwhkz2c4HD
If Electrum is online, "Unpaid" status may have been a result of the received amount didn't matched your specified amount.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
mjch12000 (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
December 09, 2020, 02:13:37 PM
 #4

Thanks that sorted it thank you
o_e_l_e_o
In memoriam
Legendary
*
Offline Offline

Activity: 2268
Merit: 18746


View Profile
December 09, 2020, 11:08:49 PM
 #5

If Electrum is online, "Unpaid" status may have been a result of the received amount didn't matched your specified amount.
The issue here appears be the timing. OP has sent his request to expire at Unix time stamp 1607512999, which corresponds to 11:23:19 (UTC) on December 9th. The payment he received, which was for the specified amount of 0.006623, was not broadcast until 11:32 and not confirmed until 11:50, according to blockchain.com.

OP, the invoices you generate in this way are simply used by Electrum to track payments you have requested. If a payment is not paid within the time frame you specified, or pays less than you have requested, it will flag up as it did in your case here. That doesn't necessarily mean you have not received any payment though, and payments can still be made just fine after your request has expired.
nc50lc
Legendary
*
Offline Offline

Activity: 2590
Merit: 6344


Self-proclaimed Genius


View Profile
December 10, 2020, 02:36:19 AM
Merited by o_e_l_e_o (2)
 #6

If Electrum is online, "Unpaid" status may have been a result of the received amount didn't matched your specified amount.
The issue here appears be the timing. OP has sent his request to expire at Unix time stamp 1607512999, which corresponds to 11:23:19 (UTC) on December 9th. The payment he received, which was for the specified amount of 0.006623, was not broadcast until 11:32 and not confirmed until 11:50, according to blockchain.com.
He didn't set an expiration for the invoice, if there is, there should be a "&exp=86400" (in seconds) next to the one in the OP.
The unix timestamp "&time=1607512999" is the time when he created the invoice.

OP didn't clear what had "sorted" the issue, but I guess it's just a simple sync problem.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!