Cashier profiles
Cashier profiles are XML documents that implement the profile.dtd document type definition.
The profiles must contain the following basic structure:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Profile SYSTEM "profile.dtd">
<Profile useWallet="false" enableTrace="true">
<CollectPayment>
...
</CollectPayment>
<Command name="DEPOSIT">
...
</Command>
...
</Profile>
All of the information needed to connect to WebSphere Commerce Payments is supplied by way of the Payments page in the Configuration Manager.
When the useWallet attribute is set to true, the Cashier builds a ReceivePayment API request when the Cashier.collectPayment(...) method is called. If the attribute is set to false, an AcceptPayment API request is constructed instead.
The following Cashier profiles are supplied by WebSphere Commerce:
- WCPPlugin_BankServACH.profile
- WCPPlugin_CustomOffline_BillMe.profile
- WCPPlugin_CustomOffline_COD.profile
- WCPPlugin_OfflineCard.profile
- WCPPlugin_Paymentech.profile
- WCPPlugin_VisaNet.profile
WebSphere Commerce-provided Cashier profiles all have the enableTrace attribute set to true so that the Cashier will always record diagnostic information. However, since the actual trace() method used by the Cashier to record this information is the WebSphere Commerce trace class ECTrace, the trace setting controls whether the diagnostic information is written to the log. Tracing for the Cashier function is enabled when you enable tracing for the Order component.
You
can configure the Cashier parameters to add the sensitive attribute
in the profile. If the value of the sensitive attribute
is set to true, this Cashier parameter value is not recorded
in the log. For example: <Parameter name="$PAN" sensitive="true"><CharacterText>{card_number}</CharacterText></Parameter>