Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Excerpt
hiddentrue

Gateways allow for the processing of one time or recurring payments and can be one of two types: Merchant, or Non-Merchant.

Table of Contents
Table of Contents
maxLevel4
minLevel2
outlinetrue
classtoc

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 offsite on the gateways website.

Info
titleNot an exhaustive list.

This is not an exhaustive list of gateways for Blesta. This list contains the gateways that ship with Blesta, or can be found on our Github. There are many third party gateways, and some can be found on the Marketplace. We are also available to hire for custom development. If you're looking to create your own gateway, see Getting Started with Gateways in the developer manual.


Info
titleInstalling Gateways
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 for the desired gateway

Merchant Gateways

Authorize.net

Image Removed

BluePay

Image Removed

eWay

Image Removed

PayPal Payflow Pro

Image Removed

Quantum Gateway

Image Removed

Stripe

Image Removed

Non-Merchant Gateways

2Checkout

Image Removed

Google Checkout

Image Removed

PayPal Payments Standard


Note
titleDo not uninstall token based gateways

Token based gateways should not be uninstalled unless you do not intend to use them anymore. Payment Accounts are linked to the payment gateway instance. If you reinstall a payment gateway that utilizes tokens like Stripe Payments, the associated gateway_id will no longer match and all existing Payment Accounts will be unusable. It's possible to update accounts_cc.gateway_id from the old gateway ID to the new gateway ID by running the following query. First, backup your database. Second, determine the old gateway_id by viewing existing records in the accounts_cc table. Third, determine the new gateway_id by observing the ID in the URL when managing the Payment Gateway in Blesta. Fourth, run the following query, replacing NEWID and OLDID with the new and old ID's.

Code Block
languagesql
UPDATE `accounts_cc` SET `gateway_id`='NEWID' WHERE `gateway_id`='OLDID';

Optional: Existing transactions can also be updated, in order to allow earlier transactions to be voided or refunded.

Code Block
languagesql
UPDATE `transactions` SET `gateway_id`='NEWID' WHERE `gateway_id`='OLDID';



Children Display
alltrue
depth2
styleh3
excerpttrue
excerptTypesimple
Image Removed