protonscr

Unable to perform ideal payment in steam big picture

steamopen Big Picture
ValveSoftware/steam-for-linux#5078 · opened 2017-07-13 by ardje · updated 2019-07-18 · 1 comments · github
Aardje 2017-07-13 github

Your system information

  • steam beta 2017-07-11 and any version before that in big picture mode
  • Distribution (e.g. Ubuntu): steamos

Please describe your issue in as much detail as possible:

In big picture upon payment I can choose ideal.
Upon going to the third party payment provider on your side, the payment fails.
ideal-payment-failure

The obvious problem is that the third party payment provider needs the actual session and cookies made by the backend as arguments in the URI. There are no arguments in the URI :-(

I vaguely remember that ideal payment does work in steam client desktop mode. The website goes to the same third party provider and includes the needed arguments.

I think this bug also exists in the windows big picture version, but you can always use desktop mode on windows. You can't select desktop mode in big picture.

Note:
This is very different than #4684 which is probably related to that persons bank requiring specific things from the browser.

How to reproduce (except for 0 you can safely reproduce this):
0) usign a dutch account

  1. Select something to buy
  2. Select ideal as payment mode
  3. Select that you really live in the Netherlands
  4. Select go do the payment
  5. See the error.

Instead of the error the following should be displayed by the third party provider:
the amount, for who, a selection for the bank.
You can reproduce the working URL by buying using a browser. The moment you can select a bank is the thing that does not work in big picture, as that one doesn't send the session info.

Ideal payment goes like this:

  1. Your server creates a transaction with your third party payment provider
  2. Your server directs the browser to the third party payment provider with the transaction info
  3. The third party offers the browser a selection of banks on the ideal network
  4. The third party redirects the browser to the payment processor of the selected bank.
  5. selected bank does whatever it does to provide payment. Third party is notified using a back channel, but might require a redirect back to the third party.
  6. third party redirects browser back to server with a payment confirmed hash.
  7. server checks third party payment provider if that confirmation was legit.

Currently we are stuck at 2).

Aardje 2017-07-13 github

I think #4684 fails at 5), which is bank specific.

Nothing extracted yet.