The payment processor MPI (Mercantile Payments Inc.) uses the payment gateway BridgePay in order to connect to ThinkReservations. It works like this:
ThinkReservations <-> BridgePay <-> MPI
Due to an issue with BridgePay, MPI is migrating clients to an alternate payment gateway. To minimize disruption for merchants, MPI has made the decision to move all mutual clients to Authorize.net so they can resume processing as quickly as possible. Your payment processor will still be MPI.
The expectation is that clients will eventually return to BridgePay.
This article covers the process and important information that you will need to know to handle special situations:
Step 1: Learn ThinkReservations' role in payment processing
First, it's essential to understand that ThinkReservations is not a gateway, processor, or merchant service provider. That means that ThinkReservations isn't responsible for any of the functions associated with processing credit and debit cards, including validation, charging refunding, voiding, or storing customer card data.
Click here for more on how this works
Click here for more on how this works
ThinkReservations connects to a processor or gateway to send and receive information.
Sending Data:
ThinkReservations will securely send card information to your gateway or processor so that it can be validated and retained. When you perform a transaction, ThinkReservations sends information to the gateway or processor so that card can be charged, refunded, or voided.
Receiving Data:
The connected processor gateway will send back information on the status of the transaction (submitted/settled), and if the processor runs into an error, they send us the error information. We expose the status of the transaction in the Status column of the Payments table. If there is an error sent to us, we alert you in the form of a popup.
ThinkPayments:
Technically, ThinkReservations role in payment processing will change with the upcoming launch of our own payment solution: ThinkPayments. This option will be available in or near March, 2026.
Step 2: Understand you will lose access to retained cards
This is something we want to be clear about. As mentioned in Step 1, ThinkReservations doesn't store any card data. ThinkReservations uses something called tokenization that allows us to tell the gateway which card they have in their vault to charge. You can only be connected to one payment processor or gateway at a time. When you disconnect from BridePay, ThinkReservations no longer has access, and the tokens become useless.
This becomes a potential problem in two situations:
A future reservation is a no-show. You don't have the card on file anymore to charge a cancellation fee, and they won't provide one to you on the phone to charge the fee.
This is mitigated by reaching out to MPI to acquire the full credit card number. Then you can take that number, retain in ThinkReservations, and charge the cancellation fee or penalty via Authorize.net in ThinkReservations.
A past reservation needs a refund. You don't have a "linked transaction" anymore to issue the refund.
This is mitigated by giving the guest their money back via an alternate method. The most common (and least expensive) is to send the guest a check. See Refunding via a check for instructions.
Step 3: ThinkReservations is notified that your Authorize.net account is ready
ThinkReservations is CC'd on MPI's email about the Authorize.net account details. Our team reviews these as they come in and uses this information to make the switch for you in your account.
Step 4: ThinkReservations makes the switch
The process on our side looks like this:
The BridgePay gateway is disconnected.
All previously retained cards are automatically removed. (This does not impact existing transactions.)
We will connect the new Authorize.net account to ThinkReservations.
We update your booking engine settings to allow guests to book, rather than asking them to call you.
We confirm to you that the connection has been made via email.
You will receive an email from Authorize.net confirming the transaction (and each subsequent transaction, unless disabled -reach out to Authorize.net on how to disable if you wish to do so).
Step 5: Run a test transaction
When you can, please retain a card, charge a small amount, and then void the transaction.
Frequently Asked Questions
How do you refund a charge made on your old processor?
It's not possible to "refund" these transactions because they're tied directly to the BridgePay gateway. As ThinkReservations doesn't have access to that account after the switch, the refund cannot be completed as normal. You will need to use an alternate method to return funds to your guests. The most common is to send a check. Another option may be to issue a gift certificate as a type of credit or voucher. You may be able to use what is called a "blind credit", where you charge a credit card in the negative.
How do I get access to a credit card I previously retained with MPI?
Please call MPI during normal business hours to ask for the full card details. Once you have these full card details, you will be able to retain the card in ThinkReservations so that it's stored in the new Authorize.net gateway. Once you have retained the card in ThinkReservations, you will be able to charge it as normal.
MPI will confirm your identity and request the last four digits of the card so they can look it up for you.
Where can I learn more about the BridgePay outage?
BridgePay has posted its status page here:
How do I contact MPI?
MPI - Mercantile Processing, Inc.
877-508-2831
Wynn Salisch - Casablanca Ventures
(203) 253-7259