MyBridgePay

FE 2023.001

Released April 2023

Enhancements

The following enhancements and fixes were made to MyBridgePay in v2023.001. These changes are scheduled for production deployment April 17th thru April 21st 2023.

• Override Duplicate Transactions in the Virtual Terminal 

• Batch Summary Report Updates

• First Data Rapid Connect Boarding Updates

• Disabling the Dashboard Right for a Use

• Minor Enhancements/Fixes

Override Duplicate Transactions in the Virtual Terminal 

A user can now override a duplicate transaction in the Virtual Terminal. This functionality, once enabled in Account Management on the Virtual Terminal Settings tab, allows a Virtual Terminal transaction to override any duplicate transaction settings setup in Account Management in the Gateway Configuration tab. 

➢ In Account Management on the Virtual Terminal Settings, the user must enable Duplicate Override in the Virtual Terminal Settings to have the option appear in the Virtual Terminal.

Image Removed

 ➢In the Virtual Terminal, the user can toggle Duplicate Override on if they have a transaction that fails the duplicate settings currently setup in Account Management in the Gateway Configuration tab. Enabling the Duplicate Override toggle on the Virtual Terminal will allow duplicate Pre-Auth, Sale and Invoice Numbers to process without any error. Processing a Virtual Terminal transaction with the Duplicate Override toggle disabled will process the payment normally and will be declined if duplicate transaction data is used.

Image Removed

Things to Note:

•  You must have enabled at least one Duplicate Transaction settings in Account Management in the Gateway Configuration tab in order for duplicate transactions to be blocked.

Batch Summary Report Update

The Batch Summary report will now properly show the branded icons for Visa, MasterCard and Discover debit cards instead of the default debit icon. Non-branded debit cards will continue to display the default Debit icon.

Image Removed

First Data Rapid Connect Boarding Updates 

The boarding process for First Data Rapid Connect in the Settings section of the Boarding Portal allows for easier navigation and boarding efficiency by grouping of Industry Specific Settings by type and the ability to collapse or expand these types.

Image Removed

Image Removed

Disabling the Dashboard Right for a User

 The dashboard data can now be hidden from any user by disabling the Dashboard Tab right in the Admin Module. Access the Admin Module and edit the Role you wish to update. Ensure that the Dashboard Tab checkbox is unchecked and save the role. Any user assigned this role will no longer see any dashboard data. The dashboard module will still appear on the left navigation, yet no numerical or card data will be displayed to the user who does not have the right enabled. Instead, users will see a message of “Select a menu option to process.”

Image Removed

Image Removed

Minor Enhancements/Fixes
 

•  Enhancements

  • Added a Clear option in the Admin tab when searching for roles.

    Image Removed

•  Fixes

  • Resolved an issue where users were not able to export reports.

  • Resolved an issue where Sale agent users were not able to edit Threshold Controls for their Merchant Accounts.

  • Resolved an issue when clicking the email option on a receipt, unwanted data would appear on the Receipt Email screen. 

Supported Browsers in MyBridgePay 

The following browsers are supported in MyBridgePay when using the latest versions:

• Google Chrome

• Microsoft Edge

• Mozilla Firefox

FE V2022.002

Released February 2023

Enhancements

The following enhancements and fixes were made to MyBridgePay in v2022.002. These changes are scheduled for production deployment February 6th thru February 14th prior to 6 am ET.
 

❖ Connected Multiple Merchant Accounts to a Single PAX Device

❖ Custom Field Creation and Editing Enhancements

 ❖Custom Merchant Account Fields

 ❖ Unsettled Void Right

❖ "Send to Customer" Email Option when Vaulting a Payment

❖ Account Management Business Info and User Data Rules 

Connected Multiple Merchant Accounts to a Single PAX Device

The ability to pair multiple Merchant Accounts to a single PAX terminal is added to the Virtual Terminal. Now, multiple Merchant Accounts can be setup to process to a single PAX terminal. You can pair up to 25 Merchant Accounts to a single terminal. Here are some things to note about this added functionality in the Virtual Terminal:

• You must ensure that the Username and Password entered into the BridgePay BroadPOS file (BridgePay Tab) is a Merchant Group Username and Password. 

• To use the Multi-Merchant functionality built into the BridgePay BroadPOS application, you must program each Merchant with a Merchant Group User or you will receive errors when attempting to process a payment from the PAX device.

• It is a good idea to disable "Local Duplicate Check" in the PAX device as it will consider all paired Merchant Accounts and users may experience unwanted declines. We recommend you use the duplicate checking in the MyBridgePay portal per Merchant Account, as this will be more accurate.

Custom Field Creation and Editing Enhancements 

The process of creating custom fields has been updated to allow the creation of multiple field types. In addition, the ability to make a custom field required has been added to the application. Your user must have the Custom Fields right enabled to be able to view/create/edit Custom Fields in Account Management.
 

Creating Custom Fields 

We have made a few minor changes with creating Custom Fields. First, when creating a Custom Field, the user is now given the option to choose between two field types, Transaction and Merchant Account. Transactions Custom Fields appear on the Virtual Terminal when processing a payment. Merchant Account Custom Fields appear on the Business Information page for Merchant Accounts and are a new feature we’ll discuss later in these notes. Field style allows the user to select the field type (Text Box, Drop Down, etc). Field Name is name of the Custom Field you are creating. No changes were made to the validation options for a Custom Field.

Image Removed

New Custom Field Features 

We have enhanced the way Custom Fields are displayed and managed after creation. Both Transaction and Merchant Account Custom Fields appear in a single list. Here is a breakdown of all the columns and their uses.

Reseller Level (Account Management)

Image Removed

Field ID: This column displays the ID number for the Custom Field.

Field Name: This column displays the Field Name for the Custom Field.

Field Style: This column displays the Field Style for the Custom Field (Text Box, Drop Down, etc.).

Field Type: This column displays the Field Type for the Custom Field. This can be “Transactions” or “Merchant Account.”

Is Required?: This column allows the user to choose if this Custom Field is required on the Virtual Terminal (Transactions) or on the Business Info page for a Merchant Account in Account Management (Merchant Account). This setting is inherited for lower hierarchy levels. EXAMPLE: If required at the Reseller level, will be required for all Merchant Groups and Merchant Account under that Reseller. Individual Merchant Accounts can disable the question if set to required at a higher hierarchy level. The setting is only to require an enabled field and does not force a custom field to be enabled.

Activate on New Merchant Account: This column allows users to choose if newly created Merchant Accounts will have the Custom Field activated by default.

Actions: This column gives users the ability to edit a Custom Field and the ability to bulk enable/disable a Custom Field on all Merchant Accounts lower in the hierarchy. Custom Fields created in a higher hierarchy level cannot edit Custom Fields. EXAMPLE: If Custom Field was created at the Reseller level, editing at a Merchant Group or Merchant account level will not be possible.

Manage Activations: This is a new feature and it allows Reseller, Sales Agent or Merchant Group users to Activate or Deactivate a Custom Field for all Merchant Accounts lower in the hierarchy. EXAMPLE: Activate a Custom Field at a Reseller level, will activate the Custom Field on all Merchant Accounts under that reseller. You can also deactivate a Custom Field on all Merchant accounts so be sure to pay close attention to the activation text.

Image Removed

Merchant Group Level (Account Management)

Image Removed

Field ID: This column displays the ID number for the Custom Field.

Field Name: This column displays the Field Name for the Custom Field.

Field Style: This column displays the Field Style for the Custom Field (Text Box, Drop Down, etc.).

Field Type: This column displays the Field Type for the Custom Field. This can be “Transactions” or “Merchant Account.”

Is Required?: This column allows the user to choose if this Custom Field is required on the Virtual Terminal (Transactions) or on the Business Info page for a Merchant Account in Account Management (Merchant Account). This setting is inherited for lower hierarchy levels. EXAMPLE: If required at the Reseller level, will be required for all Merchant Groups and Merchant Account under that Reseller. Individual Merchant Accounts can disable the question if set to required at a higher hierarchy level. The setting is only to require an enabled field and does not force a custom field to be enabled.

Activate on New Merchant Account: This column allows users to choose if newly created Merchant Accounts will have the Custom Field activated by default.

Display on Receipts?: This column allows the user to choose if the Transactions Custom Field appears on the receipt. Not applicable for Merchant Account Custom Fields. There is a limit of 3 Transactions Custom Fields enabled on a single Merchant Account that can be displayed on the receipt.

Actions: This column gives users the ability to edit a Custom Field and the ability to bulk enable/disable a Custom Field on all Merchant Accounts lower in the hierarchy. Custom Fields created in a higher hierarchy level cannot edit Custom Fields. EXAMPLE: If Custom Field was created at the Reseller level, editing at a Merchant Group or Merchant account level will not be possible.

Manage Activations: This is a new feature and it allows Reseller, Sales Agent or Merchant Group users to Activate or Deactivate a Custom Field for all Merchant Accounts lower in the hierarchy. EXAMPLE: Activate a Custom Field at a Reseller level will activate the Custom Field on all Merchant Accounts under that reseller. You can also deactivate a Custom Field on all Merchant accounts so be sure to pay close attention to the activation text.

Image Removed

Merchant Account Level (Account Management)

Image Removed

Field ID: This column displays the ID number for the Custom Field.

Field Name: This column displays the Field Name for the Custom Field.

Field Style: This column displays the Field Style for the Custom Field (Text Box, Drop Down, etc.).

Field Type: This column displays the Field Type for the Custom Field. This can be “Transactions” or “Merchant Account.”

