Aarón Bueno Villares
2016-09-09 17:41:04 UTC
I'm trying to add, to a website I'm developing, a payment method (Redsys; a
spanish virtual POS), to accept card payments. Of course, the most tricky
part is to manage the redirection (and, in the case of Redsys, an on-line
notification, which is an extra url to send payment details). So, the most
obvious way to do it is emulate what Wt currently does.
Reading the Wt implementation, I've seen two different approaches to manage
these redirections.
* Google OAuth: the redirection url is a static resource which redirects
to a private resource (which closes the windows)
* PayPalCheckoutExpress: the redirection url is just a private resource,
which closes the windows and trigger a JSignal.
Why Google OAuth uses two WResources? Is there any adventage? And why
triggering a JSignal from within javascript? Isn't it better to trigger a
signal from the resource itself?
Thank you very much in advance,
spanish virtual POS), to accept card payments. Of course, the most tricky
part is to manage the redirection (and, in the case of Redsys, an on-line
notification, which is an extra url to send payment details). So, the most
obvious way to do it is emulate what Wt currently does.
Reading the Wt implementation, I've seen two different approaches to manage
these redirections.
* Google OAuth: the redirection url is a static resource which redirects
to a private resource (which closes the windows)
* PayPalCheckoutExpress: the redirection url is just a private resource,
which closes the windows and trigger a JSignal.
Why Google OAuth uses two WResources? Is there any adventage? And why
triggering a JSignal from within javascript? Isn't it better to trigger a
signal from the resource itself?
Thank you very much in advance,