Developer forum

Hi Mario

Yes, we have not tested that one. Talk to Nuno - he made this template.... In my world that template contains way too much code and should be @RenderEbizChargeScripts() only.

BR Nicolai

Gotcha! Will do. Thanks Nicolai

Hi Mario, I'll work with the Swift team on that. 

Hi Nicolai,

The excessive markup is because of checkout handlers that looks similar to this. The yellowish part represents the Swift checkout layout, which is the same on all other steps. The @RenderEbizChargeScripts() would represent the Purple area. That way, when checkout handlers provide that option, they still feel within the Checkout, rather than redirected out of it.

Hope that better describes the thought process and markup applied to a lot of the checkout handler templates (the ones that don't redirect the user completely).

// Nuno

Yeah, you are on your own here.

Inline payment gateways is a problem as your customer will need to be PCI compliant and probably also Dynamicweb. So we will not support it.

If you choose to, feel free.

BR Nicolai

Understood, but that's it's an iframe (not inline) just like Cybersource and ChargeLogic (and btw the Checkout handler was developed by EbizCharge themselves, not us).

But so that we are clear, the EbizCharge Checkout handler is part of DW9 (it's not "custom"), and the templates Mario mentioned are also part of Swift.

Unless there's some PCI compliance issue with using iframes that I'm not aware, this should be simple and non-risky to support. And if it is, then we should also consider other Checkout Handler to be removed and we/you don't set ourselves up for any potential issues.

// Nuno

Hi,

This is bugged with 17640.
It is the embedded mode that fails. Redirect mode works as intended.

Kind regards,
Merethe Vrå Andersen, QA