Is Required?: This column allows the user to choose if this Custom Field is required on the Virtual Terminal (Transactions) or on the Business Info page for a Merchant Account in Account Management (Merchant Account). This setting is inherited for lower hierarchy levels. EXAMPLE: If required at the Reseller level, will be required for all Merchant Groups and Merchant Account under that Reseller.

Display on Receipts?: This column allows the user to choose if the Transactions Custom Field appears on the receipt. Not applicable for Merchant Account Custom Fields. There is a limit of 3 Transactions Custom Fields enabled on a single Merchant Account that can be displayed on the receipt.

Things to Note:

• You can now require Custom Transaction fields on the Virtual Terminal

• There is currently no way to pull a report for the Custom Merchant Account Field data entered during boarding.

• There is a limit of 3 Transactions Custom Fields enabled on a single Merchant Account that can be displayed on the receipt.

• Custom Fields created via the Boarding API will not appear in MyBridgePay.

• Requiring a Custom Field is only available in MyBridgePay. Requiring a Custom Field via the Boarding API was not added as a feature in this release.

• If using Service Fees, the Service Fee Merchant Account cannot have a required Custom Field enabled to prevent transaction declines.

Custom Field Creation and Editing Enhancements 

Collecting custom information when boarding a Merchant Account is now a feature in Account Management. Create Custom Merchant Account Fields in the same way you create Transaction Custom Fields today. The created Custom Merchant Account Fields will appear on the Merchant Account Business Info screen when creating or editing a Merchant Account. These can also be requirement for creating and editing Merchant Accounts. Please see the section above for details on creating Custom Fields (Custom Field Creation and Editing Enhancements). If the Merchant Account fields are enabled on a Merchant Account, when you access the Merchant Account’s Business Info in Account Management, you will see the fields displayed. They can be completed and saved.

Image Removed

Things to Note:

• There are plans to add reporting for Custom Merchant Account Fields in the future.

• If added to an existing Merchant Account, any required field must be completed before the Save option is allowed.

Unsettled Void Right

A new “Unsettled Transaction Void” right has been added to the application. This right, if enabled on a user, will allow voiding payments on the Batch Management Unsettled Batch tab. The existing void right has been changed to only allow voiding from Find Transactions.

Image Removed

"Send to Customer" Email Option when Vaulting a Payment

When making a Wallet payment in the Recurring Billing Virtual Terminal and then emailing a receipt, the ability to email the Wallet payment customer has been enhanced. A toggle has been added that will email the customer if enabled. Users will no longer need to know and enter the full email address of the customer as this data will be prepopulated.

Image Removed

Account Management Business Info and User Data Rules

In an attempt to avoid data integrity issues between the database and the user interface, we have updated the rules when entering Business Information and User Information in the Account Management module. Existing data that has been entered will not need to be changed. Moving forward, these rules will be followed when creating Resellers, Sales Agents, Merchant Groups and Merchant accounts and their users.

