Set this field to the way you want the cart to connect to this gateway.<br><br>

<b>1. Server to Server communication</b><br>
Server at e-commerce site sends all order information to the Payment Gateway in the background via SSL (Secure Socket Layer). Payment Gateway sends information back to e-commerce server indicating the transaction status, and that information is then used to determine what message to issue to the customer. In this method, the customer never sees the URL for the Payment Gateway in their browser. The customer never leaves the site that they ordered from. This method requires that you have CURL installed, and that it be configured to use OpenSSL.<br><br>

<b>2. Client side secure form POST</b> <br>
Client sends all order information via their browser to a secure page on the payment gateway site. This sometimes can appear the same to the customer as the first method, if the payment gateway supports a quick redirect back to the originating site. All payment information is entered at the e-commerce site. Because of this, this method requires that the e-commerce site have an SSL certificate installed, or have access to a shared SSL certificate. <br><br>

<b>3. Client side non-secure form POST</b><br>
This method is used when the e-commerce site does not have SSL installed. Because of lack of SSL, there is no secure way for the e-commerce site to gather payment information. The order information is sent to via a form POST or a link to a secure URL at the Payment Gateway site. The client is then presented with a form in which they enter their payment information, and complete the order.<br><br>
<b>Note:</b>not all gateways support all methods