Differences

This shows you the differences between two versions of the page.

--- faq:datacap_netepay_hosted [2022/01/17 09:55 (2 years ago)] – [Supported US Pinpads] craig
+++ faq:datacap_netepay_hosted [2022/01/17 09:59 (2 years ago)] – [Datacap deployment Ids] craig
@@ Line 37: / Line 37: @@
 ===== Datacap deployment Ids =====
-There are 3 new options for creating the deployment Ids for the datacap bridge installs.
+There are 3 new options for creating the deployment Ids for the datacap bridge installs. Each physical location where a walk-in customer can pay, usually requires a separate merchant account.
-- Generate one Deployment ID (Multiple client applications point to a single, consolidated NETePay instance or Tran device) Standard Installation
+  - Generate one Deployment ID (Multiple client applications point to a single, consolidated NETePay Server) Standard Installation. Suitable for on-prem location with a single merchant Id.
-  - Generate one Deployment ID with multiple Merchant IDs (Consolidated NETePay instance or Tran device for use when a pay station needs to route to multiple merchant accounts, e.g. municipal, sub-contractors, etc.)
+  - Generate one Deployment ID with multiple Merchant IDs (Consolidated NETePay server for use when a station needs to route to multiple merchant accounts). Suitable for On Prem, or cloud if they have access to a shared datacap netepay bridge.
-  - Generate unique Deployment ID for each lane (NETePay or Tran device runs on each lane independently) Learn more Note: with this option, you cannot create a backup deployment. Options for add-ons may also be limited.
+  - Generate unique Deployment ID for each lane (NETePay runs on each lane independently, each station only has access to 1 merchant Id)  Note: with this option, you cannot create a backup deployment. Options for add-ons may also be limited.