LDAP for user authentication web services

Home > Plugins > Case-Study

CC application using LDAP Web Services

Business Requirements

To create an Application system that will enable the clinet's global users to subscribe and set-up the services provided on client's corporate Web site and be billed monthly on a credit card. The process includes interaction with LDAP servers and credit card processing gateway.

Solution

The user accesses the application on client's corporate Web site and provides the billing information (Name, address, e-mail address, telephone, and Credit card #). The information will be verified by application for valid field content and edited by the user.

Application will then format the information, store it in secured database on the corporate Web server, and send electronically a copy to the Credit Card Clearing Company for credit charge authorization. The user will be advised by the application that once the site is authorized to bill the credit card, a username and password will be assigned and sent to him via e-mail. As soon as the user starts using the FGR service, the credit card will, each month, be charged with a variable amount.
Upon reception of the credit card user information, Credit Card Company will process the usage authorization and electronically return an appropriate notice. The return notice will trigger one of two processes within Application. If the user is rejected, this user's record will be flagged "rejected" and corrective action will be taken. If the user is approved, the user's record will be flagged as approved. The application will then create this user's userID & password, which will be saved in the user's record in and sent to the RADIUS authentication database using LDAP. The application will also send a pre-formatted e-mail, which will display the userID and password, as well as contain the appropriate dialer exe.
The user will be able to use application to update the account information using the assigned username and password. If the credit card number gets updated, process 2)-Set-up must be re-done. The user will also be able to access the detailed call records that were produced for a month of service from a different Web site. Any rep can use application to update the Status of an account. Credit card numbers are not visible to CS reps. On or around the 15th of each month, another application will be used by the accounting person in charge of invoicing to send billing information to credit card company. The application will retrieve a single file containing all the userIDs and their respective charges for the previous month. The Application will match a userID with its credit card information and send electronically the amount to be charged to Credit Card Company. It is assumed that there is an acknowledgement of this transaction. If the application cannot find a valid record in for a userID found in the billing file , the accounting rep will be prompted and a new monthly exception file will be created. Accounting will be responsible for acting on this information.

For more on our web services expertise and custom application development and integration solutions, please contact us. We are a company based in India that offers outsourced web service and SOA consulting and development services.

Recent Updates

Case Studies