ActiveCheckout FAQ
 Previous Index  Next 
Section 5 - Differentiation
How is it different from Microsoft Passport?
| Comparison |
ActiveCheckout
SPA applet |
Microsoft Passport |
|
Transfer of personal information to merchant |
Fills in personal details at a merchant's website through the existing fields on the website |
Merchant sites which are Passport-enabled retrieve the customers information directly from the Passport service. |
|
Authentication Model |
Authenticates credit card transactions with participating credit card issuers |
Authenticates credit card transactions with .NET MyServices . Does not provide any authentication with credit card issuers. |
|
Data Storage |
Consumer's local machine |
Microsoft Servers |
|
Business Model |
Reduce fraud and chargeback for online purchases |
Single sign-on service to stimulate online shopping |
How is it different from the Yahoo Wallet? The Yahoo wallet only provides single-click purchasing within the Yahoo shopping network. It does not provide any realtime authentication with the cardholder's issuer.
How is it different from AOL Magic Carpet/Screen Name Service? AOL only provides single-click purchasing within the AOL shopping network. It does not provide any realtime authentication with the cardholder's issuer.
How is it different from PayPal? PayPal is an account-based system that lets anyone with an email address send and receive online payments using their credit card or bank account. ActiveCheckout is used to make authenticated payments with online merchants which accept online credit card transactions.
How is it different from Gator?
| Comparison |
ActiveCheckout
SPA applet |
eWallet |
| Size |
~200 kb |
~2.7 MB |
|
Form Filling |
Yes |
Yes |
|
Storage of passwords for different websites |
No |
Yes |
|
Advertising |
No |
Yes |
|
User Experience |
Only wakes up to assist in making online payments |
Provides pop-up advertising boxes whenever a customer is browsing the Internet |
|
Authentication Model |
Distributed authentication architecture supporting authentication of cards from multiple issuers within the same applet |
Does not provide authentication with a cardholder's issuer.
|
|
Business Model |
Reduce fraud and chargeback for online purchases |
Provide targeted advertising to online customers based upon their purchasing patterns. |
How is it different from Brodia?
| Comparison |
ActiveCheckout
SPA applet |
eWallet |
|
Form Filling |
Intelligent Form Population (IFP) which works on over 90% of existing websites |
Form-filling only worked on a limited number of profiled websites or websites which support the ECML standard |
|
Storage of passwords for different websites |
No |
Yes |
|
Advertising |
No |
Yes |
|
Data Storage |
Customer's local machine |
Brodia Servers |
|
User Experience |
Only wakes up to assist in making online payments |
Provides advertising whenever a customer is browsing the Internet |
|
Authentication Model |
Distributed authentication architecture supporting authentication of cards from multiple issuers within the same applet at SPA-enabled sites |
Issuer-centric authentication model. Brodia wallet issued by one issuer did not support authentication of cards from other issuers. |
|
Distribution Model |
Same applet can be distributed to all cardholders and in advance of their issuer deploying server-based software |
Individual issuer had to sign up to the Brodia managed service prior to issuing eWallets to cardholders |
|
Business Model |
Reduce fraud and chargeback for online purchases |
Stimulate online shopping to increase cardholder spending |
How is it different from the IBM Digital Wallet?
| Comparison |
ActiveCheckout
SPA applet |
eWallet |
|
Size |
~200 kb requiring |
~4.3 MB requiring |
|
Installation |
Automatic install into the cardholders browser |
Required the cardholder to run a setup.exe installation program |
|
Certificate |
Not required |
Required the cardholder to apply for a digital certificate from their issuers and install a digital certificate into their eWallet |
|
Form Filling |
Intelligent Form Population (IFP) which works on over 90% of existing websites |
Form-filling only worked on a limited number of websites which support ECML |
|
User Experience |
Simple and frictionless e.g. automatic wake-up, auto-detect forms etc. |
A full windows application with cumbersome operation |
|
Firewalls |
Designed to work with proxy servers |
Cardholders experienced difficulties behind corporate firewalls |
|
Authentication Model |
Distributed authentication architecture supporting authentication of cards from multiple issuers within the same applet at SPA-enabled sites |
Only provided authentication at sites which were SET enabled.
|
|
Distribution Model |
Same applet can be distributed to all cardholders and in advance of their issuer deploying server-based software |
Individual issuer had to implement SET prior to issuing certificates to cardholders |
| 
