You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Table of Contents

Gateways are separated into two categories: Merchant and Non-Merchant. Typically, Merchant gateways require a merchant account and payment is all handled seamlessly through Blesta. Non-Merchant gateways usually do not require a merchant account and payment is usually processed on the gateways website.

To use a gateway, it first must be installed under [Settings] > [System] > [Payment Gateways] > Available. Once installed, the gateway can be configured and used. It will then be accessible under [Settings] > [System] > [Payment Gateways] > Installed by clicking the "Manage" button. 

Merchant Gateways

Authorize.net

Gateway Options
  1. Login ID
    1. This is the Login ID provided by Authorize.net or your merchant account provider.
  2. Transaction Key
    1. This is the Transaction Key provided by Authorize.net or your merchant account provider.
  3. Payment API
    1. AIM (default) stores credit card data encrypted within Blesta.
    2. CIM stores credit card data with the gateway, and not within Blesta.
  4. Test Mode
    1. Select this option to run transactions in Test Mode. This method is only supported if the Payment API is AIM.
  5. Developer Mode
    1. Selecting this option posts transactions to the developer environment. You must have a developer account to use this option.

BluePay

eWay

PayPal Payflow Pro

Quantum Gateway

Stripe

Non-Merchant Gateways

2Checkout

Google Checkout

PayPal Payments Standard

  • No labels