blueedge

Has anyone used or installed X-Payments and the associated "connector" (http://addons.oscommerce.com/info/7510)?

It is my understanding that if an Oscommerce site directly accepts credit cards (not using a third-party payment site, such as PayPal), Trustwave will not deem the site to be PCI compliant. Has anyone had any experience with Trustwave PCI compliance using an OSC site that directly accepts credit cards?

However, it seems that an OSC site can be compliant if it uses X-Payments, since X-Payments is PA-DSS compliant and on Trustwave’s list of accepted credit card payment systems.

I anxiously await your thoughts and comments.

[This was originally posted in the wrong forum.]

I have Authorize.net Credit Card AIM installed as a payment method.

When an order is created, the site sends the customer the standard text version email summarizing the order. A second email is also sent to the customer. The second is an html version email that also summarizes the order. It must be trigger somewhere in the Authorize.net payment contribution because the email contains the Authorize.net transaction ID and it only happens with credit card orders.

At first, I thought that it was an Authorize.net developer's setting. However, when I switch it over to production with another account, it still produced the html version emails. Although I'm pretty sure that the setting have to be somewhere in OSC, I cannot find setting the the admin payment module for the email.

Since I think that it may be confusing for the customer to receive a text and html version of the order acknowledgement, how do I turn off the html order email that is trigger somewhere by Authorized.net?

Thanks.

I'm working on a new 2.2 site. For some reason, emails submitted from the Contact Us form are automatically misdirected to my junk email folder in Outlook.

On another, older site, the Contact Us emails are properly directed to my Outlook inbox. If I insert the email address from the old store into the configuration of the new store, thereby, using the old email address to receive emails from the Contact Us form on the new site, the Contact Us emails are still sent to the junk folder.

In addition, when emails are sent and received normally with Outlook using the new email address, the emails appear in the inbox.

This makes me think that there is something with the Contact Us code on the new site causing the incoming emails to be misdirected to the junk folder. Any suggests on how to get Contact Us emails from being misdirected to the junk folder?

I have Authorize.net Credit Card AIM installed as a payment method.

When an order is created, the site sends the customer the standard text version email summarizing the order.

A second email is also sent to the customer. The second is an html version email that also summarizes the order. It must be trigger somewhere in the Authorize.net payment contribution because the email contains the Authorize.net transaction ID and it only happens with credit card orders.

At first, I thought that it was an Authorize.net developer's setting. However, when I switch it over to production with another account, it still produced the html version emails. Although I'm pretty sure that the setting have to be somewhere in OSC, I cannot find setting the the admin payment module for the email.

Since I think that it may be confusing for the customer to receive a text and html version of the order acknowledgement, how do I turn off the html order email that is trigger somewhere by Authorized.net?

Thanks.