IDentiWall eBanking
Target market
Any eBanking providers who wish to implement Multi-Factor authentication and secure ebanking methods.
Product schema
Typical workflow
Same as in the case of IDentiWall Web
but with the addition of:
- Behavioral engine that follows the customer’s normal behavior and instructs IDentiWall to execute special measures
if the behavior is suspect.
- More elaborate Transaction Verification
- Split Transaction over two networks in which the customer is asked to key in details of the transaction both in the
HTML form over the IP network as well as over the cellular network.
Included technologies
- Authentication methods
- Secured banking
- SMS sending
- Billing methods
- HTTP gateway
- Radius server
- Security
Optional technologies Implementation issues
- SMPP client
- Secured registration
- LDAP client
- Mobile pre-installed agent
- WAP push agent
- SMS sending gateway
- Billing server
- Syndication server
Billing issues
- Who serves as the SMS broker?
- Opening an account with the SMS broker
- Who pays for the SMSs, the customer or its users?
- If the users pay (such as in a typical university situation), each user needs to activate their account by
purchasing SMS credits in the Billing server.
- Set up the user’s profile of preferences
Licensing issues
- Number of users with pre-paid license fees to be covered by IDentiWall. For these users the customer will be
charged discounted prices for their SMS consumption.
- Does the customer wish to implement Pay-as-You-Go users? For such users the customer has to purchase undiscounted
SMS credit.
- Does the customer want their users to pay for their service? Such users will have to open and/or activate their
account by purchasing SMS credits from in the Billing server.
For more information see Secure e-Banking
More
IDentiWall Authentication Security Products |
