Device Ordering
The Datacap TranCloud device requires that we order Credit Card devices with Ethernet connections.
Since the device uses an Ethernet connection, the device must use an End to End (E2E) encryption. Different processors use different encryptions. You need to work with the customers credit card processor to determine what encryption should be used.
If the processor is:
TSYS - the device must have TSYS Volatage
FIRST DATA - the device must have TransArmor
- but you have to select the appropriate TransArmor encryption the options are:
- Wells A
- Wells NA
- Carlton NA
- PNC A
- BAMS A
- IGNITE PAYMENTS
- The Processor should know the right choice
- TransArmor is additional fee, so anyone using FirstData needs to be made aware of this.
HEARTLAND - should have E2E included
MERCURY - should have E2E included
CHASE PAYMENTECH - E2E is not supported and therefore can't be used with an Ethernet connected device
GLOBAL PAYMENTS - E2E is not supported and therefore can't be used with an Ethernet connected device
Debit Key Encryption and E2E Encryption are two different things.
If the customer is signed up for debit (also an additional fee) you will to set up the debit key encryption when ordering a device.
Errors
ERROR CODE 11: DUKPT Error If the device is not encrypted properly you will receive a Type 11 Error, Encryption not enabled when trying to do the Parameter Download from iMerchant. If you receive this error, notify the customers credit card processor, make sure they are signed up for the right encryption and the device will need to be sent back to the vendor to be reprogrammed with the proper encryption.
ERROR CODE 512: Credit Card Declined - This is an error with the Token Type ID. It's either the ID entered in the Datacap file or its the settings behind the Token Type ID. This was an issue with the setup of Merchant ID parameters within FDPOS. Payment Depot had the TransArmor Encryption Type = 00 (No Encryption) it should be set to 04 (3DES), they also had Security Level = 03 (TransArmor Token Only) it should be set to 01 (merchant participates in encryption and tokenization)
ERROR CODE 004003 - AuthenticationError - we weren't connecting to Datawire. The first issue was that we ordered the Tranclouds under different Merchant ID's and when I updated them to reflect the new ID's given to you by Payment Depot I didn't Acquire a new Datawire ID for the new merchant ID. The second issue was that the Merchant ID given to us from Payment Depot included the Group ID of 10001 in the Merchant ID. We received 100017468330 from Payment Depot and Datawire is only looking for 7468330, so we updated all of the Trancloud files to reflect this and we acquired new Datawire ID's for each Merchant ID. I'm still running into an issue acquiring a new Datawire ID for Union Station under the same Merchant ID as the LODO Store, I have a call into Datacap to try and resolve this issue.
Datacap Setup
When setting up the device on the Datacap file
TSYS - TSYS with Voltage is what you will select for devices with TSYS Voltage encryption
FIRST DATA - the RAPID CONNECT TDES option is what you will select for devices with TransArmor encryption