...
Excerpt |
---|
|
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 |
---|
maxLevel | 4 |
---|
minLevel | 2 |
---|
outline | true |
---|
class | toc |
---|
|
|
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 |
---|
title | 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. |
Info |
---|
|
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. |
Infonote |
---|
|
Additional gateways are added periodically. If the gateway you use is not listed, we may be able to develop it for you. |
Merchant Gateways
Authorize.net
Image Removed
Gateway Options
Option | Details |
---|
Login ID | This is the Login ID provided by Authorize.net or your merchant account provider. |
Transaction Key | This is the Transaction Key provided by Authorize.net or your merchant account provider. |
Payment API | AIM (default) stores card data encrypted within Blesta. CIM stores card data with the payment gateway only. (Must be enabled in Authorize.net) |
Test Mode | If selected, transactions will be processed in test mode and will not settle. |
Developer Mode | If selected, transactions will be posted to the developer environment. Developer account required. |
Accepted Currencies | USD |
BluePay
Image Removed
Option | Details |
---|
Account ID | This is the Account ID provided by BluePay or your merchant account provider. |
Secret Key | This is the Secret Key provided by BluePay or your merchant account provider. |
Test Mode | If selected, transactions will be processed in test mode and will not settle. |
Accepted Currencies | USD |
eWay
Image Removed
Option | Details |
---|
Customer ID | This is the Customer ID provided by eWay or your merchant account provider. |
Refund Password | This is the Refund Password as set in your eWay account. If not set, refunds cannot be issued. |
Test Mode | If selected, a test account with a test credit card number will be used regardless of what is entered. |
Developer Mode | If selected, transactions will be posted to the eWay sandbox environment. A sandbox account is required. |
Accepted Currencies | AUD |
PayPal Payflow Pro
Image Removed
Option | Details |
---|
Vendor/Merchant Login | This is the Vendor/Merchant Login provided by PayPal Payflow Pro or your merchant account provider. |
Password | This is the password as configured within PayPal Payflow Pro. |
User | This is the User provided by PayPal Payflow Pro or your merchant account provider. |
Partner | If direct from PayPal, enter PayPal here. If by an authorized PayPal reseller use the value provided to you. |
Test Mode | If selected, transactions will be processed in test mode and will not settle. |
Accepted Currencies | AUD, CAD, CHF, CZK, DKK, EUR, GBP, HKD, HUF, ILS, JPY, MXN, NOK, NZD, PHP, PLN, SGD, SEK, TWD, THB, USD |
Quantum Gateway
Image Removed
Option | Details |
---|
Gateway Login | This is the Gateway Login provided by Quantum Gateway or your merchant account provider. |
Restrict Key | This is the Restrict Key provided by Quantum Gateway or your merchant account provider. |
Use Maxmind | If selected, Quantum Gateway will run transactions through their Maxmind service. Additional charges may apply. |
Accepted Currencies | USD |
Stripe
Image Removed
Option | Details |
---|
API Secret Key | This is the API Secret Key provided by Stripe or your merchant account provider. |
Store Card Information Offsite | If selected, card details will be stored with Stripe rather than within Blesta. (Recommended) |
Accepted Currencies | USD |
Non-Merchant Gateways
2Checkout
Image Removed
Option | Details |
---|
Vendor Account Number | This is the Vendor Account Number provided by 2Checkout. |
Secret Word | This is the Secret Word provided by or configurable within 2Checkout. |
API Username | This is the API Username provided by or configurable within 2Checkout. It is required to process refunds. |
API Password | This is the API Password provided by or configurable within 2Checkout. It is required to process refunds. |
Test Mode | If selected, transactions will be processed in test mode and will not settle. |
Accepted Currencies | AED, ARS, AUD, BRL, CAD, CHF, DKK, EUR, GBP, HKD, ILS, INR, JPY, LTL, MXN, MYR, NOK, NZD, PHP, RON, RUB, SEK, SGD, TRY, USD, ZAR |
Google Checkout
Image Removed
Option | Details |
---|
Callback URL | You must set this URL as your API Callback URL under Settings > Integration within your Google Checkout account. |
Merchant ID | This is the Merchant ID provided by Google Checkout. |
Merchant Key | This is the Merchant Key provided by Google Checkout. |
Callback Key | This is used to verify transactions from Google Checkout are legitimate. Anything can be entered. |
Developer Mode | If selected, transaction will be posted to Google Checkout's Sandbox environment. Only enable if you are testing with a sandbox account. |
Accepted Currencies | GBP, USD |
PayPal Payments Standard
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. Code Block |
---|
| 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 |
---|
| UPDATE `transactions` SET `gateway_id`='NEWID' WHERE `gateway_id`='OLDID'; |
|
Children Display |
---|
all | true |
---|
depth | 2 |
---|
style | h3 |
---|
excerpt | true |
---|
excerptType | simple |
---|
|
Image Removed