WebSphere Commerce Payments
When a WebSphere Commerce Site administrator sends a command to Payments, the administrator is authenticated by the realm, then authorized through the Payments access control facility.
The WebSphere Commerce Site Administrator must belong to one of the four Payments defined access roles to have access to the Payments functions. The four access roles are:
- Payments Administrator
- Merchant Administrator
- Supervisor
- Clerk
If you enable single realm and single logon, active WebSphere Commerce Site Administrator login IDs are listed in the Payments user interface. Any WebSphere Commerce user with the Payments Administrator role could assign Payments access roles to any administrators who are displayed on the list. Additionally, once an administrator with Payments defined access roles has logged into WebSphere Commerce Accelerator or the Organization Administration Console, the WebSphere Commerce user can launch the Payments user interface without having to log on again.
The WebSphere Commerce Site Administrator ID created during instance creation is automatically given the Payments access role of Payments Administrator.
Note: If you want to use self-signed server certificates with Internet Explorer 6, configure the Internet Options so that in the Advanced tab under Security the checkbox for Check for publisher's certificate revocation is selected.
Advanced orders Event-driven payments
Other than the Site Administrator role (or Customer Service Supervisor) which is recommended for updating payment or refund method configurations, there are no specific roles associated with the processing of event-driven payments. The notion of the four WebSphere Commerce Payments-defined access roles applies in an advanced orders environment only if the WCPayments plug-in is used to bridge to WebSphere Commerce Payments. If the WCPayments plug-in is not used, the four access roles do not apply.