Common integration methods for p…

Hosted Payment Page

When a user confirms an order on a merchant website and clicks the “Continue Payment” button, the browser jumps directly from the merchant website to the payment page provided by the best payment gateway, where the card information is entered and payment is made.

In-Context Popup

When a user confirms an order on the merchant’s website and clicks the “Continue Payment” button, the payment module provided by the payment gateway pops up directly on the current page, allowing the user to make a payment without leaving the merchant’s website. The most typical example is PayPal’s contextual checkout.


The payment gateway extracts the parts containing the input card information and payment button into a common component, allowing the merchant to load the payment component into the page using an iframe when presenting the payment page.


When a user finishes entering payment enterprise information on the merchant’s website and clicks on a button to perform the payment function, an API request is sent directly from the back end of the merchant’s website to the payment security gateway.

For merchants who can meet PCI DSS and have some technical ability to integrate APIs, the API integration model with the best user experience is the best choice.

For merchants who want to be completely free from PCI regulation, or who want to provide payment functions as soon as possible, but do not have high requirements for user experience, Popup or Hosted Payment Page is a good choice.

For most merchants in general, iFrame is the best choice for most scenarios because it not only helps merchants to avoid PCI, but also needs to have a better user experience and faster integration speed.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>