A client using this module has pointed out this bug. Set transaction type to pre-auth and Ubercart records it as payment received, which is not correct. Payment is *not* received and the order should be "pending". That way, the store admin can go in, see the order and click the button to take payment from within the Drupal UI, rather than having to go to Sagepay to complete the transaction.

Does this make sense? Is it possible, given the data storage restrictions? I imagine there must be a way to send a confirmation to pre-authed transactions, without storing personal/card data?

Comments

hanoii’s picture

hanoii
Primary language Spanish
Location 🇦🇷UTC-3
commented
Title: When the transaction type is set to pre-auth, the transaction status is set to payment received » AUTHENTICATE: the transaction status is set to payment received instead of something more meaningful
Category: bug » task
Status: Active » Closed (works as designed)

Sorry I took this long to answer this, but....

Maybe the status is sent to payment received, but I think you can still authorize the card from the site's order admin. It's been a while since I tested this, but you should have an authorize button in your credit card form block of the when viewing the order from the store admin.

I think the reason why it's set to payment received is more related to the workflow ubercart does when processing any gateway rather than something I do. I might have to check whether something changed on D6, but for D5, I don't think there's another way around, but the functionality should be there.

I am flagging it as by design for now, as this is more an usability issue than a bug report, if you think otherwise or you can't seem to process the authorize orders please let me know.