FE 25.2

FE 25.2

The following enhancements and fixes were made to MyBridgePay in v25.2. These changes are scheduled for production deployment in July/August 2025.

  1. Support Canadian Addresses in MBPUI User Management

  1. Separate AVS Settings for Address and ZIP

  1. Minor Enhancements / Fixes

  1. API Enhancements

1. Support Canadian Addresses in MBPUI User Management

BridgePay is now allowing merchants to use Canadian addresses in boarding new Reseller, Sales Agent, Merchant Group and Merchant Account users.

In Account Management, under User Details, you are able to create and edit all users to have Canadian addresses.

image-20250729-133010.png

In boarding, you will notice two country options, United States or Canada.

image-20250729-133030.png

Choosing Canada, changes the dropdown of State/Province to display Canadian provinces.

image-20250729-133048.png

In kind, when choosing Canada and a Canadian province, your postal code must be presented in the correct format (A1A 1A1).

The same edits can also be completed in the Administration section of MyBridgePay. Once you find the user you wish to edit and click the Edit button on the left-most side of the results, the ability to edit the user appears.

image-20250729-133104.png

Under Country, you are able to choose United States or Canada.

image-20250729-133115.png

After choosing Canada, you will be able to choose the appropriate Province.

image-20250729-133131.png

Much like in Account Management, if a Canadian province is used, your postal code must be presented in the correct format (A1A 1A1).

2. Separate AVS Settings for Address and ZIP

We have made significant upgrades to our AVS settings within the gateway with this release.

image-20250729-133149.png

Previously, “Street Address does not match” and “ZIP Code does not match” were combined together. These have been separated and now allow both of these to be checked independently.

image-20250729-134848.png

Now that these are able to be independently checked, the AVS responses have also been updated accordingly.

  • Street Address Does not match

    • 46 - Street Address doesn’t match, 5-digit ZIP matches

    • 47 - Street Address doesn’t match, 9-digit ZIP matches

  • ZIP Code Does not match

    • 4D - Street address matches, ZIP does not match

  • Street Address and ZIP does not match

    • 45 - Street address and ZIP don’t match

3. Minor Enhancements / Fixes 

  • Added the ability to configure, manage and see Virtual Terminal and API Custom Fields in MyBridgePay

    • Transaction and Organization Custom Fields types only

    • Wallet and Contract Custom Fields are not supported in the MyBridgePay Portal currently

  • Resolved an issue where incorrect Merchant Accounts would be displayed using the Custom Fields Transaction List report

  • Resolved a spelling error in the frequency template of Recurring Billing

  • Resolved an issue where MyBridgePay allowed mismatches between the password and confirmed password fields in Account Management

  • Resolved an issue where Merchant Group users were unable to change their Merchant Account access in MyBridgePay

  • Resolved an issue where Merchant Group users were unable to be edited in MyBridgePay

  • Resolved an issue where users with Recurring Billing access were unable to save or edit Billing Frequency in MyBridgePay

4. API Enhancements

Boarding API

  • Resolved an issue where custom fields were unable to be created

  • Updated Failed CreateTokePayAuthentication & UpdateTokenPayAuthentication request messages due to not meeting PrivateKey rules

    • New Message Reads: PrivateKey requirements not met. Must be at least 6 characters, including one uppercase letter, one lowercase letter, one digit and one non-alphanumeric character

Transaction API

  • Added merchantAdviceCode to responses if provided by Java Payment Service in the Serv Fee response block

    • Codes added

      • 004 or comparative request responses (Sale, Sale-Auth)

      • 023 or comparative request responses (Find Transaction)

  • Resolved an issue where the Find Transactions request was returning invalid amounts on transactions with tips

Wallet API

  • Updated the CreateWalletView call to only work when a CustomerWalletId only includes the correct characters that are allowed. 

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 ©2025