FE v2024.003

The following enhancements and fixes were made to MyBridgePay in v2024.003. These changes are scheduled for production deployment in June 2024.

1. Automatic Voiding and Refunding Service Fees

2. Minor Enhancements & Fixes

3. API Enhancements

1. Automatic Voiding and Refunding Service Fees

When voiding or refunding a transaction that has an associated service fee, the gateway will now automatically void or refund the service fee without a user having to perform this separately in the MyBridgePay Portal or in an API request. This works for obth Credit Card and ACH Service Fees.

Voiding a transaction is required when the transaction’s batch is not settled.  Refunding a transaction is required when the transaction’s batch is settled.

In the Account Management module, the fee settings have now moved to Gateway Configuration from Virtual Terminal Settings. There is also a toggle at the bottom for automatically refunding service fees.  If enabled, all associated service fees will be automatically refunded when the initial transaction is refunded.  Be advised that the Automatically Refund Service Fees option needs to be enabled if service fees are passing through an integration and not just the Virtual Terminal in order for the automatic refunding of service fee transactions.

Open

After the transaction has been processed and a void or refund is needed for that transaction, follow the same steps as before. First, go to Find Transactions and search for the transaction that needs to be voided/refunded.  The following steps are for voiding a transaction.

Open

When pressing the red trash can to the far left of the transaction, the Virtual Terminal will appear.

Clicking Process and confirm to process the void.

Pressing Confirm will complete the void for the transaction in question. Because there was a Service fee associated with the payment, the service fee was also automatically voided.

2. Minor Enhancements & Fixes

• Upgraded reCAPTCHA to version 3 (No more finding bicycles or cars when logging into the MyBridgePay Portal).

• Added the ability to filter the lists for accounts/users to only display active accounts/users in Account Management.

• Included User ID when receiving the Forgot Password email.

• Updated reports so set Start Dates persist when changing Select Account information.

• Added a Total Summary to the Transaction Summary report.

• Resolved issue that prevented addition of Vantiv and Elavon processors.

• Added Puerto Rico as a State option for WebLINK3.

• Added a display active/failed contracts toggle in Recurring Billing to display all contracts regardless of page view.

• Service Fee and Convenience Fee setup has now moved from Processing Applications to Gateway Configuration.

• Resolved an issue where user sessions would time out and cause login issues.

• Resolved an issue where Custom Fields were not saving on a newly created merchant account when using a sales agent.

• Resolved an issue where edited fields on a role were not cleared when the role was not saved.

• Resolved a minor issue where the text color was incorrect on voided transaction in batch management.

• Resolved an issue where validation text was not appearing on all required fields when setting up an account or user in Account Management.

• Resolved an issue were card present transactions processed via the Transaction API were displaying the last 3 digits of the card number instead of 4 digits in Find Transactions.

• Resolved an issue where the Save button was accessible when all required fields had not been filled out when adding a processor to a merchant account.

• Resolved an issue where changing the state on the TSYS processor settings form did not allow saving the processor settings.

3. API Enhancements

Boarding API

• Added an error message when attempting to add more than 999 Merchant Accounts to a Merchant Group.  999 is the maximum number of Merchant Accounts allowed in a single Merchant Group.

• Allow revoking a Sales Agent’s user access to all merchant accounts under a specific merchant group using one API call.  Formerly, integrators would need to make a call per merchant group.

Reporting API

• Added Tax Amount to transaction response data.

Recurring Billing API

• If you are using scheduled payments within the Recurring Billing API, failed scheduled payments will now count towards the max failures set on the contract.  They were not prior to this release.  This does not change the calls within the Recurring Billing API.  It only changes logic.

Transaction API

• When voiding or refunding a transaction that has an associated service fee, the gateway will now automatically void or refund the service fee without having to perform this separately (Automatic refunding requires a MyBridgePay setting to be enabled first).

• Added organizationId support.  Integrator can now send organizationId in requests in place of merchantCode & merchantAccountCode for all requests.

• Added a new request type Get Fee Amount.  This request allows you to setup a fee in MyBridgePay (AccountManagement >> Merchant Account >> Gateway Configuration) and then make a request in the Transaction API to return the fee amount.  This is very useful when using a percentage fee type.

• Enhanced the Find_Transaction call by allowing transactionCode, purchaseToken, merchantAccountCode & invoiceNumber.

• Added Routing Number to the Transaction Response when processing an ACH through the API.

BridgeComm API

• When voiding or refunding a transaction that has an associated service fee, the gateway will now automatically void or refund the service fee without having to perform this separately (Automatic refunding requires a MyBridgePay setting to be enabled first).

• Added OrganizationId support.  Integrator can now send OrganizationId in requests in place of MerchantCode & MerchantAccountCode for all requests.

• Added a new request type (026) Get Fee Amount.  This request allows you to setup a fee in MyBridgePay (AccountManagement >> Merchant Account >> Gateway Configuration) and then make a request in BridgeComm to return the fee amount.  This is very useful when using a percentage fee type.

• Added additional response codes.  All current response codes can be found here: https://bridgepaynetwork.atlassian.net/wiki/spaces/DC/pages/246644751

  • Some Response Codes were updated

  • 20005 P2PE Service Error updated to 80018 P2PE Service Error

  • 90002 Unauthorized Access updated to 80019 Unauthorized Access

  • 90003 Custom Field Name Does Not Exist updated to 80020  Custom Field Name Does Not Exist

  • 90004 The request was invalid or unreadable updated to 80021 The request was invalid or unreadable

  • 90005 Missing Required Custom Field Data updated to 80022 Missing Required Custom Field Data

  • 90006 Invalid Custom Field Data updated to 80023 Invalid Custom Field Data

  • 90007 Cannot Append Custom Field Data updated to 80024 Cannot Append Custom Field Data

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

• Google Chrome

• Microsoft Edge

• Mozilla Firefox

Table of Contents: