Introduction

BridgePay is excited to announce PayGuardian Cloud Tetra, a semi-integrated solution joining our PayGuardian Cloud API with Ingenico Tetra payment terminals.

Ingenico devices do not come with a power cable, power pack or USB/Ethernet cables. Please ensure you explicitly order the required cables. Most use cases will require the Ethernet enabled power cable.

Before using the device, please ensure it has been set up correctly by the distributor to include the accurate date and time. Incorrect date and time can cause call scheduling and mandatory daily reboots to fail. Please follow these steps to ensure the devices are set up properly: https://bridgepaynetwork.atlassian.net/wiki/spaces/DC/pages/243236929/Ingenico+Device+Troubleshooting#Validating-Device-Configurations

Device Configuration

  • Devices can be ordered from these distributors:

  • When ordering devices from distributors, please include the following information with your request:

    • PayGuardian Cloud

      • State that the terminal must be configured for BridgePay’s PayGuardian Cloud solution

    • Ingenico Tetra device model

      • Lane/3000

      • Lane/3600

      • Lane/5000

      • Lane/7000

      • Lane/8000

      • Link/2500

      • Move/5000

    • Environment (select one)

      • Production

      • UAT

    • Key injection

      • Slot 0 (optional): Debit key (only needed if processing debit)

      • Slot 5 (required): BridgePay end-to-end encryption (E2EE) key

Download Files for Device Distributors

Ingenico Local Loading Tool (LLT)

Install LLT first. Use it to connect to the Ingenico Tetra device and install the PayGuardian Cloud Tetra package.

PayGuardian Cloud Tetra packages

Note: These are release packages. For debug versions, please contact TetraBoarding@bridgepaynetwork.com.

Production 1.33

UAT 1.33

Boarding

When boarding a merchant who intends to use PayGuardian Cloud Tetra, the Reseller must request device configuration from BridgePay, as the device serial number is required, as well as parameter defaults.

  • Complete the following request form and return to TetraBoarding@bridgepaynetwork.com. All fields are required.

  • Confirmation will be returned upon completion of boarding in our Hosted Estate Manager.

  • To change already boarded devices, please submit a new form to TetraBoarding@bridgepaynetwork.com

  • Below is an glossary of the terms found in our Bulk Tetra Terminal Request Form:

Boarding Form Header

Description Of Field

Valid values

Environment

The environment in which BridgePay should board the terminal.

UAT

Production

Reseller Name

The name of the Reseller Account within the Gateway.

Variable

Reseller ID

The Reseller Account ID within the Gateway under which BridgePay should board the terminal.

Numeric Value

Merchant Group Name

The name of the Merchant Group within the Gateway.

Variable

Merchant Group ID

The Merchant Group ID within the Gateway under which BridgePay should board the terminal.

Numeric Value

Merchant Account Name

The name of the Merchant Account within the Gateway.

Variable

Merchant Account Code

The Merchant Account ID within the Gateway under which BridgePay should board the terminal.

Numeric Value

Device Type

The terminal model of the Tetra device Bridgepay should board.

Lane 3000

Lane 3600

Lane 5000

Lane 7000

Lane 8000

Link 2500

Move 5000

Device Serial Number 1 & 2

The 25-digit Serial Number found on the bottom most Ingenico tag on the back of the device.

Variable

Automatic Updates

Determines whether or not the terminal will automatically update to the newest version when released.

Yes

No

Automatic Update - Frequency (Days)

Determines the frequency at which the device checks for updates.

Numerical (in Days)

Automatic Update - Device Update Time

The time at which your device checks for updates.

HH:MM AM/PM

All Settings Enabled

Determines whether all subsequent settings should be enabled. Answer Yes if BridgePay should enable all settings to the right of this column.

Yes

No

Daily Reboot Time (11pm if Blank)

The time at which the device performs a daily reboot.

HH:MM AM/PM

EMV Chip Insert

Enables processing via inserting the card into the device.

Yes

No

EMV Contactless

Enables processing via Tap/NFC (including Apple Pay & Google Pay)

Yes

No

Manual Entry

Enables processing via manually typing the card information on the device, if a card is not present.

Yes

No

Signature Capture

Requires the cardholder to sign for the transaction.

Yes

No

Cash Back

Allows a debit cardholder to request for cash back after the card is read.

Yes

No

Tip Prompt

Allows a cardholder to choose a tip amount during the payment process.

Yes

No

Amount Confirmation

Requires the cardholder to confirm the amount of the transaction prior to payment presentation.

Yes

No

CVV Prompt

Requires entering the CVV of the card during payment.

Yes

No

ZIP Prompt

Requires entering the ZIP code of the billing address for the card during payment.

Yes

No

Debit AID - MASTERCARD

Determines whether the device requires a PIN (US Common), does not require a PIN (Global) or allows the cardholder to choose for Mastercard transactions.

Yes

No

Debit AID - VISA

Determines whether the device requires a PIN (US Common), does not require a PIN (Global) or allows the cardholder to choose for VISA transactions.

Yes

No

Debit AID - AMEX

Determines whether the device requires a PIN (US Common), does not require a PIN (Global) or allows the cardholder to choose for American Express transactions.

Yes

No

Debit AID - DISC

Determines whether the device requires a PIN (US Common), does not require a PIN (Global) or allows the cardholder to choose for Discover transactions.

Yes

No

Debit AID - DNA

Determines whether the device requires a PIN (US Common), does not require a PIN (Global) or allows the cardholder to choose for DNA transactions.

Yes

No

Debit AID - UnionPay

Determines whether the device requires a PIN (US Common), does not require a PIN (Global) or allows the cardholder to choose for DNA transactions.

Yes

No

Debit AID - JCB

Determines whether the device requires a PIN (US Common), does not require a PIN (Global) or allows the cardholder to choose for JCB transactions.

Yes

No

Download & Pairing Process

Upon receipt of the terminals, a final download must be completed to ready the device for use with PayGuardian Cloud. The following instructions should be provided to the recipient of the terminals (merchant or reseller partner) to complete this final download:

  • Plug the device into power and Ethernet

    • Wait for the boot process to complete

    • Terminal should load to a Welcome payment screen

  • Connect the Device to Hosted Estate Manager for Download Management

    • Press 2634

    • Press “F”

    • Select “Tetra Admin”

    • Select “2 - Download Application”

    • Select “2 - Start Download”

    • For “Enter Package Name” hit the Green O key (there is no need to enter a name)

    • Download will take place

      • Note that the device will reboot multiple times during the download. Do not interrupt power or Ethernet connections.

  • Pair the device with PayGuardian Cloud following the process for Pairing with PayGuardian Cloud

    • Use the GetPairingCode request to obtain a pairing code

    • Enter the Pairing Code on the device

    • Use the GetUUID request to retrieve the terminalID

  • Complete a transaction using the PayGuardian Cloud API with your terminalID

Pre-Deployment Steps

Confirming the Installed Package

Beta Feedback

We would like to hear any/all feedback regarding your entire experience ordering/configuring/using the devices as you would in normal business operations. 

All beta feedback should be submitted via email to TetraBoarding@bridgepaynetwork.com with the subject line: Tetra Beta

Table of Contents