logo

New Response

« Return to the blog entry

You are replying to:

  1. If the "(WebProcessPayment)" agent fails in someway that you don't catch the @SetField won't get run.

    Having been down this road over the past 13 years with my eCommerce site, can I just state one thing which you really should make clear for the best security. The Credit Card info (and personal info) should NEVER be stored in the database which is used to run the website.

    That never as in don't save it, don't view it, don't edit it. Having talked at UKLUG on the subject of security of Domino sites, having a job in security, having had over £8.2 millon transactions through my sites and having hacked more than a few websites (in the white hat sense) you should never store the info even for an instant.

    Customer info is sacrosanct. It is the make or break of any business. Once it gets out you face more trouble than you know. Don't risk it.

    The trick here is to use you website as a pass through to a 2nd database where all the info is kept under lock and key and is encrypted to the hilt. Submit to an agent and let that handle the necessary workings. Never save to a document under any circumstances.

Your Comments

Name:
E-mail:
(optional)
Website:
(optional)
Comment: