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 processed offsite on the gateways website.
Not 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.
Installing Gateways
Do 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.
UPDATE accounts_cc SET `gateway_id`='NEWID' WHERE `gateway_id`='OLDID';