Payment Gateways

 Last Edited: Sep 09, 2019

Prerequisites

  • - You have installed the eCommerce Module in Site Settings
  • - You have an account set up on one of our supported Payment Gateways (listed in this document)

Introduction

You need to set up a Payment Gateway in Siteglide in order to take payments via eCommerce.


How to set up

In the Siteglide admin panel, you want to navigate to ECOMMERCE>Payment Gateways

Click 'Add new Payment Gateway' in the top right, and fill in the following details:

  • - Gateway Provider - Choose from a dropdown of our supported Payment Gateways
  • - Name - Set a friendly name for reference in the list view in Siteglide
  • - Enabled - This must be true if you want the Gateway to be active
  • - In Test Mode? - This determines which key pairs are used when taking a payment. When you start out, you probably want this set to 'true'. Once you're ready to go live, it should be 'false'.

Payment Gateways typical provide 2 keys for each environment (live and testing).

The names of those are specific to the Gateway. See below for what we expect from each Payment Gateway.

Stripe:

  • - Public Key (Live) - pk_live_XXXXXXXXXXXXXXXX
  • - Secret Key (Live) - sk_live_XXXXXXXXXXXXXXXX
  • - Public Key (Test) - pk_test_XXXXXXXXXXXXXXXX
  • - Secret Key (Test) - pk_test_XXXXXXXXXXXXXXXX

Authorize.net

  • - Public Key (Live) - API Login ID (live)
  • - Secret Key (Live) - Transaction Key (live)
  • - Public Key (Test) - API Login ID (sandbox)
  • - Secret Key (Test) - Transaction Key (sandbox)

Minimum payment amounts

Some Payment Gateways enforce an minimum transaction value. Typically this is because they charge a small fixed transaction fee, so need a minimum transaction value in place to ensure you don't lose money on the charge.

These minimum amounts are documented by the Payment Gateway:


Test cards and data

StripeStripe testing docs

Authorize.net Authorize.net testing guide