The following enhancements and fixes were made to MyBridgePay in v24.5. These changes are scheduled for production deployment in October 2024.

1. Threshold Minimums

2. Visa Platform Connect (VPC) Processor

3. Minor Enhancements / Fixes

4. API Enhancements

1. Threshold Minimums

 We have made updates to our Threshold Controls by adding two new controls for Threshold Minimums. The addition of a Minimum Single Sale / Sale-Auth and Minimum Single Refund.

Open

Options Explanation

Minimum Single Sale / Sale-Auth

The dollar value minimum of a single sale or sale-auth transactions.
Enter the dollar amount minimum as the lowest value allowed as a payment. Any attempt to make a single sale / sale-auth below the entered amount will result in a decline.

Minimum Single Refund

The dollar value minimum of a single refund transactions.
Enter the dollar amount minimum as the lowest value allowed as a refund. Any attempt to make a single refund below the entered amount will result in a decline.

 In addition, the following BridgeComm API and MyBridgePay response code for declines due to Single Sale / Sale-Auth and Single Refund Threshold Minimum has been created.

• 30112 - Single Min Threshold Not Reached

2. Visa Platform Connect (VPC) Processor

Visa Platform Connect (VPC) is now an available processor in the BridgePay Gateway. Resellers will simply need to add VPC as credit card processor in the MyBridgePay Boarding Portal. VPC will supply the merchant with a Connection String that is entered into the MyBridgePay Boarding Portal. A VPC merchant account will need to be setup with VPC. If you are interested in using VPC as a credit card processor, contact sales@bridgepaynetwork.com.

 Account Management >> Navigate to Merchant Account >> Processors >> Create Processor

Open

The addition of a VPC processor can also be accomplished through the Boarding API.

3. Minor Enhancements & Fixes

• Allow "_-@." when creating a username

• Resolved issue where the Find Transactions report would not show any data

• Resolved issue where the Custom Fields Transaction List report would not show any data

• Enhancements to improve login speed

• Updated TokenPay to be able to accept Canadian Provinces and Postal Codes

• Updated WebLink3 to be able to accept Canadian Provinces and Postal Codes

• Updated TokenPay to display “Card Number” instead of “Credit Card Number” on the card number collection field

4. API Enhancements

 Boarding API

• Allow special characters in usernames when creating a user “_-@.”

BridgeComm

• Allow special characters in usernames when processing a payment “_-@.”

• Allow for the BridgePay card token to be returned on Activation, Reactivation and Deactivation of gift cards

• Added the ability to pass transactionCode and InvoiceNumber into the gateway on Activation, Reactivation and Deactivation of gift cards

• Allow a surcharge to be added in payment requests using the “FeeIsSurcharge” field

Reporting API

• Return “FeeIsSurcharge” in responses

Transaction API

• Add Routing Number to the transaction response when processing an ACH transaction via the TokenPay PaymentMethodToken Transaction API Request

• Allow a surcharge to be added in payment requests using the “feeIsSurcharge” field

• Allow for the BridgePay card token to be returned on Activation, Reactivation and Deactivation of gift cards

• Allow for transactionCode and InvoiceNumber to pass to BridgeComm for Activation, Reactivation, and Deactivation of gift cards

Wallet API

• Enhanced GetWalletViews call to return both active and deactivated wallets

Supported Browsers in MyBridgePay

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

• Google Chrome

• Microsoft Edge

• Mozilla Firefox