FE v2022.002

Owned by Angela Nicgorski (Unlicensed)
Last updated: Jul 12, 2023 by Mark Mauer
11 min read

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.

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)

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.

Merchant Group Level (Account Management)

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.
 

Merchant Account Level (Account Management)

 

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.

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.

"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.

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

Property of BridgePay Network Solution ©2024