ecommerce recommendations and related topics
Netcheque
Developed at the Information Sciences Institute of the University of Southern California. Registered users may write checks to other registered users through e-mail or other network protocols. When the check is deposited, it authorizes the transfer of funds from the issuer's account to the receiver's account. All information is kept on a netcheque server, which is responsible for keeping accounts for customers, approving payments, and making the necessary changes in client accounts.
Security wise, Netcheque uses Kerberos for signature authentication, and it uses conventional cryptography, not public key cryptography.
cookie
A message given to a Web browser by a Web server. The browser stores the message in a text file. The message is then sent back to the server each time the browser requests a page from the server.
Also see session cookie and persistent cookie.
The main purpose of cookies is to identify users and possibly prepare customized Web pages for them. When you enter a Web site using cookies, you may be asked to fill out a form providing such information as your name and interests. This information is packaged into a cookie and sent to your Web browser which stores it for later use. The next time you go to the same Web site, your browser will send the cookie to the Web server. The server can use this information to present you with custom Web pages. So, for example, instead of seeing just a generic welcome page you might see a welcome page with your name on it.
The name cookie derives from UNIX objects called magic cookies. These are tokens that are attached to a user or program and change depending on the areas entered by the user or program.
Also see Do Cookies Compromise Security? in the Did You Know . . . ? section of Webopedia.
Anatomy of a Credit Card Transaction: The Basics
For a bigger understanding of a credit card transaction, the consequent is a
step-by-step breakdown: from the customer making a purchase using ECmerchant to
the merchant receiving an authorization on the value request. This not only
shows who is involved in this path , however it will highlight some considerations
in choosing an Internet value supply and establishing a merchant credit card
account.
Once the merchant account is in settle with an acquiring financial school
the merchant will desire to understand how money will be moved from the customers'
accounts to the merchant account. The best path to appreciate how an Internet
merchant gets paid is to follow a typical credit card transaction path . Fully
automated from end-to-end, in most cases it takes just seconds to entire.
1. A customer visits a web site, using average web browser software,
and fills her ECmerchant shopping cart.
2. The customer and ECmerchant exchange details online regarding
addresses, delivery and final value.
3. ECmerchant then displays the 'BUY' button to the customer, and a
transaction is initiated.
4. The customer clicks the 'BUY' button, prompting ECmerchant
to mail and electronic invoice.
5. ECmerchant provides transaction details in a form or the shopper's
browser automatically opens her online wallet, allowing her to select a value
instrument.
6. An encrypted charge value message is sent to ECmerchant.
7. When the server software receives the value message, it adds
merchant identification data.
8. The value request is encrypted and forwarded to gateway server
hosted by an ECommerce value supply corporation.
9. The gateway server decrypts the message and authenticates customers'
data and merchant validation.
10. A message is sent over secure, private financial networks to the
merchant's bank or authorized processor requesting charge approval.
11. Once the request is processed, a positive or negative response is
sent back to ECmerchant and on to the customer.
12. If the transaction is authorized, a digital receipt is delivered,
and the transaction is entire and captured.
