Hello,
First, my scenario:
Quantity
Product description
Product cost
Shipping cost
Taxes
Total cost
Billing:
Company
First name
Last name
Address line 1
Address line 2
City
State
Postal code
Country
Phone
Fax
Shipping:
Company
First name
Last name
Address line 1
Address line 2
City
State
Postal code
Country
Credit cart type (American Express, Discover, Master Card, VISA)
Credit card number
Expiration date (Month Year)
Security code
2) After the order form is filled out the user clicks the Submit Order button.
What I would like to happen when the user clicks the Submit Order button depends on what Authorize.Net has available, is able to do, and cost:
Assuming Authorize.Net can save all the above data at a reasonable cost:
I read in the Developer FAQs the following:
If you, or your merchant, do not have an SSL certificate, we recommend Direct Post Method (DPM). Direct Post Method uses a unique fingerprint to authenticate transactions, so developers customize a secure hosted payment form without needing an SSL certificate.
It is my understanding that we would not gather such information outside a SSL link, is this correct?
Is that form your form on your site?
Regards,
Robert
06-25-2011 01:36 PM
First off, I do not know if you will be able to use Silverlight with DPM. DPM requires an html form to submit data directly from the customer's browser to Authorize.Net. If this is not possible with Silverlight, then you will want to look into AIM.
As for storing the information, Authorize.Net will store all transaction details and most of that information will be available to you either programmatically through the Transaction Details or through the online merchant interface. Of the fields that you listed, the only fields not retrievable would be the Credit Card Number, Expiration Date, and the Security Code. The last 4 digits of the card number will be returned. The rest of the information is stored and retrievable for at least 2 years after the transaction has processed as long as your Authorize.Net account remains open.
It is also worth noting that if you were to go with option 2, this would dramatically increase the difficulty of being PCI compliant. It would also not be allowable for you to collect the customers Card Security Code, as this cannot be stored at any time.
07-05-2011 03:55 PM