Bank transfer selected from checkout.fi.

User goes to payment portal, selects bank transfer, returns to customer page and gets message that payment has failed.

Comments

demoshane’s picture

Addition: Order doesn't get listed as waiting for payment. But at Checkout.fi it shows up as waiting for payment.

demoshane’s picture

One thing comes to mind. Checkout's order status 3 waiting for payment might not give correct return value for drupal so that order would get mapped as waiting for payment, instead it reports it as failed payment?

operinko’s picture

Status: Active » Needs review

Fixed in commit 69c48f2.

demoshane’s picture

While returning from Checkout, everything is fine except error:
Notice: Undefined index: payment_pending funktiossa uc_order_status_data() (rivi 1916 tiedostossa /sites/all/modules/ubercart/uc_order/uc_order.module).

Another thing is that bank transfer order gets status payment received (On view orders, if you open order, there it says payment pending) (even user has not paid it yet to checkout), this should set status to waiting for payment. Currently you can't trust order status if bank transfer is enabled. (Does drupal get message from checkout when user has paid bank transfer so that order status gets updated to payment received?)

operinko’s picture

Should be fixed in commit fb785fd.

The only way for us to get a message from Checkout.fi regarding delayed payments (such as a bank transfer) is polling them with the order at certain intervals (initial poll at next cron run, after that once per hour) and for that, we need a scheduler which wasn't a dependency before. Hence I hesitated adding a dependency to an already used module.

I added that functionality to the -dev branches for both drupal 6 and 7, but please note that due to adding a scheduled check for the delayed payments, job_scheduler is now a dependency.
(It shouldn't break anything if you don't have it installed when updating due to some checks, but it won't do any of the checking either).

operinko’s picture

Status: Needs review » Closed (fixed)

With no activity on this issue since I fixed it, I'm assuming the problem has gone away.
Open a new issue if this persists.