The Authorize.net Accepted Hosted payment method has three issues on our site:
1- The name of the customer is NOT included in the records information that is saved to the backend admin.
2 - The popup to enter the credit card information is not PCI compliant and this should be entered at the Authorize.net website without any connection to our current site for security reason.
3 - The Grey NEXT Button and the blue NEXT buttons are confusing the users. Many are clicking on the blue next button at the bottom of the payment page and getting an error message. Change the language or make these separate pages.

I tried reverting to SIM payment method, which DOES go to Authorize.net's website for card entry, however, none of the customer's information is saved to the backend in the admin section. I am using the latest updates available across the board.

This is a nightmare since using the new JA Payment Plugin and my clients are at the point of abandoning this component and my services. We need answers and a solution to this NOW!!!!

Your changes have are now jeopardizing my reputation and my relationship with my clients and it needs to get resolved before I am hit with severe consequences.

I edited the main.css file as a temporary fix for the BLUE NEXT button by changing the background color and font color and also commenting out the rollover button to deactivate it totally so users would not be confused as follows:
location of the file is at: Component / templates / assets / css / main.css

.dtnav_buttons input[type="submit"] {
  color: #ffffff;
/* Hide this button background - Jim
  background-color: #428bca; 
 End here */
  background-color: #f5f5f5;
  border-color: #357ebd;
  display: inline-block;
  font-weight: normal;
  text-align: center;
  cursor: pointer;
  border: 1px solid transparent;
  white-space: nowrap;
  padding: 6px 12px;
  font-size: 14px;
  line-height: 1.42857143;
  border-radius: 0;
}
/* Hide this until a fix is made - Jim
.dtnav_buttons input[type="submit"]:hover {
  color: #ffffff;
  background-color: #3071a9;
  border-color: #285e8e;
}
End here */

    jstratos
    Hi,

    Could you share the admin username also? I see only the password now.

    And tell me the event that I can replicate the same issue, I will check it for you.

    Regards

      5 days later

      saguaros
      UN: I added it to the account info.
      All of the events - doesn't matter.

      I tried using the SIM payment method, however, nothing was being saved to the admin records section and the only user data they captured was from Authorize.net. So, they were missing all the fields record information in the backend. I prefer to use SIM method for PCI compliance but not in the current condition.

        Again, when using the SIM payment method, records are NOT saved in the backend admin section. Only captured in Authorize.net.

        When using the Accepted Hosted payment method, as you did, records ARE captured in the backend admin section, however, Authorize.net does NOT capture the customer's name.

        We prefer to use the SIM payment method for PCI compliance. Accepted Hosted is NOT PCI compliant.

          jstratos

          Hi,

          Last time, our developer tested with SIM method, let me ask him for further checking on this.

          I checked the test record by your developer and it was via ACCEPTED HOSTED . He needs to test using SIM and not during the daytime because he will cause problems with incoming reservations when he changes to SIM method during testing.

            jstratos
            Hi,

            I will inform him the same, he will add your own info back after testing.

            Regards

            8 days later

            Is there an answer on this? The University is screaming at me that this is not PCI compliant which is mandated. Come on people... please fix this so we can use the SIM payment method.

              jstratos
              Hi,

              To be frank, we're working hard on the new version so sorry for this lateness. Our developer is working on this, give us more time.

              Hi,

              Kindly check the latest record: Gurpreet Litt, it's from our developer test. It saves fine with SIM payment method.

              10 days later

              I see that a test conference was created and Gurpreet tested using SIM method and the records were saved. He used TEST MODE for Authorize.net.

              I ran another test myself, in LIVE MODE, just now using SIM Method and got an error message after trying to go to the payment process. Please retest and select the "UConn Center for Learning in Retirement: Spring 2019 conference" to see the error message. There is no relay response URL assigned in Authorize.net. Advise what that should be if one is still required.

                5 days later

                Okay, I am fine with this then. There is no need then to work on SIM method since this is the preferred method according to Auth.net.

                Accept Hosted. Accept Hosted, a mobile-optimized, PCI DSS SAQ-A compliant solution for accepting payments. Accept Hosted is a replacement for our legacy hosted payment form, SIM, and offers many advantages, including the freedom to accept payments while reducing PCI scope and development efforts. We encourage you to begin migrating to or using Accept Hosted immediately.

                SOURCE:
                https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Introducing-Accept-Hosted-a-Mobile-Optimized-Payment-Form/ba-p/57535

                  jstratos
                  Hi,

                  In this case, you can go to Pay options in DT Register component settings and select 'AuthorizeNet Accepted Hosted' method then.

                  Regards

                  Write a Reply...
                  You need to Login to view replies.