<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Accept JS Hosted Form Style in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Accept-JS-Hosted-Form-Style/m-p/67427#M40837</link>
    <description>&lt;P&gt;I created&amp;nbsp;a case in the idea exchange.&amp;nbsp; Please vote if this is something you are interested in.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.developer.authorize.net/t5/Ideas/Accept-JS-Hosted-Form-Style/idi-p/67426" target="_blank"&gt;https://community.developer.authorize.net/t5/Ideas/Accept-JS-Hosted-Form-Style/idi-p/67426&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 17 Apr 2019 15:19:28 GMT</pubDate>
    <dc:creator>CoryAuth</dc:creator>
    <dc:date>2019-04-17T15:19:28Z</dc:date>
    <item>
      <title>Accept JS Hosted Form Style</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Accept-JS-Hosted-Form-Style/m-p/67324#M40754</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have reviewed all documentation and it is apparent that there is no way to style the form in the Accept JS Hosted form.&amp;nbsp; In order to do so, we would need&amp;nbsp;to create our own form and submit it via JS.&amp;nbsp; Thus, opening us up to SAQ A-EP requirements;&amp;nbsp;which requires a lot more time investment to manage.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I also understand that SAQ A requires any vendor (Authorize)&amp;nbsp;offering CSS manipulation to verify all code submitted&amp;nbsp;for security.&amp;nbsp; There should be a way to do this programmatically, where only a subset of CSS would be processed, and the rest eaither ignored or appropriate errors raised.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Not allowing styling makes for a confusing experience for the end user.&amp;nbsp; They have spent a long period of time on our site choosing items to buy, only to end up on a page that looks nothing like what they were just on.&amp;nbsp; Even if it appears in a pop up, it is still a little unsettling to the user that they will be putting card data into something that looks so different.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It would be greatly appreciated if a method be could created to allow for the styling of the form.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has or is this being considered?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have seen a few other comments with regards to this, but there is no other detail than to create your own form.&amp;nbsp; There are other vendors offering this fetaure.&amp;nbsp; I would hope/expect&amp;nbsp;that Authorize.Net would offer it too.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I look forward to your response.&amp;nbsp; Thank!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Apr 2019 13:18:44 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Accept-JS-Hosted-Form-Style/m-p/67324#M40754</guid>
      <dc:creator>CoryAuth</dc:creator>
      <dc:date>2019-04-09T13:18:44Z</dc:date>
    </item>
    <item>
      <title>Re: Accept JS Hosted Form Style</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Accept-JS-Hosted-Form-Style/m-p/67427#M40837</link>
      <description>&lt;P&gt;I created&amp;nbsp;a case in the idea exchange.&amp;nbsp; Please vote if this is something you are interested in.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.developer.authorize.net/t5/Ideas/Accept-JS-Hosted-Form-Style/idi-p/67426" target="_blank"&gt;https://community.developer.authorize.net/t5/Ideas/Accept-JS-Hosted-Form-Style/idi-p/67426&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Apr 2019 15:19:28 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Accept-JS-Hosted-Form-Style/m-p/67427#M40837</guid>
      <dc:creator>CoryAuth</dc:creator>
      <dc:date>2019-04-17T15:19:28Z</dc:date>
    </item>
    <item>
      <title>Re: Accept JS Hosted Form Style</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Accept-JS-Hosted-Form-Style/m-p/94917#M58662</link>
      <description>&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;If the form is JS-hosted, the main thing that helped me was targeting the container after it renders and then applying custom CSS classes dynamically. Many hosted forms ignore external styles at first load, so using a small script to watch for DOM changes makes a big difference. I implemented something similar on the &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;Apricocia&lt;/SPAN&gt;&lt;/SPAN&gt; site, especially for contact and exchange request forms, to keep styling consistent with the store design. It improved usability a lot. Their setup might give you ideas&amp;nbsp;&lt;A class="" href="https://apricocia.com" target="_blank" rel="noopener"&gt;https://apricocia.com.&amp;nbsp;&lt;/A&gt;Keeping styles aligned with the main brand layout makes forms feel more trustworthy and seamless.&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Tue, 24 Feb 2026 11:03:49 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Accept-JS-Hosted-Form-Style/m-p/94917#M58662</guid>
      <dc:creator>samuelmixhle</dc:creator>
      <dc:date>2026-02-24T11:03:49Z</dc:date>
    </item>
  </channel>
</rss>

