Payment Plugin Configuration Parameters

Demo Payment

Demo Payment is a dummy payment plugin shipped with Billing. Accepting transactions, it processes them as real ones, but does not pass them on to the financial institutions. Demo Payment is also a sample for building custom payment plugins. Refer to the Payment Plugin SDK Guide for details. The plugin can operate both in redirect and tokenized modes.

Enable Tokenization Mode. The option defines the operating mode of the Demo Payment plugin:

• When the tokenzation mode is enabled, the Demo Payment plugin allows a customer to save payment method details for future payments, in which case Billing stores a token that represent this payment method in Billing. For the subsequent payments, the customer may choose to use the saved payment method or get redirected to the Demo Payment page to use another payment method.
• When the tokenzation mode is disabled, the Demo Payment plugin operates in the redirect mode: for every payment a customer is redirected to the Demo payment page.

For recurring payments to be processed by the Demo Payment plugin, it is required that the plugin operates in tokenized mode.

Logging errors

By default, responses from the processing center are written to /var/log/httpd/payment-sdk.log.

2Checkout

2Checkout is an online payment processing center that accepts transactions via API. For additional information, visit their official site (https://www.2checkout.com). The plugin operates in the modal mode.

Publishable Key. The API key to identify your account with 2Checkout; can be safely passed within a browser. The publishable key can be used when creating tokens.

Private Key. The API key that can perform any API request to 2Checkout without restriction. It must be kept confidential and only stored on your own servers. The Private Key and Publishable Key can be found under the API tab in your 2Checkout account.

Seller ID. Your 2Checkout account ID.

Secret Word. The secret word which is set at the 2Checkout account.

Sandbox Mode. The option indicates whether the transactions are processed in the test mode:

• In the Sandbox mode, all transactions appear to be processed as real transactions. The gateway accepts these transactions, however, does not pass them on to the financial institutions.
• For production environment, this option must be disabled.

Username and Password. The credentials to authenticate with 2Checkout. They are generated at the 2Checkout account page.

Logging errors

If enabled, responses from the processing center will be written to /var/log/httpd/payment-sdk.log

Authorize.Net

AuthorizeNet is an online payment processing center that accepts transactions through API. For additional information, visit their official site (http://www.authorize.net/). The plugin can operate both in the redirect and tokenized modes.

API Login ID and Transaction Key. The log-in credentials are obtained from AuthorizeNet when subscribing to their services.

Test Mode. The option indicates whether the transactions are processed in the test mode:

• In the Test mode, all transactions appear to be processed as real transactions. The gateway accepts these transactions, however, does not pass them on to the financial institutions.
• For production environment, this option must be disabled.

Logging errors

By default, responses from the processing center are written to /var/log/httpd/payment-sdk.log.

eWAY

eWAY is a global omnichannel payment provider, processing secure credit card payments for merchants around the world. For more information, visit their official site https://eway.io/. The payment gateway operates both in the redirect and tokenized modes.

API Key and API Key Password. The log-in credentials are obtained from eWAY when subscribing to their services.

Allow Tokenization. The option defines the operating mode of the plugin:

• When the tokenzation mode is enabled, the plugin allows a customer to save payment method details for future payments, in which case Billing stores a token that represent this payment method in Billing. For the subsequent payments, the customer may choose whether to use the saved payment method or get redirected to the payment page to use another payment method.
• When the tokenzation mode is disabled, the plugin operates in the redirect mode: for every payment the customer is redirected to the payment page.

For recurring payments, the plugin must operate in tokenized mode.

Approve CHALLENGED Transactions. eWAY checks every transaction against fraud, and suspicious (challenged) transactions are refused. Enable the option to approve such transactions.

Verify Customer Phone. When enabled, the customer's phone will be verified at the payment page.

Verify Customer Email. When enabled, the customer's email will be verified at the payment page.

Responsive Shared Page Theme. A theme of the payment page where customers are redirected to.

Test Mode. The option indicates whether the transactions are processed in the test mode:

• In the Test mode, all transactions appear to be processed as real transactions. The gateway accepts these transactions, however, does not pass them on to the financial institutions.
• For production environment, this option must be disabled.

Debug Mode

If enabled, responses from the processing center will be written to /var/log/httpd/payment-sdk.log

PayPal Express Checkout

PayPal Express Checkout is a payment option of the PayPal online payment processing center. Express Checkout supports handling recurring payments automatically. For additional information, visit their official site https://www.paypal.com/webapps/mpp/express-checkout. The plugin can operate both in the redirect and tokenized modes.

PayPal API Username and PayPal API Password. Credentials identifying you as a PayPal account holder.

PayPal API Signature. The signature to be sent in your API requests.

PayPal Sandbox (test mode). The option indicates whether the transactions are processed in the test mode:

• In the Test mode, all transactions appear to be processed as real transactions. The gateway accepts these transactions, however, does not pass them on to the financial institutions.
• For production environment, this option must be disabled.

Debug PayPal response to file

If enabled, responses from the processing center will be written to /var/log/httpd/payment-sdk.log

PayPal Standard

PayPal an international e-commerce business offering different payment services and allowing merchants to process payments online or to redirect their customers to secure PayPal pages. For more information about PayPal, visit their official site. The plugin operates in the redirect mode.

PayPal Email Address, PayPal Username and PayPal Password. Credentials identifying you as a PayPal account holder.

PayPal API Signature. The signature to be sent in your API requests.

Test Mode. This option indicates whether the transactions are processed in the test mode:

• In the Test mode, all transactions appear to be processed as real transactions. The gateway accepts these transactions, however, does not pass them on to the financial institutions.
• For production environment, this option must be disabled.

Debug Mode

If enabled, responses from the processing center will be written to /var/log/httpd/payment-sdk.log

Stripe

Stripe Checkout is an embeddable payment form of the Stripe online payment processing center. For more information, visit their official site https://stripe.com/checkout. The payment gateway can operate both in the modal-form and tokenized modes.

Live Settings

Publishable Key. The API key to identify your account with Stripe; can be safely passed within a browser. The publishable key can be used when creating tokens.

Secret Key. The API key that can perform any API request to Stripe without restriction. It must be kept confidential and only stored on your own servers.

Test Settings

Publishable Key and Secret Key. API keys for the test mode. The meaning and purpose of the values is similar to the ones described above.

Test Mode. The option indicates whether the transactions are processed in the test mode:

• In the Test mode, all transactions appear to be processed as real transactions. The gateway accepts these transactions, however, does not pass them on to the financial institutions.
• For production environment, this option must be disabled.

Debug Mode

If enabled, responses from the processing center will be written to /var/log/httpd/payment-sdk.log

Note: To use MOTO (Mail Order/Telephone Order) payment transactions that do not require SCA (Strong Customer Authentication) in CloudBlue Commerce a provider must explicitly enable this ability for their account in Stripe.