MyBridgePay Enhancements

The following enhancements and fixes were made to MyBridgePay in v24.10. These changes are scheduled for production deployment in April 2025.

1. Email Notifications for Lockouts and Password Changes

2. Successful and Failed URL Updates for Hosted Payments Page

3. Minor Enhancements

4. API Enhancements

1. Email Notifications for Lockouts and Password Changes

With this release, we have modified how we communicate lockouts and password changes within MyBridgePay. If, for any reason, a user is locked out of their MyBridgePay account, the user will receive two forms of communication.

First, after a user is locked out, the user will receive this message on MyBridgePay.

Open

In tandem with this message, the user also receives an email noting their lockout.

Open

Additionally, when the user resets their password, they receive a confirmation email when the password is changed.

Open

2. Successful and Failed URL Updates for Hosted Payments Page

We have added an extra layer of validation for successful and failed payments made through the Hosted Payments Page. Previously, on successful and failed URLs, it was difficult for an integrator to track the success or failure of the payment made. With this release, BridgePay will include the transaction’s reference number at the end of the success and failure URL for easy tracking. Below are examples of how this will appear to integrators.

Successful Payment:

{Successful Payment URL}/?referenceNumber=4592909104

Failed Payment:

{Failed Payment URL}/?referenceNumber=4592909104

3. Minor Enhancements

•  Updated Forgot Password Page Copyright logo to reflect current year

• Reporting Updates to properly reflect Push Payments transaction type

  • Sales Report

  • Transaction Details

  • Current Open Batch Summary

  • Transaction Summary

  • Reporting API

• Resolved an issue where Recurring Billing Service would return zero on “GetNumberOfContractsToProcess” call

• Resolved an issue where transaction details would not appear when clicking on a transaction

• Changed validation of Successful and Failed URL field for Hosted Payments Page to no longer allow a port number on the URL

4. API Enhancements

To view the most up-to-date API guides in the BridgePay Development Center.

Transaction API

• Updated Response Data to include Bin Data in Multiple Request Types (Sale, Sale-Auth, Tokenize Credit Card & Card Verification)

  • cardBIN (Up to the first 8 digits of the card)

  • cardType (Visa, Mastercard, etc)

  • cardIdentifier (Displays whether the card is a debit or credit card)

• Up-to-date Transaction API documentation

BridgeComm

• Updated 001, 004, and 015 Response Data to include the following Bin Data

  • CardBIN (Up to the first 8 digits of the card)

  • CardType (Visa, Mastercard, etc)

  • CardIdentifier (Displays whether the card is a debit or credit card)

• Up-to-date BridgeComm API documentation

Reporting API

• Updated  Response Data to include Bin Data Response Block

  • CardBIN (Up to the first 8 digits of the card)

  • CardIdentifier (Displays whether the card is a debit or credit card)

• Up-to-date Reporting API documentation

Supported Browsers in MyBridgePay

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

• Google Chrome

• Microsoft Edge

• Mozilla Firefox