On Monday, November 19, 2001 4:02 AM, Sumatipal Kotangale wrote: > > I need a clarification on the MIASET transactions originating from > Merchant Web site. The scenario is something like this. There is a > Merchant SET engine which maintains the merchant profiles and > certificates and accepts transations from those merchants over SSL. > Basically its a Merchant Aggregator. It then converts this message to SET > and sends it to SET Payment gateway. But now if the merchant SET engine > (aggregator) and the SET Adapter are on the same LAN/Intranet, then can > it still be called a MIASET transaction. The confusion here is that the > SET transaction flow is only between the Aggregator SET Engine and SET > adapter but both of them are on the same LAN/Intranet, and the SET > enabled transactions are not flowing over the Internet. Whereas over the > Internet the transactions come over SSL. So can this transaction be still > called as MIASET enabled transaction.
The SET specification is not concerned with how the messages are transported between the merchant and the payment gateway as long as those messages correspond to the SET specification, they can use any transmission medium. SET messages do not use SSL. _________________________________________________________________ Tony Lewis ([EMAIL PROTECTED]) Chief Systems Architect, Application Architecture & Standards Visa International Service Association
