Skip to Main Content
This article analyzes SET, Secure Electronic Transaction, and WAP, Wireless Application Protocol. Because a WAP client has a less powerful CPU and less memory, and the normal SET cardholder software is large, a WAP client cannot install it. This article provides one model in which a WAP client installing a "thin" wallet securely connects with an Internet wallet server, and communicates with other SET entities to support SET payment. The WAP client's wallet is used by the cardholder to communicate with merchant POS applications and enter SET purchase instructions. The wallet server contains most of the functionality now found on current fat SET wallets. It routes purchase requests from the cardholder, communicates with other SET components, and manages the digital keys and certificates supporting SET security.