This page describes the different integration solutions that BridgerPay offers.

BridgerPay currently offers several solutions to process payments:

Embed vs MPI

We offer you two solutions, which, depending on your case, can be employed separately or together. First, Embed WebSDK, is a Cashier widget: a front-end solution embedded in your website ("script") or located in an arbitrary web resource ("iframe"). It implies that you provide some known information on a customer and their transaction (e.g., the first and last name and other data based on their profile, and the purchase price). After that, the customer enters the missing information (e.g., credit card credentials) by using the Cashier widget.
Second, MPI is about server-to-server deposits. You collect all the information of a customer, including the credit card credentials, by using your own front-end solution, and then transmit it to BridgerPay. Additionally, this approach supports only the debit and credit card payment methods.

Direct Embed vs API (Secured Embed)

If you choose to employ our Cashier widget, you have two ways to do this: Direct Embed or API (Secure Embed). The former is simpler and consists of only one step. The latter is more secure and takes three steps to implement. When integrating the Direct Embed scheme, you launch a JS code with your cashier key (provided by BridgerPay) and other parameters to create a Cashier session. It doesn't require access to the API methods. When integrating the API (Secure Embed) scheme, you need to Authorize in BridgerPay to generate a server-side (cashier) token, which will encapsulate all the information for creating a more secure Cashier session. Only after the token is created do you launch a JS code with the cashier key and cashier token. Upon integration, customers interact with a Cashier widget: they select a payment method, enter their information, confirm a purchase, see the result of their deposit, etc.

API methods

Our API methods are grouped according to their purpose. You can see the currently available ones in the preceding figure, and we are working on providing you with even more. For now, these are:
  • Authorization to log in to the BridgerPay system.
  • Server session initialization to create a Cashier and server sessions to later accept a customer's deposit.
  • Get transaction by Order ID to retrieve the details of the transaction based on the Merchant Order Id.
  • Refunds to initiate a partial or full refund for a customer.
  • Payouts to transfer funds you owe a customer according to your mutual agreement: insurance compensation, prize, etc.
  • PreAuth/ Void / Capture to put an amount on hold and later to Void or Capture the payment.

Who is involved

There are four parties involved in BridgerPay's business processes: 1. Your customer 2. You (the Merchant) 3. BridgerPay 4. Payment Service Providers (PSPs) Additionally, a Cashier widget, if applicable, can be included in this set too (see the figure below).

Embed Solution process:

Embed Solution

MPI Solution process:

MPI Solution