Meet NETePay Hosted

• Tokenization across all processors, even if you change processors.
• Easier switching of processors. Debit keys still need to be changed, but this may be able to be done remotely soon.
• Same pinpads supported across all US processors.
• No charge for software upgrades

• EVO SNAP NETePay-Hosted Bridge - EVO EVO will provide
• Global Canada NETePay-Hosted Bridge - GCR
• Global Payments Portico NETePay-Hosted Bridge - HPS
• Heartland Portico NETePay-Hosted Bridge - HPS
• Paymentech NETePay-Hosted Bridge - PNH
• RapidConnect NETePay-Hosted Bridge - RAPID
• TSYS NETePay-Hosted Bridge - TSYS
• Worldpay Core NETePay-Hosted Bridge
• Worldpay TCMP NETePay-Hosted Bridge - WPH

• Global Canada NETePay-Hosted Bridge - GCR - Verifone P400

• Elavon Host EMV - ELH
• Moneris Canadian Host EMV POSPAD - MSH
• Paymentech Canadian Host EMV - PNH

• Ingenico Lane 3000 requires 6.2.4.193 or newer
• Ingenico Lane 7000 requires 6.2.4.193 or newer
• Verifone P400 requires 6.2.4.451 or newer

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.

1. 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.
2. 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.
3. 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.