faq:datacap_netepay_hosted
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
faq:datacap_netepay_hosted [2022/01/17 09:59 (2 years ago)] – [Datacap deployment Ids] craig | faq:datacap_netepay_hosted [2023/05/24 10:47 (10 months ago)] (current) – [Supported Netepay Hosted US Networks] craig | ||
---|---|---|---|
Line 13: | Line 13: | ||
===== Supported Netepay Hosted US Networks ===== | ===== Supported Netepay Hosted US Networks ===== | ||
* EVO SNAP NETePay-Hosted Bridge - EVO EVO will provide | * EVO SNAP NETePay-Hosted Bridge - EVO EVO will provide | ||
- | * Global Canada NETePay-Hosted Bridge - GCR | ||
* Global Payments Portico NETePay-Hosted Bridge - HPS | * Global Payments Portico NETePay-Hosted Bridge - HPS | ||
* Heartland Portico NETePay-Hosted Bridge - HPS | * Heartland Portico NETePay-Hosted Bridge - HPS | ||
* Paymentech NETePay-Hosted Bridge - PNH | * Paymentech NETePay-Hosted Bridge - PNH | ||
- | * RapidConnect NETePay-Hosted Bridge - RAPID | + | * RapidConnect NETePay-Hosted Bridge - RAPID (Firstdata/ |
* TSYS NETePay-Hosted Bridge - TSYS | * TSYS NETePay-Hosted Bridge - TSYS | ||
- | * Worldpay Core NETePay-Hosted Bridge | + | * Worldpay Core NETePay-Hosted Bridge (Vantiv / Fifth-third) [FTH] |
- | * Worldpay TCMP NETePay-Hosted Bridge - WPH | + | * Worldpay TCMP NETePay-Hosted Bridge - (RBSLink) [WPH, WPT, LNK] |
===== Supported Netepay Hosted Canadian Networks ===== | ===== Supported Netepay Hosted Canadian Networks ===== | ||
- | * Global Canada NETePay-Hosted Bridge - GCR - Verifone P400 | + | |
===== Not supported ===== | ===== Not supported ===== | ||
Line 30: | Line 29: | ||
* Paymentech Canadian Host EMV - PNH | * Paymentech Canadian Host EMV - PNH | ||
- | ===== Supported US Pinpads ===== | + | ===== Supported US Netepay Hosted |
- | | + | ^PIN Pad^Encryption Key^Application Load^Cables| |
- | | + | |{{: |
- | | + | |{{: |
+ | |{{: | ||
+ | |||
+ | <note important> | ||
+ | * Datacap Forms Package | ||
+ | * Debit Key Injection (Key Provided by processor/ | ||
+ | * End-To-End Encryption Key - see table above and confirm with the link above. | ||
+ | * USB cable and Power supply if required. | ||
+ | * You must order from one of the suppliers referenced by the above links. | ||
+ | |||
+ | </ | ||
- | ===== Datacap deployment Ids ===== | ||
- | 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 Server) Standard Installation. Suitable for on-prem location with a single merchant Id. | ||
- | - 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 runs on each lane independently, | ||
faq/datacap_netepay_hosted.1642442391.txt.gz · Last modified: 2022/01/17 09:59 (2 years ago) by craig