IBM AS/400e User Handbook Manual page 698

IBM Licensed Programs: Application Development Products
are role-based access controls for granting privilege levels to merchant's employees. The
merchant can also enable and disable event notification service.
Merchants who integrate WebSphere Payment Manager into their business software and
business process can deploy multiple Payment Manager instances as needed to support
multiple merchant instances. This allows communication using HTTP command requests and
receive XML responses—an industry standard.
A hosting service, or Payment Service Provider (PSP), is ideal for any business with low
payment transaction volumes. PSP customers are typically:
• Companies that do not want to manage onsite software and hardware
• Merchants needing a service to handle the complexity of clearing payments with credit
card associations, such as Visa, MasterCard, and Europay
• Businesses new to e-commerce, or that have low payment transaction volumes
browser-based, familiar cash register user interface
Becoming a Payment Service Provider (PSP) is a natural extension for financial institutions
that process credit card transactions for retail stores, mail or telephone order companies, or
small Internet-based businesses. This allows retention of and increase in the financial
institution's customer base. Payment services can also be outsourced to a third party such as
a business partner. Some Internet service providers (ISPs) are also adding payment services
to their business customer offerings. PSPs are positioned to easily help secure and develop
merchant relationships. They quickly can be profitable by collecting revenue from an
increasing volume of transaction fees and through value-add services.
A PSP that uses WebSphere Payment Manager values the ease of adding, modifying,
removing, and provisioning remote merchants, including the ability to deploy separately
multiple Payment Manager instances in support of multiple merchants. Also valuable is the
Multipayment Framework (MPF), which offers the ability to add new payment methods
(cassettes) to the system and deploy for merchant use. Dynamic configuration updating
without system disruptions is also supported to reduce downtime. A browser-based GUI is
provided to securely manage multiple merchants with individual business data privacy,
protection, and integrity. A basic network management support, certified Tivoli ready, is
provided. There is a multilevel trace capability to enhance serviceability.
WebSphere Payment Server allows only designated employees who administer merchant
accounts to:
• Add new merchant customers
• Remove existing ones
• View or edit sensitive customer business data stored on the system
• Modify the system, such as adding new payment types or cassettes
• Set the privileges or restrictions for other employees or customers
668
AS/400e System Handbook