Credit / Debit Card
NETePay
Flashpoint integrates to DataCap Systems NETePay credit card solution. Using standard Internet or other TCP/IP virtual private network service, payments are authorized in as little as 2 seconds. Also, automatic fail-over to dial back-up is available by adding Datacap’s fast-connect modem, DialLink™. NETePay’s client/server architecture is scalable to fit the needs of any size enterprise and is currently operating in businesses ranging from a single register to over a thousand stores. The following processors are available through the NETePay integration:
Chase Paymentech (US and Canadian debit),
Fifth Third Processing Solutions,
Dialect Payment Services (Australia),
First Data Merchant Services,
Global Payments,
Heartland Payments,
Moneris Canada,
Nova Information Systems,
RBS-Lynk Systems,
Sterling Payments,
TSYS Vital Visanet.
DialEpay
Flashpoint integrates to DataCap Systems DIALePay credit card solution. Using standard phone lines, payments are authorized without the need of bulky equiptment. The following processors are available through the DIALePay
Chase Paymentech,
Fifth Third Processing Solutions,
First Data Merchant Services,
Global Payments,
NPC / B of A ,
Nova Information Systems,
RBS-Lynk Systems,
Sterling Payments,
TSYS Vital Visanet.
Flashpoint also offers a free TCP/IP integration using MercuryPay Server Configuration
Flashpoint integrates to Mercury Payment Systems for high speed (2 sec) credit card authorization. Mercury Payment Systems' MercuryPay wass co-developed Datacap Systems, Inc. The MercuryPay system is a client-server payment processing application that moves transaction information from the client to server in encrypted tcp/ip packets. On the client side is an activeX component that is integrated into the Flashpoint. This component works with the MercuryPay server, standalone NetEpay servers, as well as Datacap's System's Datatran dial-up processing machine. From Mercury’s servers they are sent over a point-to-point connection to Global Payments Inc. The FDIC insured funds are then securely and rapidly transferred by HSBC Bank to the merchant's account at the bank of their choice. The full card numbers are never stored on Mercury’s servers (only in the processing host).
MercuryPay Server Configuration
Mercury Payment Systems maintains multiple servers for redundancy and load balancing. These servers are located in different regions of the country to maintain independent operations even if a whole region is experiencing telecommunications difficulties. Each MercuryPay server is directly connected to the processing host.
Each server has a DNS name the client component is configured with a list of these names. In the event that the primary MercuryPay server name is unresponsive during an attempted transaction, the client component will use the alternate server.
|