Tomas,
> You are obviously privy to information reserved for Visa/Mastercard
> partners ? Does this mean that in order to develop software for the next
> generation of SET, one must sign non-disclosure agreements ? I'm happy
> to do so if that's what is required.
I just told VISA I was very interested and landed on somebody's CC-list....
> (Please can someone tell me what I have to do to attain sufficient
> understanding to be able to start designing software. I have all the SET
> 1.0 documents.)
I think you should forget the 1.0 documents as the changes introduced are
rather large. I guess your intention is to produce Merchant-side SW?
BTW, this time VISA/Mastercard *may* have learned the hard lessons they did
when failing to bring SET 1.0 to the market. I.e. I hope (for all the customers using
the currently inferior credit-card systems), that they actually will make merchant
server-plugins available for download instead of relying on a lof of competing
companies
to perform tedious spec. interpretation and interoperability testing. Now when crypto
export rules have changed this should be simple.
A "taste of 3D" can be found (and executed without any registrations etc) on
http://buyer.x-obi.com
where B2B-authentications are performed using the same technology (Server-based PKI,
auto POSTed HTML forms containing signed messages, and no local client SW).
Preliminary whitepaper: http://www.x-obi.com/purple
Regards
Anders Rundgren
CEO X-OBI
