You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I might return as customer if you implement the displayPaymentEU hook.
Seems like you have only implemented the old approach: The displayPayment.
The problem is that some newer and more modern checkout pages only support the newer approach.
The displayPayment - the older approach - simply emits HTML code with all payment functionality into a page. And the expectation is that the page to be standard checkout page. This is very easy and convenient for developers, but it's very "hardcoded". It works on standard (or slightly modified) checkout page only.
The displayPaymentEU approach is a declarative approach. Instead of emitting HTML, the module describe what is needed to do in order to process payment. And it's responsibility of checkout page to display the HTML and call the payment functions when needed. This makes it very easy to switch between checkout pages.
Most payment modules implement both approaches. And it shouldn't be hard to implement.
Thanks in advance,
Elund
The text was updated successfully, but these errors were encountered:
Hello,
Good to hear that you have bought ePay back :-)
I might return as customer if you implement the displayPaymentEU hook.
Seems like you have only implemented the old approach: The displayPayment.
The problem is that some newer and more modern checkout pages only support the newer approach.
The displayPayment - the older approach - simply emits HTML code with all payment functionality into a page. And the expectation is that the page to be standard checkout page. This is very easy and convenient for developers, but it's very "hardcoded". It works on standard (or slightly modified) checkout page only.
The displayPaymentEU approach is a declarative approach. Instead of emitting HTML, the module describe what is needed to do in order to process payment. And it's responsibility of checkout page to display the HTML and call the payment functions when needed. This makes it very easy to switch between checkout pages.
Most payment modules implement both approaches. And it shouldn't be hard to implement.
Thanks in advance,
Elund
The text was updated successfully, but these errors were encountered: