Help - Payment page changes needed

[suncloth]

I am in the process of having our credit cards done automatically through Authorize.net. Now none of our payment options require credit card information as the payment page indicates (check/credit card provided separately/credit card entered into Authorize page). Is there a way to change the payment page so it does not have the credit card entry fields and the statement that they are required fields? It appears the customer will have to enter the data again when they go to the Authorize page anyway and the other methods of payment don't require it.

[cdicken]

Your best bet is probably to split the HTML table which contains the payment selection drop-down and the credit cad entry fields. To find this table, open Act_Order02.html and look for where it says:

NETQUOTEDEL:PAYMENTPROMPT000
NETQUOTEDEL:PAYMENTPROMPT001

In between these two lines, enter something like:

</table>
<br>
Credit Card Entry (if not using Authorize.Net)
<br>
<table border="0" width="CUSTOMVAR:ACTSTDWIDTH" cellspacing="2" cellpadding="3">

[suncloth]

Chris,
Thanks for the help! It worked to separate it into 2 tables and give instructions to the customer on when to fill in the lower table. I wish I would have done that a long time ago.
As I described earlier, I now want to eliminate those inputs from the website. Now that you pointed me to the right place, I deleted all of the lines between the "NETQUOTEDEL:PAYMENTPROMPTXXX" lines after the first one. It appears to work great except for a warning when I upload the page asking if I really want to do that since some variables are missing on that webpage due to the deletions. I ran some tests and it appears to work fine. Is there a reason I shouldn't do this?

[chrisbrown]

Don't remove the lines but comment them out thus:

<!-- original line -->

[BPJSURF]

I think you may want to review the Auth.net configuration documentation as You do not need to enter the feilds as described in your post. Actinic (when using Auth.net) will allow a user to select the Payment type (i.e Creditcard / auth.net) and will automatically bump your browser to the Auth.net secure page where the user only inputs the credit card and expiry date. all other data feilds are migrated to Auth.net by Actinic. There is no double entry. I would download the auth.net install doc from our website http://www.actinic.us/documentation.html and contact support if you need additional assistance setting up the payment processing using Auth.net.

Brian

[suncloth]

Brian,
I already have the document (thanks to your staff) and used it to setup my Authorize.Net account with Actinic Business. What I found was that on the os000001.pl page where you select payment method, it also had fields to fill in the credit card information (it even indicated that they were required to be filled in). That credit card information did not get passed to Authorize.Net. Everything else did get passed (except for the State which is not critical).
The customer would select "Authorize.Net", type their credit card information into the fields in Actinic, and then when they clicked on the "Next" button they would be taken to the Authorize.Net payment page. Unfortunately they would have to type their credit card info at that page again. I did not want the customer wondering about where their credit card information went the first time they typed it in so I identified a way to remove the credit card input fields in Actinic. If what I am describing is not the way it is setup to work, let me know.

[BPJSURF]

The credit card details should not be entered in the "actinic" checkout process. All customer data but the credit card and expiry date are entered in Actinic as default. Then the data is ported to the "secure" Authorize.net checkout page. The purpose of using Auth.net is
1) to clear the credit card and
2) to provide the secure checkout for the entry of the credit card.

As default the Auth.net integration works great I would see absolutly no reason to modify the perl script to send creditcards with the customer data.
Unless I am missing something, I really can not understand why you want to make such changes?

Brian

[suncloth]

All I am doing is removing the ability for the customer to enter the credit card information as you stated is the desire in your first sentence. All of the other information is being input in Actinic and passed to Authorize.Net (and working great).