/
FE v24.9

FE v24.9

MyBridgePay Enhancements

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

  1. Convenience Fee and Service Fee Setup Defaulted in API Transactions

  1. Minor Enhancements / Fixes

  1. API Enhancements

1. Convenience Fee and Service Fee Setup Defaulted in API Transaction

An API transaction that excludes a Convenience or Service Fee in the payload will now automatically use what has been setup in the Gateway Configuration tab of MyBridgePay Account Management Module.  For example, if a user sets a Service Fee in Gateway Configuration and then processes a transaction using the Transaction API or BridgeComm API, the Service Fee setup in Gateway Configuration tab of MyBridgePay Account Management Module, will be processed on the transaction.  If the Transaction API or BridgeComm API payload includes a Service Fee, it will take priority and use the information provided in the payload rather than what has been setup in Gateway Configuration tab of MyBridgePay Account Management Module.  This is done in support of current integrations.  This new feature is supported for both Convenience and Service Fee configuration and has been updated on both BridgeComm API and Transaction API payment requests.  Setting up a configured fee is only available to Reseller and Sales Agent users.

The following applications will follow these new Convenience Fee/Service Fee rules:

  • Transaction API

  • BridgeComm API

  • PayGuardian Cloud

  • PayGuardian Desktop

  • Hosted Payment Page

  • Bulk Transaction API

  • Import Transactions

  • Recurring Billing

  • Weblink

 

To set a Convenience or Service Fee in MyBridgePay[CH4] , navigate to the Account Management Module, drill down to a Merchant Account, click the Gateway Configuration tab and edit the Optional Fee Type section with desired configuration and save.  All API transactions made to this Merchant Account will now automatically include this fee regardless if the fee is not sent in the payload.

image-20250221-180619.png
image-20250221-180826.png

Supported Scenarios

  • Fee not setup in Gateway Configuration tab and Fee is sent in the API payload/application

    • Fee from the API payload will be processed

  • Fee setup in Gateway Configuration tab and Fee is sent in the API payload/application

    • Fee from the API payload will be processed

  • Fee setup in Gateway Configuration tab and Fee is not sent in the API payload/application

    • Fee from the Gateway Configuration tab will be processed

  • Fee not setup in Gateway Configuration tab and Fee is not sent in the API payload/application

  • No Fee processed 

2. Minor Enhancements & Fixes

  • Admin Users passwords expire every 90 days.  Admin Users with expired passwords will be prompted to reset their password on the next login.

  • Updated the required MyBridgePay password length to between 12 and 64 characters.

  • Admin Users now prompted to reset their password immediately when expired.

  • Enhanced WebSecurity logs.

  • Password reset emails will now display the subject of “Gateway Password Reset.” 

3.    API Enhancements 

All APIs

  • Updated the APIs to return an error message if an Admin user’s password is expired. 

BridgeComm

  • As stated above in section #1, transaction requests can omit Convenience or Service Fees in the payload and the transaction will use what has been saved in the MyBridgePay Account Management Module > Gateway Configuration  tab for the transaction.  This first requires set up of the desired fee structure in MyBridgePay Account Management Module > Gateway Configuration.  Requests including a Convenience or Service Fee in the payload have priority and will use the payload fee data instead of what is saved in the MyBridgePay Account Management.

Transaction API

  • As stated above in section #1, transaction requests can omit Convenience or Service Fees in the payload and the transaction will use what has been saved in MyBridgePay Account Management > Gateway Configuration for the transaction.  This first requires setting up the desired fee structure in MyBridgePay Account Management Module > Gateway Configuration.  Requests including a Convenience or Service Fee in the payload have priority and will use the payload fee data instead of what is saved in the MyBridgePay Account Management Module.

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