RVC routing for multi-MID deployments
Purpose: Run more than one merchant account from a single workstation, sending each revenue center's payments to the right account.
When to use this: A location has several revenue centers, say a restaurant and a bar, that settle to different Merchant IDs, but they share one counter PC. Routing makes sure each revenue center's payments go to its own account.
How it works
The point-of-sale sends a Merchant ID with each payment, based on the revenue center the check belongs to. The workstation looks at that Merchant ID and routes the payment to the matching account. Anything with no specific match falls back to the workstation's primary Merchant ID.
You don't manage this on the PC. The routing list lives in the workstation's cloud config, as a set of Alternative Routes, each one pairs a Merchant ID with the account it should use.
Steps
- Confirm which revenue centers exist and which Merchant ID each should settle to. Get the Merchant IDs from your contact if you don't have them.
- In the cloud portal, open this workstation's config, see Provisioning configs.
- Set the workstation's primary Merchant ID (the fallback).
- Add an Alternative Route for each additional revenue center: the Merchant ID it should use.
- Save the config.
- On the workstation, open
http://localhost:3036/api/dashand press Reload Workstation Config.
[INSERT SCREENSHOT: cloud portal Alternative Routes editor with two Merchant IDs configured]
Verify
- Ring a test sale in each revenue center and confirm in the cloud portal Transactions view that each landed under the correct Merchant ID.
