Home
Reference
Payments subsystem
In WebSphere Commerce, payment processing uses the Payments subsystem.
Payment configuration files
Use these files when configuring the Payments subsystem and payment plug-ins.
EDPGlobalConfigs XML file
Configure asynchronous processing, and the location of ticklers in this file.

Reference
- WebSphere Commerce API reference
  WebSphere Commerce exposes two main programming APIs. The first and newest API is a REST interface, and most new classes are exposed here. The legacy Java API also contains new classes not suitable for REST, and can be browsed in Javadoc format.
- Cross-reference of data beans, EJB beans, and tables
  Data beans are grouped into several component groups.
- Cross-reference of commands, tasks, and tables
  URL commands, controller commands, task commands, view commands and tables are related to each other.
- Cross reference: Commands to beans to database tables
  Use this information when you are customizing a command and you want to know which tables are affected. You should also use this topic if you are modifying a table and want to know which commands and beans are affected.
- API changes between WebSphere Commerce Version 7.0.0.9 and WebSphere Commerce Version 8.0.0.0
  If you are migrating version 7.0 of WebSphere Commerce, review the API changes between releases.
- WebSphere Commerce database schema
  The WebSphere Commerce database model was designed for data integrity and optimal performance. WebSphere Commerce provides several hundred tables that store WebSphere Commerce instance data. To maintain data integrity, and to ease maintenance referential integrity, constraints are widely used in the database model. Indexes are used carefully on tables to avoid over-indexing and to provide a good balance between data retrieval and data manipulation activities (insert and update). The business rules are implemented at the application level rather than by using database trigger. Triggers, however, are used to facilitate data staging and optimistic locking. A limited number of SQL-based database stored procedures are used for data intensive activities.
- Payments subsystem
  In WebSphere Commerce, payment processing uses the Payments subsystem.
  - Payments subsystem
    In WebSphere Commerce, payment processing uses the Payments subsystem.
  - Extended data in payments or credits
    Some payment plug-ins require extra protocol data or keywords to communicate with a back-end system. This extra protocol data called extended data is in addition to the standard attributes defined in the PaymentInstruction definition. Extended data is any data other than the currency, amount of the payment instruction, and the payment method name. For example, credit card number, expiration, and billing address are extended data.
  - Payment rules provided in WebSphere Commerce
    Payment rules specify the payment actions that should occur for the payment methods a store accepts for its goods or services. Payment actions and credit actions are determined in terms of current-to-target state movements. payment rules define what target state a payment should be in by defining the actions needed to move a payment from its current state to the target state.
  - Payment configuration files
    Use these files when configuring the Payments subsystem and payment plug-ins.
    - AVSRules XML file
      Determines the response when AVS scores 0 to 4 are received for credit card payment methods.
    - CorePaymentActions XML file
      The CorePaymentActions.xml file defines the payment actions required to move the payment from the current state to the required targeted state.
    - EDPGlobalConfigs XML file
      Configure asynchronous processing, and the location of ticklers in this file.
    - PaymentMappings XML file
      Configure the mapping from payment method to payment method configuration and payment actions. You can change what payment rule a payment method uses by changing the PaymentMappings XML file. The behavior of payment processing also changes; when a different payment rule is specified, the actions the system takes also change.
    - PaymentMethodConfigurations XML file
      Use the PaymentMethodConfigurations.xml file to configure the payment method details.
    - RefundMethodConfigurations XML file
      Use the RefundMethodConfigurations.xml file to configure the refund method details.
    - RefundMappings XML file
      Use the RefundMappings.xml to configure between a refund method and refund method configuration. This file can contain multiple refund method mappings.
    - PaymentSystemPluginMapping XML file
      Use the PaymentSystemPluginMapping.xml file to map payment systems to payment plug-ins.
  - Payment plug-in specification
    Review the following overview of the payment plug-in specification to better understand how you can use payment plug-ins.
- Dynamic caching
  In general, caching improves response time and reduces system load. Caching techniques are used to improve the performance of World Wide Web Internet applications. Most techniques cache static content (content that rarely changes) such as graphic and text files. However, many websites serve dynamic content, containing personalized information or data that changes more frequently. Caching dynamic content requires more sophisticated caching techniques, such as those provided by the WebSphere Application Server dynamic cache, a built-in service for caching and serving dynamic content.
- Data Load utility configuration file schema
  The Data Load utility contains several configuration files. You can use the configuration file schema to understand and customize the data load configuration files.
- WebSphere Commerce web services
  WebSphere Commerce provides many web services.
- Utilities
  Utilities help you to accomplish administrative or configuration tasks, for example, loading data, publishing a store.
- Shopping flow URLs
  WebSphere Commerce shopping flow URLs are organized by subsystem.
- Ant targets
  A WebSphere Commerce instance can be created from the command line. The command-line utility uses Apache Ant to create the objects required. The targets are divided into several high-level groups that correspond to the environment that is to be configured.
- Glossary

EDPGlobalConfigs XML file

Configure asynchronous processing, and the location of ticklers in this file.

This file is located in the following directory:

WC_eardir/xml/config/payments/edp
workspace_dir/wc/xml/config/payments/edp

Example

<?xml version="1.0" encoding="UTF-8"?>
<EDPGlobalConfigs xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:noNamespaceSchemaLocation="com/ibm/commerce/edp/eut/parsers/EDPGlobal.xsd">
  <EDPTicklerFactory>WebSphereCommerce</EDPTicklerFactory>
  <AlwaysExecuteProcessBGInFG>true</AlwaysExecuteProcessBGInFG>
</EDPGlobalConfigs>

EDPTicklerFactory

Specifies where ticklers are sent.

WebSphereCommerce: WebSphere Commerce tickler system. This is the default and recommended value.
WasLog: WebSphere Application Server log.

AlwaysExecuteProcessBGInFG

Specifies which type of event should be raised to process the payment actions.

True: Synchronous event is raised
False: Asynchronous event is raised.