Hello,
We've been using the SIM integration with hosted payment form for years and were able to use our own logo on the hosted payment form. Now that we're migrating from the old SIM integration to the new Accept Hosted (redirect method) payment form, I don't see any way to add a custom logo to the top of the form. Is this feature available with Accept Hosted like it was with SIM? If so, how can we add the logo?
If it's not available, this seems like a downgrade instead of an upgrade and will likely result in many unhappy clients on our end. We have thousands of clients that use this integration with our shopping cart system. Please advise.
โ03-16-2019 10:27 AM
Not available. Only option is to use an iframe. I have decided that for my current project I am going to implement an iframe. You have a mass market application, and most likely this involves some CMS features where your customer can change the appearance. Not sure how this will affect your implementation or if it is possible for you. If you do use it maybe we can figure out some things together. I'm having some quirky issues at the moment.
โ03-16-2019 10:56 AM
Thanks for the reply! That's a little disappointing. I assumed that this "new and improved" integration would be exactly that. You're correct that our clients are able to customize the look and feel of their cart system. With the SIM integration, we had them upload their logo to their Authorize.net interface and then they added the logo url to their Authnet integration settings in our application. We then sent that logo url over via the SIM interface and it worked well. Maybe this is something that I can add in a feature suggestion somewhere?
โ03-16-2019 11:02 AM
Yes it is, but it has been requested a million times. I've seen post after post where people do not like the limitations of the new form with the redirect method. I'd say auth.net is well aware of the issue at this point.
Depending on the level of customization you offer, it may be quite possible to implement the iframe. You will be sending out a new version of your application, with updated code? The issues you will have with the iframe will be if the customer has a lot of control over the width/height of the page where the payment takes place. It is possible that if they make the page too small, the entire form won't be visible.
It will likely take some additional tweaking for your needs, and there may be issues I haven't had yet. But if you load in an iframe the customer's logo will be right there like it is on other pages. I do consider this an upgrade, after working on both products. Accept Hosted is much easier to use and the added features to enhance transaction reporting are a real plus.
Aesthetically, the new hosted form is not as nice as the old one with the redirect method. But if you use an iframe the experience is enhanced big time. You can have the page outside of the iframe look however you want, and from the consumer's perspective there is no impression of ever being redirected. It is a seamless transaction on one website to them.
โ03-16-2019 12:10 PM
Techinically, the iframe method would help us get closer to the look and feel that we're looking for. But the reason why we can't do the iframe approach is because of the additional level of PCI compliance that it puts us and our clients in. So unfortunately, the hosted payment form redirect method is our only option at this point.
โ03-17-2019 12:24 PM
โ03-17-2019 03:04 PM - edited โ03-17-2019 03:15 PM
โ03-17-2019 03:05 PM
Thanks! For some reason, I thought embedding in an iframe automatically put you in the SAQ A-EP category. If that's not the case, that would be very good to know. I also remember reading something about iframes being bad for this particular use case, but I don't remember exactly what the reason was or where I read it.
โ03-17-2019 03:34 PM
โ03-17-2019 06:45 PM
โ03-17-2019 07:10 PM