faq:datacap_netepay_hosted
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
faq:datacap_netepay_hosted [2022/01/17 09:55 (2 years ago)] – [Supported US Pinpads] craig | faq:datacap_netepay_hosted [2022/02/03 13:31 (2 years ago)] – [Supported US Pinpads] tanya | ||
---|---|---|---|
Line 31: | Line 31: | ||
===== Supported US Pinpads ===== | ===== Supported US Pinpads ===== | ||
- | * Ingenico Lane 3000 | + | * Ingenico Lane 3000 requires 6.2.4.193 or newer |
- | * Ingenico Lane 7000 | + | * Ingenico Lane 7000 requires 6.2.4.193 or newer |
- | * Verifone P400 | + | * Verifone P400 requires 6.2.4.451 or newer |
===== Datacap deployment Ids ===== | ===== 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 | + | - Generate one Deployment ID (Multiple client applications point to a single, consolidated NETePay |
- | - Generate one Deployment ID with multiple Merchant IDs (Consolidated NETePay | + | - Generate one Deployment ID with multiple Merchant IDs (Consolidated NETePay |
- | - Generate unique Deployment ID for each lane (NETePay | + | - 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. |
faq/datacap_netepay_hosted.txt · Last modified: 2023/05/24 10:47 (11 months ago) by craig