Merchant feature

We can use the merchant feature to manage merchant information by storing and managing the store-specific properties from the Payment perspective.

In the Payment perspective, multiple stores can share the same merchant. The merchant information is used by the payment side to facilitate payment operation and management.

When you set the association between the store and a specified merchant, the payment processing component maps the merchant configuration to a set of merchant configuration information NVPs specific to the merchant and the Payment plug-in. These NVPs are passed to the plug-in API by way of the plug-in context. If a Payment plug-in requires the merchant configuration property, the stores that use the Payment plug-in must specify the value of the merchant configuration property. However, if the Payment plug-in does not define a merchant configuration property, the stores that want to use the Payment plug-in do not need to do anything. The following database tables support the management of merchant information:

MERCHANT

This table stores basic merchant information, such as the name and the state of a merchant.

MERCHCONF

Merchant configuration for the specific payment system and payment configuration group. For example, the mapping between the merchant and the specified Payment plug-in.

MERCHCONFINFO

This table stores the NVPs for properties of merchant information for a specific merchant configuration. In this table, we can specify if the merchant information is encrypted.

STOREMERCH

Mapping information that indicates which merchant ID is used for a specific store.