Jump to:
| Project: | iDEAL Pro | Ubercart Payment |
| Version: | 6.x-2.3 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Issue Summary
Hello,
I just had a costumer paying, but there was a error suddenly?
Location https://www.domain.com/uc_ideal_pro/complete/14187?trxid=002000011160112...
Referrer https://www.abnamro.nl/nl/ideal/confirm.do
Message iDEAL payment status request error: SO1000: 'Failure in system - System generating error: acquirer' in /home/janton/domains/domain.com/public_html/sites/all/modules/uc_ideal_pro/ideal.inc:951
I checked the ABN payment system and i see that the payment was ok.
This user had a "open" iDEAL payment just before he tried it again i see this in ABN: 005 - Betalingsverzoek verlopen
(also in error log i see iDEAL payment failed: status: EXPIRED) but this expired state was trigger by cron after his second payment>the one with the error or bug.
It could be a couple of things:
1.) Perhaps a Open iDEAL payment and the iDEAL pending problem from the new ubercart causes this issue?
2.) Some strainge ABN bug or maybe a bug from my memcache
3.) A new Bug in this system:
"OPEN" state AND second try to pay before cron is run?
Comments
#1
I'm not completely sure, but it might be that the following is happening:
If a user confirms an order, the iDEAL transaction ID is saved and the user is redirected to the iDEAL page of his bank. If the user presses 'back' and re-confirms an order, it might be the case that a new, second transaction ID is generated which might not be properly saved to the database. When the user gets redirected back to your site at the end of the transaction, the module is then checking against the wrong iDEAL transaction (the first). This transaction will then still be 'open' and only expires after a timeout (detected by a cron run).
Do you see any (database) errors in the logs?
#2
Unfortunately i don't see any other errors in the log.
Yes it could be possible what you say, but i'm not 100% sure what the user did.. because i see his first (open)payment and then 50 minutes later he tried again.. but he did a login before that (because anonymous checkout is also possible) So i think it's unlikly he remained on the same page (because he first need to login)
The link is correct, and i checked the database that also contains the correct transaction ID(trxid)
https://www.domain.com/uc_ideal_pro/complete/14187?trxid=002000011160112...
I only don't know what about that second ec=3746af2c814c2b3308b355cc59a5e5f490f761f5
I even see status SUCCESS in uc_payment_ideal database
#3
The ec=… is the bank/transaction checksum.
I'm really not sure what happened, and without a probable explanation I can't really tell if there's a problem in the module or somewhere else.
#4
I just some tests and found this issue happends when somebody tries to pay with ABNAMRO but used Chrome for his browser...(chrome and ABNAMRO conflict..)
After cron is run i see this error in my log:
Message iDEAL payment status request error: SO1000: 'Failure in system - System generating error: acquirer' in /home/janton/domains/domain.com/public_html/sites/all/modules/uc_ideal_pro/ideal.inc:951
More a issue with ABNAMRO and Chrome, but ok good to know!