Retention of payment information in the WebSphere Commerce database
Some client applications of WebSphere Commerce might send unnecessary data in payment information (extra data in extended data). The following mechanisms are available so you can specify what data should be retained in the WebSphere Commerce database as to avoid database storage issues and maintain satisfactory performance:
- Plug-in deployment descriptor: You can specify the protocol properties for which you would like to retain the data through the <ProtocolProperties> and <ProtocolProperty> elements.
- PaymentSystemPluginMapping.xml file: You can use either or both of these mechanisms:
- You can specify that certain keywords be retained globally, regardless of the payment plug-in processing the information, through the <RetainKeywords> element.
- You can specify which keywords should be removed from the extended data of the payment instruction after the total amount of the payment instruction is approved. All keywords specified under the <Mapping> element in this file are saved in the database unless otherwise specified through the removeAfterApproval attribute.
WebSphere Commerce Payments will determine the appropriate retention action to take based on any configurations found in these files.
(C) Copyright IBM Corporation 1996, 2006. All Rights Reserved.