ecommerce recommendations and related topics
Transaction Authority Markup Language
Shortened as XAML. XAML is a vendor-neutral standard developed jointly by Bowstreet, Hewlett-Packard, IBM, Oracle and Sun that is used to coordinate and process online business transactions. Based on XML, XAML uses a set of XML message formats and interaction models that Web services can use to provide business-level transactions that span multiple parties across the Internet.
XAML distinguishes traditional online transaction processing (OLTP), such as making banking transactions online or purchasing a product from a consumer Web site, from business Web transaction processing (BWTP), which involves Web services from multiple organizations on the Internet and must coordinate the low-level operations of commit, cancel, retry, and compensate (undo or reverse) in order to ensure business-level transaction integrity.
The following example illustrates a business-level transaction involving a set of Web services that would utilize XAML: Consider a lumber company that needs to purchase a large quantity of a chemical it uses to treat its lumber before it is sold. In order for the buyer to purchase the chemical, the company requires additional value-added services provided by third parties, such as shipping with specific delivery terms, government compliance for safe transport, payment financing and casualty insurance. The purchase cannot take place until all these services are coordinated and the buyer is satisfied. XAML will allow the different parties involved to process the transactions over the Web.
page impression
The exact number of times a specific Web site has been accessed or viewed by a user. A page impression acts as a counter for Web pages, informing site owners how many times their sites were visited. Page impressions are also referred to as hits.
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.
