The virtualStoreList field is a critical component in the configuration of stores within the Softpay platform. This article explains its purpose, functionality, and guidelines for updating or configuring its fields.

The virtualStoreList field defines the acquirer host(s) to which a store routes transactions and specifies the acquirer-specific store identifier for each host. It is essential for ensuring proper routing and identification of the store within the payment processing system. Each entry in the virtualStoreList includes the following key components:

The routing layer relies on the virtualStoreList to determine:

Even for single-host setups, at least one entry is required. For multi-host setups, multiple entries are included to enable acquirer switching.

Important: The onlineStoreId is set during the initial creation of the store and cannot be updated later. Ensure its accuracy during setup.

You can safely update the store’s name field without causing any issues. This field is independent of the routing and processing functionality.

For stores using Elavon as the payment processor, the virtualStoreList.cardAcceptorNameLocation field has no functional effect. It is auto-populated during onboarding and can be ignored or updated without impacting the store's operations.

Updating the onlineStoreId for Nets is not supported. Instead the store must be offboarded and a new onboarded.

The virtualStoreList field is essential for defining store routing and acquirer-specific identifiers. By following the guidelines outlined above, you can ensure a smooth setup and operation of your store within the Softpay platform. For further assistance, refer to the Softpay documentation or contact support.