Business Info:
Business Name: Must be alpha numeric only and contain the following special characters -/$”#&.
Contact First Name: Alphabet Only (No Numbers or Special Characters with exception to the characters -')
Contact Last Name: Alphabet Only (No Numbers or Special Characters with exception to the characters -')
City: Alphabet Only (No Numbers or Special Characters)
Zip Code: Numeric Only (US Only)

User Details:
First Name: Alphabet Only (No Numbers or Special Characters)
Last Name: Alphabet Only (No Numbers or Special Characters)
Username: Alphabet and Numeric Only (No Special Characters)
Password: The Password field should be between 8 and 20 characters, must contain one upper-case alpha, one lower-case alpha, one digit and one special character within this list !@$^*()?
Confirm Password: The Password field should be between 8 and 20 characters, must contain one upper-case alpha, one lower-case alpha, one digit and one special character within this list !@$^*()?
City: Alphabet Only (No Numbers or Special Characters)
Zip Code: Numeric Only (US Only)

 API Updates

• BridgeComm

  • Added AVS option for NO_STREET_AND_ZIP_MATCH. Transactions will return a decline from the processor if both the street address and zip do not match what the card issuing bank has on file if this option is set to true.

  • Custom Fields with invalid XML names removed from transaction responses.

  • Added a Memo field (optional user data).

  • Now allow passing in a new value of 'unattended' in the TerminalCapabilities API field.

  • Now passing KSID acquired from HSM to JPS in the P2PEDecryptor library.

  • You can now make a call to get the current API version back. This will allow users to see if the API has been updated.

• Boarding API

  • Threshold Controls aettings can now be added/updated via the Boarding API.

  • The TenderCard Gift Card processor can now be created/updated via the Boarding API.

  • Updated to Validate Custom Field Names in Custom Field Controller Create and Update calls.

  • Added the ability to create Organization Custom Fields. These are used as custom Merchant Account Business Information fields.

  • You can now make a call to get the current API version back. This allow users to see if the API has been updated.

• Reporting API

  • Dynamic Descriptor data is now returned to the Reporting API.

  • Updated the FindTransaction call to only return transaction information that the authenticating user has access to.

  • You can now make a call to get the current API version back. This will allow users to see if the API has been updated.

• Recurring Billing API

  • You can now make a call to get the current API version back. This will allow users to see if the API has been updated.

• Wallet API

  • You can now make a call to get the current API version back. This allows users to see if the API has been updated.

Fixes/Minor Enhancements

• Enhancements

  • Removed the "Reply to" option when emailing receipts.

  • Updated the "Transaction ID" search filter on reports to include both full and partial search results.

  • Select Account Optimization

  • Added a new AVS option  for "Street Address and zip do not match" that will return a decline from the processor if both the street address and zip do not match what the card issuing bank has on file.

​​​​

• Fixes

  • ​ ​​​​​Resolved an issue where no validation text was displayed when adding numerical characters to the First & Last name fields when creating Accounts or Users in Account Management.

  • ​Resolved an issue where service fee could be set to $0.00. Must be greater than $0.00.

  • Resolved an issue where "Merchant Account" was not displaying in the list of columns in reports when the report included more than one Merchant Account's information.

  • Resolved an issue with Batch Management Unsettled Batches tab where sorting the "Capture Amount" column was not sorting correctly.

  • Resolved an issue where the "Capture All" option was still appearing on the Batch Management Unsettled Batches tab when there were no open authorizations on the open batch.

  • Resolved an issue where Custom Fields were not allowing saving if the name was changed.

  • Resolved an issue where transaction totals over $1000 with percentage Convenience/Service Fee would force a $0.00 fee. The calculation is now correct. 

  • Resolved an issue where the Recurring Billing list only displayed up to 1000 records. More than 1000 records will now displays.

Supported Browsers in MyBridgePay

The following browsers are supported in MyBridgePay when using the latest versions:

• Google Chrome

• Microsoft Edge

• Mozilla Firefox

V2022.001

Released August 2022

Enhancements

The following enhancements and fixes were made to MyBridgePay in v2022.001. These changes were deployed in UAT/Cert on July 22nd, 2022 and are currently targeted for production deployment in the week of August 15th prior to 6 am ET.

❖ Threshold Controls

❖ TenderCard Gift Cards

❖ Reseller and Sales Agent User Search

❖ Voice AUTH Capture Right

❖ Payments Accepted Checkboxes in Processor Setup

❖ Reseller and Sales Agent User Search 

Threshold Controls

Threshold controls are now available in MyBridgePay for each processor setup. This feature allows Reseller and Sales Agent users to set thresholds on each processor for individual transactions or for multiple transactions over a rolling 30-day period. Each option is explained below.

To access the Threshold Controls in MyBridgePay:

1. Click the "Account Management" tab

2. Navigate to the Merchant Account to edit

3. Click the "Processors" tab

4. Select the Processor to edit or setup a new one

5. Click the "Threshold Controls" tab

The following settings will not be available for editing.

Image Removed

Max Single Sale / Sale-Auth:
The dollar value maximum of a single sale or a Sale-Auth transaction. 
Enter the total amount allowed on a Single Sale/Sale-Auth. Any attempt to make a single Sale/Sale-Auth above the entered amount will result in a decline. 

Max Total Sales / Sale-Auths:
The rolling dollar value of all Sale, Sale-Auth open and captured transactions in a 30 day period (29 days prior to today’s date and includes today's transactions). Enter the total amount allowed on all Sale/Sale-Auths within a 30-day period. Any attempt to make multiple Sale/Sale-Auths that total above the entered amount will result in a decline. The 30-day period automatically renews each day within the MyBridgePay system. Renewal occurs at midnight Eastern Time. 

Max Single Refund:
The dollar value maximum of a single refund transaction.
Enter the total amount allowed on a single refund. Any attempt to make a single refund above the entered amount will result in a decline.  

Max Total Refunds:
The rolling dollar value of all refund transactions in a 30 day period (29 days prior to today’s date and includes today's transactions). Enter the total amount allowed on all refunds within a 30-day period. Any attempt to make multiple refunds that total above the entered amount will result in a decline. The 30-day period automatically renews within the MyBridgePay system, and is not based on a calendar month. Renewal occurs at midnight Eastern Time.

Notification Email 1:
This is a required field if any have been set. Enter the email address for a person or distribution group to receive threshold emails. An email is sent to this address for any Sale/Sale-Auth/Refund attempt that exceeds any threshold set. For Max Total Sale/Sale-Auth/Refunds, this address will receive an email when 10%, 1% and 0% of the Max Total entered is remaining. The email content and frequency cannot be changed.

Notification Email 2:
Enter the additional email address to receive the threshold emails. It follows the same rules as Notification Email 1 but this is not a required field.
 

Things to note:

• New BridgeComm API and MyBridgePay response codes for declines due to Single Sale/Refund and Total Sales/Refunds (rolling settlement volume being reached)

  • 30084- Transaction exceeds max single transaction threshold

  • 30085- Transaction exceeds max total threshold

• Recurring transaction totals are taken into consideration for any set single/total amount. Any recurring transaction that accedes a threshold will be declined. 

➩ Threshold Controls User Guide

TenderCard Gift Cards

TenderCard is now an available Gift Card processor in the BridgePay Gateway. Resellers will simply need to add TenderCard as a gift card processor in the MyBridgePay Boarding Portal. TenderCard will supply the merchant with a Connection String that is entered into the MyBridgePay Boarding Portal. A TenderCard merchant account will need to be setup with TenderCard. Resellers should reach out to TenderCard directly for assistance.

Account Management >> Navigate to Merchant Account >> Processors >> Create Processor

Image Removed

Things to note:

• Each Merchant Account can only have a single TID. This means that a single Merchant Account in the BridgePay Gateway cannot process to different TIDs. Additionally, multiple Merchant Accounts on the gateway cannot be programmed with the same connection string.

• ​​​​​​The connection string from TenderCard must be a “copy and paste” exactly as provided by TenderCard or the connection will fail and transactions will not process.

• Gift Card transactions are currently not supported in the MyBridgePay Virtual Terminal

• TenderCard can only be set-up or added to an existing merchant account via the MyBridgePay Boarding Portal. It cannot be setup via the Boarding API but will be available at a later time.

• Refunds are not supported for this Gift Card provider. You may add money back to an existing Gift Card or issue a new Gift Card for the total amount that should be returned to the customer. 

Reseller and Sales Agent User Search

Search and edit users from the Admin module. Reseller and Sales Agent users, if given the access to the Admin tab, can now search for users within their hierarchy and edit the users directly from the Admin module. Reseller and Sales Agent users will no longer need to navigate through the Account Management pages to edit different user types. To use, simply access the Admin module in the left navigation section and click on the Users tab. From here, search by username, user ID or Merchant Account Code. This feature makes it very easy to manage users.

1. Navigate to the Admin tab as a Reseller or a Sales Agent user

2. Add or edit a custom role by checking the "Admin Tab"

3. Save the custom role

4. Edit the Reseller or Sales Agent user to have access to the Admin tab

5. Add the custom role to the user and save

Image Removed

How to Search for a User

Image Removed

Reseller and Sales Agent users can easily search for users in their hierarchy. Enter text into any of the search fields and the page will automatically limit the results based on the entered text. You can also use the “Type” column to limit your results to a single user type. Below is an image of the search page for a reseller user and an explanation of each column.
 

User ID:

The unique ID of each user.

Username:

The username given during user creation.

Type:

The type of user. (Possible results: Reseller, SalesAgent, MerchantGroup, MerchantAccount).

SalesAgent:

Displays the name of the associated Sales Agent for the user if applicable.

Merchant Group:

Displays the name of the associated Merchant Group for the user if applicable.

Merchant Account:

Displays the name of the associated Merchant Account for the user if applicable.

Merchant Account Code:

Displays the ID of the associated Merchant Account for the user if applicable.

Locked Out:

This displays if the user is currently locked out or not. A checkmark displays if the user is currently locked out.
Users cannot be unlocked from this section. You must edit a user to lock or unlock the user.

Image Removed

If selected, the  icon allows editing the specific user. The screen used in Account Management to edit users is displayed. Make any desired changes and save the user.

Things to Note:

• Reseller and Sale Agent users can access this feature if the "Admin Tab" right has been enabled in a role assigned to their user.

Voice Auth Capture Right

The “Voice Auth Capture” transaction type in the MyBridgePay Virtual Terminal will now be disabled by default and can now be enabled by user. Initially, this functionality was enabled for all users. If you wish to have the option appear in the MyBridgePay Virtual Terminal, please enable the new “Voice Auth Capture” right in the Admin module.

Create a Role that has the "Voice Auth Capture"enabled.

Image Removed

Assign the role to a user. This user will be able to see the "Voice Auth Capture" option in the Virtual Terminal transaction type dropdown menu. 

Image Removed

Things to Note:

• By default, this right is disabled for all users. To allow this transaction type, access must be added to the user(s).

Resellers using the MyBridgePay Boarding Portal will now experience a more user-friendly set-up process for the card type’s acceptance section. Before this release, users who were setting up processor settings had to edit a string of letters to choose which card types they wished to allow. Now we have simplified this process by simply checking the box(es) to enable acceptance for the different card brands/types.

Image Removed

Things to Note:

• No changes were made to current processor settings. 

Fixes/Minor Enhancements

• Enhancements

  • Updated the Visa logo in the Virtual Terminal, Reports and Receipts per Visa's request.

  • Updated the receipts to only display the download/print/email icons if they are valid approvals/declines. Transaction errors will not provide these options, as the transaction is not saved into Reports.

   

• Fixes

  • ​ ​​​​​Resolved an issue where Virtual Terminal transactions that had the amount field filled out by chrome autofill caused the ID Tech Augusta card readers to not auto populate card data to the Virtual Terminal (ie: card number, expiration date). This was happening for both EMV and swiped transactions.

  • ​Resolved an issue where special characters were not being validated for the Business Name field in Account Management and the Role Name field in Admin // Roles.

    • Business Name accepted special characters: -/$#&"

    • Role Name accepted special characters: -_()

     

   

Supported Browsers in MyBridgePay
The following browsers are supported in MyBridgePay when using the latest versions:

• Google Chrome

• Microsoft Edge

• Mozilla Firefox

V2021.005
Released January 2022

The following enhancements and fixes were made to MyBridgePay in v2021.005. These changes were deployed in UAT/Cert on January 10th, 2022 and are currently targeted for production deployment in the weeks of January 17th and 24th, 2022.
 

❖ Customizable Contact Us Page & Menu Option

❖ New Search Options in the Recurring Billing Virtual Terminal 

❖ Mastercard Network Gateway Services (MNGS) Processor Added (Future Availability)

Customizable Contact Page & Menu Option

For those partners that have a branded site, we have added the ability to add a “Contact Us” option to a branded login page. Clicking the contact us link on the login page will direct the user to a contact us page. Resellers can also feel free to use our support information as their contact us email and phone number.

Image Removed

Resellers can add a contact email, phone number and message to the contact us page. 

Image Removed

Image Removed

There is also a "Contact Us" option in the MyBridgePay gateway. You can access it in the top right corner of the page with the  icon.

Image Removed

 Things to note:

• Support Email only supports a 50-character max.

• The "Custom Message" will only display on the login page if you have a Support Email or Support Phone entered and saved. 

• Only available for partners that have a branded site. 

New Search Options in the Recurring Billing Virtual Terminal 

We have enhanced the wallet search features in the Recurring Billing Virtual Terminal. Users can now search for wallets by "Customer Account Name" and "Wallet Name".

Image Removed

Mastercard Network Gateway Services (MNGS) Processor Added

We have integrated to the Mastercard Network Gateway Services or MNGS. MNGS is a direct to Mastercard processor that supports all major credit cards types. For more information visit:  https://www.mastercard.com/gateway.html

To connect a MyBridgePay gateway to MNGS:

1. Access MyBridgePay as a Reseller or a Sales Agent that has the "Processors" right enabled and the "MNGS" processor right enabled. 

2. Click "Account Management"

3. Access the Merchant Account you wish to edit.

4. Click "Processors"

5. Click "Create Password"

6. For "Type" choose "Credit Card"

7. For Processor Select "MNGS"

8. Click the "Settings" tab

9. Enter all of the required information (MasterCard would provide a Processor Setup Form or VAR sheet)

10. Click "Save"

 Selecting MNGS as a Processor:

Image Removed

Processor Settings:
 

Image Removed

Things to note:

• You must first have an account with MasterCard to use this processor type.

• MasterCard must provide the Processor settings that will be entered into MyBridgePay.

Enhancements

• Enhancements

  • Updated the Email Address field to be required when vaulting a payment from a receipt.

  • Updated the receipt text of "Merchant ID" to "Merchant Account Code" for clarity.

  • Updated the Virtual Terminal Role Right of "Void" to enable/disable void functionality in Find Transaction and Batch Management (Unsettled Batches Tab).

  • Updated the Virtual Terminal Role Right of "Refund" to enable/disable refund functionality in Find Transactions.

   

• Fixes

  • Fixed an issue where "null" was appearing in the Batch Settlement email in error.

  • Fixed an issue where the drop down selection color was not appearing as the primary color in branded accounts.

  • Fixed an issue where "Wallet Name" was not saving to the system when vaulting a payment.

  • Fixed an issue where Google Recaptcha was blocking access if the initial login attempt had invalid credentials.

  • Fixed an issue where after editing a user and clicking "Cancel" the user's name would still appear in Account Management instead of returning back to the reseller name.

  • Fixed an issue where the Dashboard where the 90 day date range option displayed 91 days in error.

  • Fixed an issue where JCB card types were displaying a Discover icon in error. 

  • Fixed an issue where vaulting a JCB card was displaying a MasterCard icon in error.

  • Fixed some column alignment issues in Batch Management.

  • Fixed an issue where the Roles search filter text could be invisible due to branding white on white.

  • Fixed an issue where "Account Type" was blank in the Batch Summary export for Cash and Check payments.

  • Fixed an issue where some Email Address fields did not allow some email formats. All Email Address fields allow all email formats now.

  • Fixed an issue where the "Name on Check" field on the Recurring Billing Virtual Terminal was required in error.

   

Supported Browsers in MyBridgePay
The following browsers are supported in MyBridgePay when using the latest versions.

• Chrome

• MS Edge

• Firefox

V2021.004
Released November 2021

The following enhancements and fixes were made to MyBridgePay in v2021.004.

These changes are scheduled to deploy the week of 11/8/21 thru the week of 11/15/21. 

❖ Industry Type added to Reports

❖ Service Fee Functionality for EMV Devices

❖ Cache Management Changes

❖ Account Processing Policy Help Text

❖ Voice Auth Capture for TSYS

❖ Separated Check and ACH Payments on the Dashboard

We have updated multiple reports to include the industry type information. This can information can be added, filtered and reorganized within the reports. To enable this column in a user’s reports, simple edit any user, click ‘User Settings” and enabled “Insert additional "Industry Type" column for UI display and export files.”

Image Removed

Image Removed

Image Removed

This will update the following reports with the Industry Type information for this specific user.

• Transaction Reports

  • Sales Report

  • Declines Report

  • Transaction List

  • Custom Fields Transaction List

   

• Batch Reports

  • Summary Reports

  • Detail Reports 

   

• Find Transactions/Advanced Search 

Exporting the reports will also include the Industry Type information if enabled for the user.

Things to Note:

• ACH transaction will report the SEC code in the Industry Type column 

Service Fee Functionality for EMV Devices

We have updated the Virtual Terminal to allow the Service Fee functionality with EMV devices (PAX and Augusta). If you have a Service Fee enabled on a Merchant Account and you choose a device, the Service Fee field will remain visible. Processing a Service Fee will charge a separate Merchant Account the Service Fee.

Things to Note:

• PAX devices only support Service Fees on Sales. If Authorization only is selected in the Virtual Terminal, the Service Fee option will disappear from the Virtual Terminal.

Cache Management Changes

We have made improvements to the MyBridgePay cache management. Now, after releases, there will be no issues with missing features or overall site navigation. This was a small change made to handle caching within MyBridgePay and it should ease some of the "after release" pains due to caching.

• A final cache clear may be needed on some browsers after this release. Once this final cache clearing is preformed, users should never need to clear cache and cookies after a release moving forward.

Account Processing Policy Help Text

We added some help text to the Account Processing Policy within a Merchant Account when setting up a processor. Now the programming of different card brands is clearer.
 

Image Removed

Account Processing Policy

When listed in the Account Processing Policy field, the card types below will be enabled for processing on a merchant account provided the processor supports the card types entered.

The exact format order must be: VMXDNGFB

Examples:

VM-D---B = Allows processing of only Visa, Mastercard, Discover and Debit card types.
VM-DNG-B = Allows processing of all card types except Diners and American Express.
V = Visa
M = Mastercard
X = American Express
D = Discover
N = Diners
G = Gift Card
F = Fleet Card
B = Debit Card

• = Skip Card Type

Voice Auth Capture for TSYS

We have enhanced the Virtual Terminal to allow for a Voice Auth transactions on the TSYS processor. This transaction type allows a merchant who has obtained a voice authorization for a credit card payment to place the transaction into the current open batch for settlement. The transaction does not need re-authorization and a new authorization should not be obtained.

This transaction is manually keyed only and cannot be processed as an EMV or Swiped transaction.

Simply chose “Voice Auth Capture” from the Virtual Terminal for the Transaction Type. This will bring up the “Approval Code” field on the Virtual Terminal. Enter the Auth Code you wish to use to process a new transaction.

Image Removed

This will bring up the “Approval Code” field on the Virtual Terminal. Enter the Auth Code you wish to use to process a new transaction.

Image Removed

Things to Note:

• This feature will not work with an EMV enabled device. The device selection filed will no longer appear if "Voice Auth Capture" is selected.

• Only available for Merchant Account connected to the TSYS processor.

Separated Check and ACH Payments on the Dashboard

We have separated checks and ACH payments on the "Payment type breakdown" on the Dashboard. They were combined totals before.

Image Removed

Fixes/Minor Enhancements

• Enhancements 

  • Image Removed

  • Merchant Accounts with unsettled batches can no longer be deactivated. Please settle all open batches before deactivating.

  • Image Removed

  • Small text update in “Processing Applications” (Removed VT and added Virtual Terminal)

  • “Add Payment Method” option when creating a wallet now only allows payments types that are setup in the Merchant Account.

  • Added a delete option for customer themes in the Branding Management.

   

• Fixes

  • Image Removed

  • Fixed an issue where Merchant Accounts with an ACH-Realtime processor setup would not display ACH as an option in the Virtual Terminal

  • Fixed an issue where Blind Refunds would not process nor would an error message appear if there were issues.

  • Fixed an issue where users could change “IsPrimary” for their own account level in error.

  • Fixed an issue where printed receipts were printing too many pages when “both” was selected on the receipt.

  • Fixed an issue where AMEX cards in the Virtual Terminal showed the icon of Debit after entering the card number.

  • Fixed an issue where after closing transaction details the row of the report is still highlighted in error.

  • Updated Activate/Deactivate hover text in Branding Management.

  • Fixed UI spacing issues in “Gateway Configuration” for duplicate transactions settings.

  • Fixed an issue where the Print option displayed a blank page from transaction details.

  • Fixed an issue with the incorrect fonts being used in Mozilla Firefox.

  • Fixed an issue where logging in to a user that only has one account level available was not pre-populating in the “Select Account” section.

  • Fixed an issue where Merchant Group and Merchant Account Custom Fields “Display on Receipts” settings were not staying set to what the Merchant Account chose.

  • Fixed and issue where declined unbranded debit transactions did not list Card Type in exported reports.

  • Fixed an issue where Exported Transaction List reports were displaying “AMEX” instead of “AMERICAN EXPRESS” for the card type in error. “AMERICAN EXPRESS” is the expected card type name.

  • Fixed an issue with Batch Summary and Batch Detail reports where debit transactions listed the Card type of “BANK CARD DEBIT” instead of “DEBIT” in error. “DEBIT” is the expected card type name.

  • Fixed an issue where Chase processor settings were unable to be edited.

  • Fixed an issue on ACH decline receipts not displaying the Account Type of “ACH”.

  • Fixed an issue where very long usernames tot not wrap text in Admin list.

  • Fixed an issue where updating a Reseller name did not reflect in the Reseller column in the Admin Module’s tab.

  • Fixed an issue where deactivated Merchant Accounts appear in the Account Select menu as active if page is refreshed after deactivation.

  • Fixed an issue where Find Transactions was displaying a Void Icon on EBT transactions in error.

  • Fixed an issue where transactions could process with an invalid Invoice Number, PO Number or Customer ID from Find Transactions.

  • Fixed a Zip Code validation error when setting up a wallet.

  • Fixed an issue where “Merchant Account Access” remained red in error in Account Management.

  • Fixed an issue in the Virtual Terminal where SEC code drop down could be deselected and still process the transaction causing an error.

  • Fixed an issue where selecting “Both” on an emailed receipt sent two Customer Copies instead of a Customer and Merchant Copy.

  • Fixed an issue where “Card Verification” was not an option in the Recurring Billing Virtual Terminal when everything was setup correctly.

  • Fixed an issue where manually entering a card was displaying the debit icon in error.

  • Fixed an issue where search filters were not cleared when a tab was closed and the page was reopened.

  • Fixed an issue where Billing Frequency Templates, Customer Accounts, Contract Templates are available and able to be selected and saved to a new Billing Contract.

   

Supported Browsers in MyBridgePay

The following browsers are supported in MyBridgePay when using the latest versions.

• Chrome

• MS Edge

• Firefox

V2021.003
Released August 2021

The following enhancements and fixes have been made to MyBridgePay in v2021.003

These changes are scheduled to deploy in UAT/Cert by  Monday 7/26/2021 and are currently targeted for production deployment the week of 8/30/2021 prior to 6 am ET. 

The following browsers are supported in MyBridgePay when using the latest versions.

• Chrome

• MS Edge

• Firefox

The following defects and minor enhancements were included in v2021.003 of MyBridgePay.
 

• Renamed the "Activate Custom Fields" and “Deactivate Custom Fields" permission rights under the “Custom Fields” rights menu when creating and editing Custom Roles in the Admin module to display as:

Mass Activate (Boarding API only)

▢ Configure
 

Mass Deactivate (Boarding API only)

▢ Configure

•  Removed the PO Number and Customer ID data fields from displaying on the Virtual Terminal payment form when a PAX device is selected from the DEVICE dropdown option list. When using a PAX device, these fields are processed through the PAX device and not the Virtual Terminal payment form.

• Updated the “Change other user’s password” right as a standalone permission setting specific to the Password fields on the users form in Account Management for those users who have the capability of editing users. Only users with this right enabled will be able to edit a password on the user’s form for another user.

• Revised how usernames are associated to transactions in reporting when PAX devices are used for processing transactions through the Virtual Terminal. The username field on reports will now display the username of the logged in MyBridgePay user who processed the transaction, and not the username configured on the PAX device.

• Updated the sort order display of the Payment Method column in the Open Batch Summary report for FSA Mastercard and Debit card transactions, which were previously positioned at the bottom of the report.

• Updated the .CSV file export format for Find Transactions/Advanced Search to include the Street and Zip columns.

• Updated the .CSV file export format to include the Payment Method column from Find Transactions/Advanced Search results.

• Updated the Find Transactions/Advanced Search results to include FSA Mastercard transactions as a separate payment method when FSA Mastercard is selected in the Account Type search filter.

• Added an error message to display immediately on the Virtual Terminal payment form when no active processor is present on a merchant account (either the processor setup does not exist or a processor is in a deactivated status): "An active processor does not exist on this Merchant Account"

• Updated the label name of the report column “Card Type” to “Account Type” for the reports listed below.

❖  Export file formats only:

     Declines, Transaction List, Custom Fields Transaction List, Batch Detail, and Find Transactions / Advanced Search
 

❖  UI and export file formats: Batch Summary Report

• Revised the column display order of the report export file formats to mirror the order in the UI grid display. The UI Grid displays the Account Number and Account Type columns as a combined column display followed in some cases by the Payment Method column. The export file formats will now display the column order as:

❖  Find Transaction/Advanced Search, Transaction List, and Custom Fields Transaction List

     Account Number | Account Type | Payment Method
 

❖  Declines

    Account Number | Account Type

• Added an informational statement to the Virtual Terminal payment form and to the receipts for Check transactions.

Please note this transaction is for receipt purposes only and this check will not be electronically processed.

• Updated zip code validation on Virtual Terminal payment form to include UK and Canada postal codes for Void and Refund transactions originating from Find Transactions / Advanced Search.

• Separated the previously shared “Cash” transaction permission rights of Cash-Sale, Cash-Refund from “Check” transactions. When Cash-Sale and Cash-Refund permission rights are enabled on a custom user role, only the Cash payment method will display as an option on the Virtual Terminal payment form.

• Separated the previously shared “Check” transaction permission rights of Check-Sale, Check-Refund from “Cash” transactions. When Check-Sale and Check-Refund permission rights are enabled on a custom user role, only the Check payment method will display as an option on the Virtual Terminal payment form.

• Removed the Merchant Account tab and Merchant Account User tab from displaying in Account Management to a user where the Merchant Account boarding rights are not enabled on the user’s assigned custom user role.

• Modified the Payment Method dropdown to only display Credit Card and/or ACH as payment method select options on the Virtual Terminal payment form when an activated credit card and/or ACH processor is setup for the merchant account.

• Moved the "Change Other User's Password" right from the "Administration" grouping to the “Merchant Boarding” grouping on the permission rights’ list for Custom Roles in the Admin module.

• Updated the display order of the Merchant Boarding permission rights for Custom Roles in the Admin module.

• Removed the currently unsupported “Check 21” payment method as an option on the Virtual Terminal payment form.

• Removed the currently unsupported “Check 21” permission rights from displaying as a select option on the rights list for Custom Roles in the Admin module.

• Enabled the ability to add or edit a payment method for a wallet in the Recurring Billing module on the Customer Accounts tab when a 5 digit zip code is present.

V2021.001
Released June 2021

The following enhancements and fixes have been made to MyBridgePay in v2021.001

These changes are scheduled to deploy in UAT/Cert by Wednesday 6/9/2021 and are currently targeted for production deployment the week of 6/14/2021 prior to 6 am ET. 

The following browsers are supported in MyBridgePay when using the latest versions.

• Chrome

• MS Edge

• Firefox

The following defects and minor enhancements were included in v2021.002 of MyBridgePay.
 

• Enhanced the Boarding Checklist to include "Virtual Terminal Settings" as an item for the Merchant Account boarding process flow when the setting is enabled on a Merchant Account.

• Updated the Tax Amount and Tip Amount fields to be uneditable on the Virtual Terminal payment form when the Transaction Type selected is “Refund” or when a Void/Refund transaction is initiated from Advanced Search results.

• Improved the accuracy of displayed settled batch totals by payment method in the Batch Settlement emails.

• Updated the new password instructional message on the Forgot Password Reset page for the minimum password requirements.

• Updated the Batch Detail Report export file formats to display the updated capture amount when it differs from the original authorization amount.

• Enhanced the Virtual Terminal generated receipts for Card Verification transactions to include download and email functionality.

V2021.001
Released April 2021

Enhancements

The following enhancements and fixes have been made to MyBridgePay in v2021.001

These changes are scheduled to deploy in UAT/Cert by Monday 4/20/2021 and are currently targeted for production deployment the week of 5/03/2021 prior to 6 am ET. 

Supported Browsers in MyBridgePay

The following browsers are supported in MyBridgePay when using the latest versions.

• Chrome

• MS Edge

• Firefox

Merchant Defined Custom Fields 
 

New feature which allows custom fields to be created for merchant accounts to pass through with transactions and as returned data on the newly created Custom Fields Transaction List report. Custom fields can be created by Resellers, Sales Agents, and Merchant Groups for use by their respective Merchant Accounts.

Data transmitted as a custom field is stored in the MyBridgePay database for informational purposes only and is not transmitted to the processor with a transaction request for authorization.

Adding Custom Fields Permission Rights to Custom Roles 
Resellers and Sales Agents can create a custom role with custom fields permission rights enabled to create/edit/deactivate custom fields, or can add the new Custom Fields rights to existing custom user roles for use within their organization hierarchy. The Custom Fields Template will only appear in Account Management for those users that have roles with custom fields rights enabled. Custom fields can be created/edited/deactivated at the Reseller, Sales Agent, and Merchant Group organization levels.Please note: You do not need to create custom field roles to assign to users for processing transactions or reporting purposes. If custom fields are activated on a merchant account they are visible for all users with access to the Virtual Terminal and/or Reports modules.You can select the custom field permission rights to assign to a Reseller/Sales Agent/Merchant Group user role in the Admin module.Once a custom role has been created or modified to include the custom fields permission rights, simply assign it to an applicable user.Please Note: A user must first logout of MyBridgePay and then login again for the updated role assignment to take effect.

Creating/Editing Custom Fields
Resellers, Sales Agents, and Merchant Groups can create custom fields for use within their direct merchant group/merchant account hierarchy structures. The Custom Fields Template will only appear in Account Management for those users that have the proper permissions.To create a new custom field, click the “CREATE NEW CUSTOM FIELD” button, add a label name for the custom field (which will display on both the Virtual Terminal payment form and on the Custom Fields Transaction List report), and select the field type.One example of the custom field type options that can be created is displayed below, but the full list includes:

Image Removed

Image Removed

• Text box with optional validators

• Drop down list display

• Check box

• List control box

• Radio button

Once the custom field has been created it will appear on the template where it can be activated by clicking the “Is Active” button. When a custom field is activated at the Reseller, Sales Agent, or Merchant Group level, it will be activated for all merchant accounts within that respective organizational hierarchy grouping. Conversely, if deactivated at a particular organization level, the deactivation will also occur for all merchant accounts within that organizational grouping.Example use case: Custom fields activated/deactivated at the merchant account level will only affect that merchant account, however if a custom field is activated or deactivated at the merchant group level, then all merchant accounts within that merchant group will be affected. You can always make changes at the merchant account for individualized settings, but please note that any changes made at the merchant group, sales agents, or reseller level will update all merchant accounts within the respective organizational structure.The purpose of activation/deactivation at anything above the merchant account organization level is to allow for mass activations/deactivations which is time efficient for large merchant groups that want all settings to be uniform and applied across most or all of their merchant accounts at one time.Display on Receipts OptionUp to 3 custom fields can be activated to display on the bottom portion of the Virtual Terminal receipts. This is an optional setting and does not prevent the custom field from displaying on the Virtual Terminal payment form or Custom Fields Transaction List http://report.To enable a custom field to display on transaction receipts, just click on the check box.Custom Fields on the Virtual Terminal Payment Form and ReceiptsOnce a custom field has been activated it will be visible on the Virtual Terminal payment form and if enabled to display on receipts, it will appear on the bottom portion of the Virtual Terminal transaction receipt just below the approval code.An example of two customs fields displayed on the payment form is shown below. One was created using a radio button field type, and the other using a text entry field type.Once a transaction with custom fields has been processed that receipt will display. Custom Fields Transaction List ReportOnce a custom field has been activated it will be visible on the Custom Field Transaction List report, both in the UI grid display and on the export file formats. This report has been modeled on the original Transaction List report.Please Note: The UI grid display has at this time been limited to display only up to 5 activated custom fields, however the report export file formats will display all activated custom fields for a merchant account and/or merchant group level report.The custom fields report is best displayed at a merchant account level, but is available for merchant group reporting as well.UI grid display format:Excel export file format:Fixes/Minor Enhancements The following defects and minor enhancements were included in v2021.001 of MyBridgePay

Image Removed

Image Removed

• Updated ACH transaction receipts to reflect ‘ACH’ as the entry method.

• Enhanced the behavior of configured convenience fees on the Virtual Terminal tab of a merchant account which can now be disabled and/or completely removed.

• Updated the Recurring Billing’s Virtual Terminal payment form to populate and display the street address stored with the wallet payment method when ‘Wallet’ is selected as the payment method.

• Removed the Street Address and Zip Code fields from displaying on the Virtual Terminal payment form when using PAX devices to process a transaction.

• Improved the clear function to include resetting both search results and search filters from the ‘Find Payment Method’ window in the Recurring Billing module.

• Modified the behavior of service fees configured on a merchant account to display only when a user checks "Use Manual Entry Form for This Transaction” if a PAX device is configured and defaulted on the Virtual Terminal payment form.

• Moved the Date/Time column to the first column position on the Batch Management module’s Unsettled and Settled tabs grid display. This corresponds to the default sort order set to the Date/Time column.

• Moved the Date/Time column to the first column position on Advanced Search and on the following reports: Sales, Declines, Transaction List, and Batch Detail. This corresponds to the default sort order set to the Date/Time column.

• Improved the hover verbiage on the ‘Vault’ icon of Virtual Terminal receipt to display as “Add to Wallet.”

• Expanded transaction field validation on the Virtual Terminal payment form to include the Zip Code, Invoice Number, PO Number, and Customer ID fields.

• Enhanced the data display in the report export file formats for numeric and dollar values as a custom formatted column rather than the current generic format. This allows export report files to retain their numeric formulas as they are displayed in the UI report grids.

• Improved the export file format to retain customized display options made to the grid display in the output file when columns are hidden or reorganized in both the Find Transactions/Advanced Search and Reporting

V2020.005-1
Released January 2021

Enhancements

The following enhancements and fixes have been made to MyBridgePay in v2020.005-1
These changes are scheduled to deploy to UAT/Cert on Monday 1/13/2021 and and our currently targeted for production deployment the week of 1/20/2021 prior to 6 am ET.
 

Supported Browsers in MyBridgePay

The following browsers are supported in MyBridgePay when using the latest versions.

• Chrome

• MS Edge

• Firefox

Optional Role Grading for Merchant Group Custom Roles
 

New feature which allows optional security role grading to be applied to custom roles created by Resellers and Sales Agents for the “Merchant Group User” type. Role grading allows the merchant group user’s custom role to have a user security grading setting that ranks the role from 1 (highest access) to 99 (lowest access).

Merchant Group users assigned a custom role may only create and manage roles of other merchant group users with the same grade ranking or lower. Multiple custom roles can be created with the same role grading number.

Image Removed

Role graded custom roles can exist in combination with non-graded custom roles, but is not recommended.

To enable the role grading security feature to function on applicable role graded custom roles for merchant group users, the “Use Role Grading” button must be enabled on the Merchant Group account.

Please Note: If role-graded custom roles are being used in combination with non-graded custom roles, the non-graded custom roles will be applicable to all merchant group users regardless of any graded custom roles assigned to the user.Example of usage:If two custom roles are created and assigned a role-grade:

Image Removed

• Merchant Group Admin – 1

• Merchant Group Supervisor – 2

A user assigned the Merchant Group Supervisor role will not be able to assign, create, edit, activate, or deactivate users with the Merchant Group Admin custom role.
 

New feature which allows the default system roles to be hidden from the Roles select list when creating and managing merchant group and merchant account users. When enabled, only the custom roles created by Resellers and Sales Agents will be displayed and available for selection.

The setting is located on the Business Info form.

Image Removed

Time on Receipts are Displayed in Local Time Zone of the Merchant Account

Updated the time on receipts to now display the Merchant’s local time using the configured “Time Zone” setting on a Merchant Account (located on the Business Info form).
 

Image Removed

New Dashboard Report Charts

Added two new report charts to the dashboard, Card Entry Method and Card Present vs. Card Not Present.

Image Removed

• Card entry method – breaks down the entry method used to process credit and debit card transactions.

• CP vs CNP – breaks down the volume of card present and card not present transactions processed.

 
Fixes / Minor EnhancementsThe following defects and minor enhancements were included in v2020.005-1 of MyBridgePay

• The Merchant’s local time displays on the Transaction Details popup, based on the “Time Zone” configured on the Business Info form for the Merchant Account.

• The Batch ID search feature can now be used on Batch Summary reports.

• Moved the Zip Code field under the Street Address field on the Virtual terminal payment form to improve entry flow.

• Removed the Street Address and Zip Code fields from displaying when using PAX devices to process a transaction on the Virtual Terminal payment form.

• Removed the Service Fee field from displaying on the Virtual Terminal payment form when using PAX devices and the Augusta device to process a transaction.

• Enabled the Convenience Fee field to display (when configured) on the Virtual Terminal payment form when using PAX devices and the Augusta device to process a transaction.

• Improve the error message displayed when Blind Refunds are attempted on a Merchant Account that does not have the ability to process Blind Refunds.

• Updated the “Revert Template” function in the WebLINK Configuration to immediately display changes.

• Improved the look of the “Payment type breakdown” donut charts on the Dashboard.

• Removed the “Undo Changes” icon from displaying for a confirmed transaction in Batch Management Unsettled.

• Improved the line graph display on the dashboard by compacting the data points displayed for 30 day reports to display every 5 days, and using a 10-day data point display for reports with ranges of 60 or more days.

• Improved the dashboard display interface with updated background, color scheme, and graphics.

V2020.004
Released December 2020

Enhancements

The following enhancements and fixes have been made to MyBridgePay in v2020.004
These changes were deployed to UAT/Cert on Monday 11/23/2020 and were deployed to production the week of 12/14/2020. 
 

Supported Browsers in MyBridgePay

The following browsers are supported in MyBridgePay when using the latest versions.

• Chrome

• MS Edge

• Firefox

When a new version of MyBridgePay is released to users, the following is recommended to avoid any service interruption. 
 

1. Log out of

MyBridgePay

1. Clear browser cache (optional in event errors appear)

2. Close the current browser session

3. Open new browser session

4. Log back in to 

MyBridgePay 

Account Selector

• Add a feature to display the selected organization account hierarchy, such as merchant group and/or merchant account, when an account level is selected to perform functions within a user’s hierarchy such as:
   

                   ✤ Processing transactions via the Virtual Terminal

                   ✤ Advanced Search features and Reporting

                   ✤ Batch Management

                   ✤ Recurring Billing and Wallet Management 

Image Removed

• Restyled the Account Selector to display all organization account levels in a single pane view when the “Select Account” button is clicked.

Image Removed

• Enhanced the Account Selector panel to enable search for an account without first pre-selecting the upper hierarchy, such as the ability to search by Merchant Account without prior selection of a Merchant Group. 

Image Removed

• Added the ability to enable the Card Verification transaction type via a configuration setting in Account Management, which is located on the Virtual Terminal Settings tab for a Merchant Account.

Image Removed

• Added the ability to process a Card Verification transaction through the Virtual Terminal payment form (available on select processors – see the BridgePay Gateway API-Processor Matrix for detailed information).

Image Removed

Batch Management – Unsettled

• A warning message has been added to display when the Capture Amount field of an uncaptured Authorization transaction has been cleared and left blank.

     “The Capture Amount cannot be blank. Please enter a Capture Amount to continue.”

Virtual Terminal Payment Form – Defaulted Device Display

• Enabled the automatic default of a configured device to display in the “Device” field on the Virtual Terminal payment form when only one device exists as a select option.

Image Removed

Receipts – Updates to transaction receipts where AVS/CVV Rules failures have occurred.  

• Updated the transaction receipts where transactions have been auto-reversed as per the AVS/CVV rules configuration settings for a merchant account. The receipt will now display a transaction type of “VOID” with the message displayed as:

                                                                                                      AVS/CVV Declined
 

Time-Zone Notation 

• Added “ET” to denote the time-zone display as “Eastern Time” throughout MyBridgePay. Updates have been made:

  • “ET” has been added to the Date/Time column headers for all grid displays and export file formats found in Reporting, Batch Management, and Find Transaction modules.

  • “ET” has been added to the “Date/Time” fields as “Date/Time (ET) on the Transaction Details pop-up, and page displays.

  • In Account Management, the Gateway Configuration tab for Merchant Account has been modified to display the message:

                                                                                                         Time Zone: Settlement times occur in Eastern Time only.
  

Processors tab – Highlight Active Processor  

• Emboldened the active processor on a Merchant Account for each processor type (i.e. Credit Card, ACH, Gift Card), which makes identification of the active processor easier when multiple processors are configured within the same processor type.

Fixes

The following defects were logged and fixed in v2020.004 of MyBridgePay

• Special characters now allowed as part of the Custom Role name when creating new custom roles by Resellers and Sales Agents in the Admin module.

• Contactless transactions display as “CONTACTLESS” instead of “CHIP READ” in reporting and retrieved receipts.

• Invalid Amount warning now displays if the user attempts to void an amount greater than the total balance remaining on the transaction while in Advanced Search.

• In Batch Management - a "Void Transaction Failed" message was added to display when any void transaction fails. The transaction in the unsettled grid will then return to its original status.

• When creating a new account entity at any level (Reseller, Sales Agent, Merchant Group, and Merchant Account), clicking on the Close button from the User Details tab before saving returned the user to an incorrect tab.

• On Void transaction receipts, the Email and Download receipts display the Void transaction type as "Voided" instead of "Void".  The verbiage has been updated to display as "Void".

•  The “success email sent” message is now displayed when sending an email from a Transaction Receipt.

• The service fee now displays on the emailed transaction receipts for transactions with services fees.

• On downloaded transaction receipts where a partial void was processed, the partial void amount now displays.

• On transaction receipts where a partial void was processed, the amount field now displays in parentheses (signifies voided amount).

• In Recurring Billing, when editing the Payment Method on an existing Customer Billing contract, the action of deactivating a wallet no longer deletes the wallet.

• On the export file formats for the Transaction List report and Advanced Search results, the Source column now displays the value “CHIP READ” for EMV transactions.

• The Amount and Capture Amount fields now displays on the Transaction Details pop-up for the Transaction List and Sales reports.

• On the export file formats for the Transaction List report, "Void" transactions are noted properly.

PayGuardian Desktop

PayGuardian Desktop Release Notes

PayGuardian Cloud

V2.4.13  ***Coming Soon***

• Added Contact EMV and Contactless EMV capability to the Ingenico TETRA Lane device series (Lane/3000, Lane/5000, and Lane/7000, Lane/8000). Please note: Processor EMV Certification is in progress. Check the BridgePay Device Matrix for further details.

• Added Lodging industry support to PayGuardian Cloud Mobile for the PAX A920, A80, and A60 devices.

• Added HSA/FSA Healthcare transactions support to PayGuardian Cloud Mobile for the PAX A920, A80, and A60 devices.

• Added support to include for the PAX E and Aries device series (E500, E600, E700, E800, and PAX Aries8).

• Added support for Level III transaction processing.

• Updated the Bluefin forms to align with Ingenico UIA versions.

V2.4.12

• Added the ability to process transactions with Dynamic Descriptors. Reserved for future use. Availability pending processor certification. 

• Added the ability to process transactions using the new “StoredCredential” transaction type in support of the secure storage of “Card on File” payment information of repeat customers. Reserved for future use. Availability pending processor certification. 

• Added the ‘Find_Transaction’ transaction type to the PG Cloud Mobile App for use with the PAX device series.

• Added the “getPairingCode” and “waitForTerminalPairing” calls to the PG Cloud listener which enables the Location ID to be automatically obtained without manual entry.

• Updated the “Tap, Swipe, or Insert” form to comply with the Visa “Tap to pay” program changes for Contactless EMV.

V2.4.11

• Added ACH transaction support to PG Cloud.

• Added PG Cloud support to the C# SDK.

• Added ability to pair PAX devices (A60, A80, and A920) with the MyBridgePay Virtual Terminal device manager.

• Added automatic re-start of the PG Cloud app after reboot for the PAX devices (A60, A80, and A920).

• Updated the MyBridgePay Virtual Terminal receipts to display all entry modes from the PAX devices (A60, A80, and A920).

• Added support to capture a voice authorization transaction to PG Cloud.

• Updated all CAPKS keys to the current versions.

• Fixed issue with querying the transaction details using the ‘Find_Transaction’ transaction type.

• Fixed issue where when the “Back” button was clicked on PG Cloud Mobile, the application automatically exited and closed.

V2.4.10

• Added support for the Ingenico TETRA Lane device series (Lane/3000, Lane/5000, and Lane/7000).

• Added Contactless EMV capability to the Bluefin P2PE supported Ingenico devices (iSC250, iPP320, iPP350, and ISMPv4).

• Added the SkipConfirm field for use in integrations to bypass the ‘Amount Confirmation’ prompt screen on the device.

• Added Lodging industry support.

• Added HSA/FSA Healthcare industry support.

• Added HSA/FSA Healthcare transactions support to PayGuardian Cloud Mobile for the PAX A920, A80, and A60 devices.

• Added Signature Capture support to PayGuardian Cloud Mobile for the PAX A920, A80, and A60 devices.

• Fixed issue where if ‘Declined’ or ‘No’ was selected on the ‘Confirm Amount’ form, the device was not returning to the Welcome screen.

• Fixed issue where the ‘TransIndustryType’ was not being passed with any transaction using a Token.

• Added two new optional fields to the Payment Request: TaxIndicator and HolderType, for use in integrations.

• Added the TransactionMode field to a transaction as applicable.

• Added the SettlementDelay field to the integration method.

• Added the ability to process a TokenPay transaction via an integration method.

• Added an automated verification/lookup for the current Ingenico UIA version which will prompt a user to upgrade to UIA version 19.02 if an earlier version is found.

• Added the ‘Allow Select Tender’ feature for Bluefin P2PE supported devices.

• Added the ability to create a new wallet and process transactions via a wallet via an integration.

• Updated the device prompt for ‘Gift Card’ to display as ‘Swipe’ on the Gift Card tender form.

• Removed the ability to cancel an ‘EMV swiped fallback’ transaction on the device after the EMV card has been swiped.

• Fixed issue with the signature truncation on the Bluefin P2PE Ingenico iSC250 device.

• Fixed issue where PayGuardian would lockup when the ‘Clear’ button was entered on a manual transaction and the ‘Auto Submit Transactions’ setting was not enabled in Settings.

V2.4.8

• Added the captured cardholder signature to display on receipt.

• Added optional fields to dynamically display on the receipt only when populated with a value supplied as part of a transaction request processed. Optional Fields are: PO Number, Invoice Number, Customer Account Code, Shipping Amount, and Convenience Fee.

• Added the cardholder name field to display on the receipt.

• Added the ability to print a single receipt for: Merchant copy only, Customer copy only, or copies of both receipts.

• Added option to display the suggested tip amount configuration on receipts.

• Added the ability to enter secure TokenAdd transactions manually on the device.

• Added ability to process Service Fee transactions in kiosk mode.

• Enhanced the configuration options for the Receipt template settings.

• Enhanced the installation process to auto-check for previous versions of Ingenico drivers and update to version 3.12.

• Enhanced receipt header and footer with boldface type.

• Updated various amounts fields on the receipt.

• Removed duplicated fields from the receipt: Total Amount, Auth Code, SEQ, Invoice Number, RefNum and TransID.

• Fixed an issue with device displaying ‘Approved’ after a manual transaction has been processed.

• Fixed issue where the Enable/Disable setting for ‘Display Optional Check Fields’ did not change the Sale screen for checks.

• Fixed issue where the Enable/Disable setting for ‘Turn Off Remove Card Tone’ and ‘Enable Quick Chip’ configurations were not functioning correctly on a consistent basis.

• Fixed issue where PG Cloud was not submitting a new TransactionID for EMV transactions.

• Fixed issue where the ‘Prev’ and ‘Next’ selections on the Trans Date range date picker in the History search were not displayed.

V2.4.7

• Added WiFi support for the Ingenico iSMPv4 device.

• Added support for Level II transaction processing.

• Added ability to configure the Suggested Tip Amount form to display on the Ingenico devices (iPP320, iPP350, iSC250, iSC350, iSC480, and iSMPv4).

• Added support for the ‘Find_Transaction’ request type.

• Added support to configure settings as ‘Required’ or as optional data entry input values for Zip and/or CVV2 on manually keyed and service fee transactions.

• Added support to configure and use the ‘Confirm Amount’ form to itemize the Service Fee or Convenience Fee when included as part of the transaction.

• Added ability to configure the Card Present/Card Not Present setting via the PG Cloud API.

• Added support to pass back the configured Payment and Fee Line text for Service Fee and Convenience Fee transactions.

• PG Cloud Portal – Added reCAPTCHA Version 3 (invisible CAPTCHA) to the login and registration pages.

• PG Cloud Portal – Added ability to configure the Pass Back Fee prompt.

• PG Cloud Portal – Added ability to configure WiFi support for the Ingenico iSMPv4 device.

• PG Cloud Portal – Added ability to configure the Confirm Amount form.

• PG Cloud Portal – Added ability to configure the ‘Total’ line on the Confirm Amount form.

• PG Cloud Portal – Added ability to remove a terminal from a location group.

PayGuardian iOS SDK

V2.16.0

• Resolved issues related to Rental Car Industry support

V2.15.0

• Resolved issues related to Rental Car Industry support 

V2.14.0

• Added Rental Car industry support. 

V2.13.0

• Added the ability to process transactions with Level III fields

• Added the ability to process transactions using the new "StoredCredential" transaction type in support of the secure storage of "Card on File" payment information of repeat customers. 

• Added EMV Contactless support for the ID TECH VP 3300. 

V2.12.0   No release associated with this version number

V2.11.0   No release associated with this version number

V2.10.0

• Added the ability to pass the 'TransIndustry' field when processing Tokens. 

• Added additional information to receipts based on the CVM results for EMV transactions.

• Added the ability to process Custom (user defined) fields.

• Added the ability to verify a credit card is valid using the new transaction type "TRANSACTION_TYPE_ACCOUNT_VERIFICATION".

• Added support to capture a voice authorization transaction.

• Added the auto-removal of the card insert message when EMV is disabled. 

V2.9.0

• Added the ability to pass the BridgeComm URL in the Payment Request.

• Added the ability to send the ‘TipRecipientCode’ field to the gateway.

• Added the ability to send the ‘ClerkId’ field to the gateway.

• Added the ability to create a new wallet and process transactions via a wallet.

• Added EMV Contactless and EMV QuickChip support for the ID TECH VP3300 device via the TSYS processing host.

• Added the ability to cancel a transaction for the ID TECH VP3300 device using the new ‘cancelTransaction’ method.

• Added the ability to set the timeout of a transaction in seconds using the ‘terminalTimeout’ field.

• Added the ‘SettlementDelay’ field to PayGuardian iOS.

• Added shorthand constructors for Sale, Find Transaction, Void, and Token requests.

V2.7.0

• Added ability to prompt the cardholder for entry of the billing Zip code and CVV code on Ingenico devices (iCMP, iSMP, iPP320, and iPP350).

• Added ability to override the Duplicate Checking feature when it is enabled on a merchant account using the ‘ForceOnDuplicate’ function which allows a duplicate transaction to process.

• Added ability to override the Card Present / Card Not Present configuration setting for the merchant account.

• Added ability to enable or disable ‘EMV Contactless’ on Ingenico devices (iCMP, iSMP, iPP320, and iPP350).

• Fixed issue where entering CV code values that start with a zero (i.e. 024, 0234, etc…) was not permitted.

V2.6.0

• Added ability to query transaction details using the ‘TRANSACTION_TYPE_FIND_TRANSACTION’ transaction type.

• Added ability to process Voice Authorization transactions.

• Added option to use manual entry through ISMP/ICMP terminals

• Added ability to enter a Tip Amount on Ingenico iCMP and iSMP devices.

• Added Cashback transaction support on Ingenico iCMP and iSMP devices.

• Added abilty to enforce card types for Debit/Credit transactions, which when enabled, forces transactions to process as ‘Debit’ if Debit AID is present, and transactions to process as ‘Credit’ if Credit AID is present.

• Added Level 2 transaction support.

V2.5.0

• Added EMV Quick Chip support for Ingenico iPP320, iPP350, iCMP, and iSMP devices.

• Added EMV Contactless support for Ingenico iPP320, iPP350, iCMP, and iSMP devices.

• Added EMV Debit support for the ID Tech Unipay III device, and the Ingenico iPP320, iPP350, iCMP, and iSMP devices.

• Added support for Ingenico RBA version 23.0.2 (required for EMV Contactless and EMV QuickChip) to be used with Ingenico iPP320, iPP350, iCMP, and iSMP devices.

V2.4.3

• Added support for Gift Card transaction processing (currently available: Valuetec, SparkBase, and SVS gift cards only).

• Added support for EBT transaction processing.

• Added Tag DF79 for TSYS EMV transactions.

• Added customer prompted secure manual entry capability on the Ingenico iCMP and iSMP devices for non-EMV transactions.

• Improved transaction flow on the Ingenico iCMP and iSMP devices by displaying the Welcome form on the terminal screen when a transaction has been ended.

• Improved error response handling to provide more descriptive messages in the transaction response fields.

V2.4.2

• Added capability to connect via IP address for the Ingenico iPP320 and iPP350 devices.

• Fixed issue with a memory leak caused by the cache not clearing after a transaction has been processed.

V2.2

• Recompiled the iOS framework as a static library.

• Added the Magtek uDynamo (non-EMV device).

• Added a flag as a switch to change from UAT Test to Production modes.

• Added online PIN and made updates to EMV Contactless.

• Fixed issue with XML Parser.

• Fixed issue where certain tag data caused transactions to auto-void.

PayGuardian Android SDK

V2.14.0

• Added Rental Car industry support. 

V2.13.0

• Added the ability to process transactions with Level III fields. 

• Added the ability process transactions using the new "StoredCredential" transaction type in support of the secure storage of "Card on File" payment information of repeat customers.

• Added EMV Contactless support for the ID TECH VP 3300.

 V2.12.0  No release associated with this version number 

V2.11.0  No release associated with this version number 

V2.10.0

• Added the ability to process Custom (user defined) fields. 

• Added the ability to verify a credit card is valid using the new transaction type "ACCOUNT_VERIFICATION."

• Added the ability to use the ID TECH VP3300 bluetooth device without first pairing to an Android device.

• Added the ability to disable the amount confirmation on the Ingenico devices (iCMP, iSMP, iPP320, and iPP350). 

V2.9.0

• Added the ability to send the ‘TipRecipientCode’ field to the gateway.

• Added the ‘SettlementDelay’ field to PayGuardian Android.

• Added two new optional fields to the Payment Request: TaxIndicator and HolderType.

• Added the ability to create a new wallet and process transactions via a wallet.

• Added FSA/HSA Healthcare industry support.

• Added Lodging industry support.

• Added ACH transaction support.

• Added support to process ‘Unknown’ tender type.

• Added the ability to pass the BridgeComm URL in the Payment Request.

V2.8.0

• Added the ability to cancel a transaction on the Process Secure Payments screen using the ‘Cancel Transaction’ button.

• Added EMV Contactless and EMV QuickChip support for the IDTech Vivopay 3300 device via the TSYS processing host.

• Added 64-bit support to PayGuardian Android.

V2.7.0

• Added ability to process Service Fee and Convenience Fee transactions.

• Added ability to prompt the cardholder for entry of the billing Zip code and CVV code on Ingenico devices (iCMP, iSMP, iPP320, and iPP350).

• Added ability to override the Card Present / Card Not Present configuration setting for the merchant account.

• Added ability to override the Duplicate Checking feature when it is enabled on a merchant account using the ‘ForceOnDuplicate’ function which allows a duplicate transaction to process.

• Added ability to enable or disable ‘EMV Contactless’ on Ingenico devices (iCMP, iSMP, iPP320, and iPP350).  

V2.6.0

• Added ability to enter a Tip Amount on Ingenico devices (iCMP, iSMP, iPP320, and iPP350).

• Added Cashback transaction support on Ingenico devices (iCMP, iSMP, iPP320, and iPP350).

• Added ability to process Voice Authorization transactions.

• Added AVS (Address Verification Service) support.

• Added Level 2 transaction support.

• Added abilty to enforce card types for Debit/Credit transactions, which when enabled, forces transactions to process as ‘Debit’ if Debit AID is present, and transactions to process as ‘Credit’ if Credit AID is present.

V2.5.0

• Added support to query transaction details using the ‘Find_Transaction’ transaction type.

• Added support to include the Industry Type with a transaction request. Supported industries are: RETAIL, RESTAURANT, ECOMMERCE, and DIRECT_MARKETING.

• Added 2 new transaction response fields:  CardModifier and CardClass.

• Added device access permissions popup to accept/decline ability for PayGuardian to access photos, media, and/or files on the device.

V2.4.0

• Added dip enforcement functionality for EMV-capable cards, to the Ingenico iPP320, iPP350, iCMP, iSMP devices. . If an EMV chip card is swiped, the card holder will be prompted to swipe 3 times, warning them that the card is EMV capable and should be dipped after each swipe attempt. On the 4^th swipe attempt, the transaction will be processed.

• Added Tip Adjustment support for a Credit Card ‘Sale’ transaction. The Adjustment transaction allows the Tip Amount element within the sale transaction to be updated with a new Tip amount.

• Added Billing fields: On each transaction, PayGuardian Android will query the device for its make, model, firmware version, kernel version, and serial number.

• Added support for EBT Cash Benefit and EBT Food Stamp transactions.

• Added support for the IDTech Minismart II and Vivopay 3300 for MSR and EMV transaction processing.

• Added EMV Quick chip, EMV Debit, and EMV Contactless support for the Ingenico iPP320, iPP350, iCMP, and iSMP devices. (Requires RBA upgrade to version 23.0.2 and Contact XML push to devices).

• Added select option for EMV Quick Chip or EMV Traditional processing configuration. To enable EMV Quick Chip processing, ‘enableQuickChip’ must be set to true in the PaymentRequest object. By default, it is set to false (currently available for Ingenico devices only).

• Added logging functionality. Logs are available in local file storage and can be accessed under: 

• Files-> Internal/External storage-> PG logs -> txt file with date and time.

• Added capability to connect the Development (DEV) environment via a VPN connection.

• Added Secure Manual Entry functionality for Ingenico iPP320, iPP350, iCMP, and iSMP devices.

• Updated the payment response fields to return additional card information such as CardClass, CardType, and CardModifier.

• Fixed issue with transaction requests not timing out for the Ingenico iPP320, iPP350, iCMP, and iSMP devices.

• Added EMV Fallback functionality to mag stripe swipe, when an EMV Chip read error occurs for the Ingenico iPP320, iPP350, iCMP, and iSMP devices.

• Fixed issue with the entry method not functioning properly. The Entry mode is set to Tap, Swipe, or ChipRead based on the entry method.

• Fixed issue with NFC contactless, where the device prompts to ‘Insert Card’ for the Ingenico iPP320, iPP350, iCMP, and iSMP devices.

• Fixed issue where all EMV transactions fail consecutively, when there is a declined transaction.

V2.2

• Added the PayGuardian Desktop EMV Parser to replace existing inconsistent parser code.

• Reset the view to return to the Start screen after transaction and also after an exception occurs.

• Added enhanced logging to capture every exception that occurs.

• Added the Global Exception Handler.

• Added a ReferenceID field to return the same populated value in the message response when populated initially.

• Added URI method as an integration option.

• Fixed the issue where PayGuardian would not relaunch after the original transaction request was initiated.

WebLINK

The following enhancements were made in WebLINK 3 v3.10 

WebLINK 3 has been modified to support the military state codes :  
 

• AE (Armed Forces Europe, t he Middle East and Africa)  

• AP (Armed Forces Pacific)  

• AA (Armed Forces Americas, excluding Canada).  

It has also been modified to support the 13 provinces and territories of Canada:  

• AB – Alberta  

• BC – British Columbia  

• MB – Manitoba  

• NB – New Brunswick  

• NL – Newfoundland and Labrador  

• NS – Nova Scotia  

• NT – Northwest Territories  

• NU – Nunavut  

• ON – Ontario  

• PE – Prince Edward Island  

• QC – Quebec  

• SK – Saskatchewan  

• YT – Yukon 

Enhanced Logging for Support

WebLINK 3 has been modified to provide our support teams with m ore information regarding  transactions processed in order to provide our customers with b etter technical support. 
 

Fixes

The following corrections have been applied to WebLINK 3 in v3. 10. 
 

Error Response Handling when Using Combined Service Fee Structure

Users of our previous enhancement for Service Fees, were experiencing issues in receiving responses when an error occurred within the gateway due to WebLINK not properly handling the response data it received. This issue has been resolved in v3.10.