Overview
This page provides an overview of how a shopper, merchant, BridgerPay, and PSP cooperate upon integrating the MPI solution.
The API SDK is an alternative solution to connect BridgerPay and allows your business to accept payments from your customers and leverage multiple payment methods to meet the needs of different people and geographies. With API SDK you will use your own front-end solution to collect all the information and then call the "POST MPI deposit request" method to process the transaction. After that, you will show the customer the appropriate web page depending on the acquirer’s response (e.g., 3D secure dialog, successful or declined transaction, etc.)
Server-side deposit flow diagram
i. The customer enters their information on your front-end to make a payment.
ii. You call the "POST Login" method to log in to BridgerPay and get the access token.
1. You initiate the transaction by calling the "POST MPI deposit request" method. The header parameter is the access token, and the body parameters are the client’s information. The response will contain the following:
  • status "approved", or
  • status "declined", or
  • status "in_process" and URL will contain the 3D Secure dialog box to confirm the payment
2. You open the "URL" in an HTML-supporting application (e.g., a web browser) and show it to the customer. Depending on whether 3D Secure is required one of the following will happen:
  1. 1.
    The customer completes 3DS, and after the transaction is approved or declined (2*)
  2. 2.
    The customer immediately sees the result of the transaction (2**)
3. The "POST MPI deposit request" method returns an "id" value (the transaction ID within the BridgerPay system). You can use it to request information by calling the "Get deposit by ID" method. BridgerPay will also notify you of the transaction’s outcome.
Copy link