FE v2023.003

Owned by Mark Mauer, created
Last updated: Aug 23, 2023
3 min read

MyBridgePay Enhancements

The following enhancements and fixes were made to MyBridgePay in v2023.003. These changes are scheduled for production deployment August 7th 2023 thru August 18th 2023.

  1. Recurring Billing Active Contracts Filter

  2. Transaction API Card Present Transactions

  3. Existing Customer Account Search

  4. Minor Enhancements & Fixes

  5. API Enhancements

1. Recurring Billing Active Contracts Filter

We have updated the Recurring Billing reports to include an Active Contracts filter to allow sorting both your active and failed contracts.

 

When you check the toggle for active contracts, all active contracts on your current page will be displayed. Note that this will not automatically sort all of your active billing contracts. If you wish to sort more of your contracts, please change the number of active records you wish to display on your screen to a larger value.

 

Alternatively, when you toggle all failed contracts accounts, your current page will display just failed contracts. Note that this will not automatically sort all of your failed billing contracts. If you wish to sort more of your contracts, please change the number of active records you wish to display on your screen to a larger value.

2. Transaction API Card Present Transactions

We have updated the RESTful Transaction API to support card present transactions.  We have updated the integrations guide with the new calls.  You can find the PostMan API documentation in our Developer Center or a direct link here.

3. Existing Customer Account Search

We have added the ability to search for an existing Customer Account Name in the Vault Payment Method screen to allow users to easily search for a specific record through a large list of vaulted payments.

4. Minor Enhancements & Fixes

Minor Enhancements

  • Added Help Text to the No End Date functionality of Billing Contracts in Recurring Billing

  • Added Customer Account Name to the Recurring Billing VT when searching for a payment method

Fixes

  • Updated TokenPay to allow integrators to remove an existing event listener

  • Updated TokenPay to correctly validate ZIP code

  • Updated TokenPay to allow for 12 characters to be entered as a bank account number

  • Updated TokenPay’s routing number behavior to always display

5. API Enhancements

  • BridgeComm

    • Added cardClass field to the Find Transactions call response

  • Transaction API

    • Added support for the following transaction types

      • Bar Tab

      • Increment

      • Tip Adjustment

      • TokenPay

    • Added cardClass field to the Find Transactions call response

  • Boarding API

    • Added RoleID and UserType to the allowed request fields when making the GetUsers call

      • If RoleID is included in the request then the returned data will only include users who have that assigned RoleID.

      • If a UserType is included in the request then the returned data will only include users of that UserType.

      • If both RoleID and UserType is included in the request then the returned data will only include users that are both assigned that RoleID and UserType passed.

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