Payment Gateway Bundle Plugin Settings

In order to complete the eWAY profile settings simply follow the steps outlined below so after a payment, eWAY can send payment notification to the plugin for post payment processing.

eWAY Settings Menu

Step 1: Check the “Use eWAY Payment Gateway” option from the eWAY Settings section.

Step 2: Enter your eWAY Customer ID

Step 3: Enter your eWAY username

Step 4: Enter a Company Name (optional)

Step 5: Select the country you are using eWAY from.

Step 6: Enter a selector Label for eWAY (This text will be displayed in the select box if a customer chooses eWAY for checkout)

Step 7: Hit the “Update” button at the bottom to save the settings and now you are ready to use eWAY with the WP Payment Gateway Bundle Plugin.

Step 1: Before you can use ARB, you will need to configure some Authorize.net AIM (Advanced Integration Method) specific settings in the plugin. Follow the setup instruction from the following link to complete the authorize.net merchant specific setup:

• Authorize.net AIM Setup

[wp_pg_eStore_ARB_subscription_button id=1]

Important Notes

1. ARB doesn’t have any option to set a different “trial period” (e.g. 7 days) from the one specified in the “Recurring Billing Cycle” (e.g. 1 month). So “Trial Billing Period” will always follow the values specified in the “Recurring Billing Cycle” (under Subscription/Recurring Payment settings section).
2. “Recurring Billing Cycle” cannot be more than 1 year or less than 7 days (as ARB only support a Subscription Length of 7-365 days or 1-12 months)
3. A Once off payment doesn’t apply on ARB. So entering -1 in the “Recurring Billing Count” field will not work.
4. “Reattempt on failure” option is not applicable for ARB.
5. A free trial can be offered by specifying “0” in the “Trial Billing Amount” field

WP eStore and NextGen Gallery Integration

The images were resized to 800×600 resolution using the NextGen Gallery resize utility. An watermark was also applied to the image using the NextGen Gallery ‘Effect’ option to prevent stealing. Once the purchase is complete the encrypted download link for the original image stored in a separate location (1920×1200 resolution and no watermark) is emailed to the buyer.

Just to clarify… You don’t necessarily have to sell digital photos to use the gallery. You could be selling anything and still use the Gallery as a means of displaying the products where each thumbnail is the icon of the product you are selling.

How to Integrate NextGen Gallery and WordPress eStore Plugins

There are two ways to integrate NextGen Gallery with the WP eStore plugin:

1. Create/Configure every product separately
2. Configure one product then use that as a template

This page explains the first integration method. Please see the following page for the 2nd integration method:

• NextGen Gallery Alternative Integration Method (Method 2)

What Plugins do you need?

You will need the WordPress eStore v1.4 or above and NextGen Gallary Plugins. This guide assumes that you have used NextGen Gallery Plugin and know how to use it. If you don’t know how to use NextGen Gallery then I suggest you read the ‘Readme.txt’ file that comes with the NexGen Gallery plugin or try the NextGen Gallery forum

The Integration Steps

Step1. What NextGen Gallery Modification is needed?

We are going to use a custom template file for the NextGen Gallery to display the shop:

1. Download the WP eStore template file for NextGen Gallery from here.
2. Unzip and upload the ‘gallery-wp-eStore.php’ file to the ‘view’ folder of the NextGen gallery plugin directory (nextgen-gallery/view/gallery-wp-eStore.php).

Note: The template file needs to be uploaded into the “view” directory of the “NextGen Gallery” plugin and not the “WP eStore” plugin.

Step 2. Displaying the Gallery

Use the following tag to display the Gallery in a post or page.

Given the gallery id is 1. Using the ‘template=wp-eStore’ option will show captions underneath each thumbnail image where you can display the ‘Add to Cart’ button and a little bit of other details/description of the image.

Note: The “S” in “wp-eStore” is capitilized.

Step 3. Adding the ‘Add to Cart’ Buttons below the Image Thumbnails

1. Go to ‘Manage Gallery’ from the NextGen Gallery settings menu and choose the Gallery that you want to turn into a shop.

2. Now in the ‘Alt & Title Text / Description’ field of every image enter the Image details (name, price etc) and the trigger text for the ‘Add to Cart’ button of that image. It should look similar to the following example:

In the above example the Product id of the Photo is 4 (the product ID can be found in the “Manage Products” menu of eStore) which I have configured from the ‘Add/Edit Products’ menu of the WordPress eStore plugin. “<br />” is a HTML code to insert a line break so the name, price and the button doesn’t appear on the same line.

3. Do the same for all the images in the gallery.

4. Save the Changes to the Gallery and Now your Gallery will look similar to the demo shown at the start of this Page.

Important Notes and F.A.Q:

Question 1: What Happens When You Upgrade the NextGen Gallery Plugin?

After you upgrade the NextGen Gallery, you need to put the WP eStore Template file back in the ‘view’ directory (nextgen-gallery/view) and all done.

This is because, when upgrading, WordPress completely deletes the folder of the plugin that is being upgraded then downloads the new version. So the previously uploaded WP eStore template file gets deleted in the process.

Question 2: Can I use an eStore fancy display inside a NextGen gallery display?

No, the NextGen gallery itself is a way of displaying your products. So you cannot insert a pre-configured eStore’s fancy display inside a NextGen gallery display (they are two different display methods).

The WordPress eStore Plugin can be found in the WordPress eStore Plugin Page. All WP eStore related documentation can be found on the WP eStore Documentation Site.

The key thing to understand here is that the APR feature protects the content inside the APR shortcode (it doesn’t try to mask the URL of the page). The content inside the APR Shortcode can only be viewed after the customers click on the encrypted link for that product that they receive after the purchase. If anyone directly goes to that URL the content inside the APR shortcode will be hidden.

Setup Preparation (Basic Understanding)

The security mechanism used by APR is an encrypted session cookie; the APR Cookie.  Each APR cookie is specific to a particular permalink, and contains encrypted timing information.  On the pages being protected by APR, called APR Targets, an APR shortcode encloses the content being protected.  Content enclosed by an APR shortcode will only be displayed if one of the following specified conditions are met:

• An APR cookie EXISTS in the current browser session.
• An APR cookie exists and is LESS THAN an a specified number of minutes old.

Setup Authenticated Page Redirect

Step1

To setup a permalink as a digital product first you need to create the target page and setup the content that you want to deliver after the purchase.

Create a page or post that will become the APR target then enclose the content you want to protect using one of the following shortcodes:

• Available Shortcodes for Authenticated Page Redirect Feature

Please make sure that the permalink you will be using works.  Copy and paste it into the address bar of your browser.  Specifically, ensure that the permalink you think you are going to use does not get modified by WordPress.  If the permalink changes, then either fix the problem or use the resulting URL as the link you will use for the APR target URI.

Step 2

Setup your digital product, using the URL of the APR target page in the “Digital Product URL” field.  CHANGE the URL scheme from ‘http’ to ‘aprtp’ or from ‘https’ to ‘aprtps’ in the “Digital Product URL” field. So for example if your APR target page URL is the following:

Change the keyword “http” to “aprtp” and use that URL in the “Digital Product URL” field. So for the above example you will enter the following in the “Digital Product URL” field:

aprtp://www.example.com/my-secret-page-with-awesome-video

Now, whenever an encrypted link, pointing to an APR target is processed by eStore; an APR cookie will be issued, before the browser is redirected to the APR target, by the download manager script. This way your customers can only view the protected content on that page after they have made a payment.

Limitations

If an APR target contains the ‘nextpage’ tag, only content on the first page will be protected by the APR shortcodes.

Payment Gateway Bundle Plugin Settings

In order to complete the Sagepay profile settings simply follow the steps outlined below so after a payment, Sagepay can send payment notification to the plugin for post payment processing.

SagePay Setup Settings

Step 1: Check the “Use Sagepay Payment Gateway” option from the Sagepay Settings section.

Step 2: Enter your Sagepay Vendor Login Name

Step 3: Enter the email address where you want to receive the confirmation email after a successful transaction

Step 4: Enter your Sagepay encryption password.

Note: A unique Vendor name and encryption password are provided when Sage Pay creates an account for you. This data is emailed to the person registered on the account. Please email support@sagepay.com if you need to retrieve your password.

Step 5: Hit the “Update” button at the bottom to save the settings and now you are ready to use Sagepay with the WP Payment Gateway Bundle Plugin.

After you install the WP Payment Gateway Bundle plugin you will need to configure some Authorize.net AIM (Advanced Integration Method) specific settings in the plugin. This will let you process credit card on your own site without sending the customer to Authorize.net site. You will however need to have SSL certificate installed on your site.

You can find the Authorize.net Advanced Integration specific settings under the “Gateway Settings” tab when you go to the payment gateway bundle plugin’s settings menu. The following screenshot shows how you can access the settings page of this plugin:

Payment Gateway Bundle Plugin Settings

In order to complete the AIM settings simply follow the steps outlined below:

Auth.net AIM Settings

Step 1: Check the “Use Authorize.net Advanced Integration Methode” checkbox from the “Authorize.net Advanced Integration Settings” section of the plugin.

Step 2: There are two pieces of information that you need to get from your Authorize.net account and specify it in the plugin so the plugin can process the payment using AIM:

• API Login ID
• Transaction Key

If you don’t know how to retrieve the API Login ID and Transaction Key you can have a look here

Step 3: Make sure you have filled in the values in the general settings section of this plugin including the “Form Processing Page URL” field.

After you install the WP Payment Gateway Bundle plugin you will need to configure some PayPal Payments Pro specific settings in the plugin and in your PayPal merchant profile account. This will let you process credit card on your own site without sending the customer to PayPal’s site. You will however need to have SSL certificate installed on your site.

You can find the PayPal Payments Pro Checkout specific settings under the “Gateway Settings” tab when you go to the payment gateway bundle plugin’s settings menu. The following screenshot shows how you can access the settings page of this plugin:

Payment Gateway Bundle Plugin Settings

In order to complete the PayPal Payments Pro settings simply follow the steps outlined below:

Step 1: Check the “Use PayPal Payments Pro Gateway” checkbox from the “PayPal Payments Pro Settings” section of the plugin.

Step 2: Fill in the API details. There are three pieces of API information that you need to get from your PayPal merchant account and specify it in the plugin so the plugin can process the payment using PayPal payments pro:

• API Username
• API Password
• API Signature

PayPal Payments Pro Setup

If you do not know how to get your PayPal payments Pro API details then the following should help (you can also contact PayPal to get your PayPal Payments Pro account API details):

• Log into your PayPal account (make sure you have PayPal payments pro active on your account – this is a paid service of PayPal)
• Click on Profile in the top bar
• Click Request API Credentials (under the Account Information section)
• Click Set up PayPal API Credentials and Permissions
• Click Grant API Permission

Step 3: Make sure you have filled in the values in the general settings section of this plugin including the “Form Processing Page URL” field.

Payment Gateway Bundle Plugin Settings

In order to complete the Google Checkout profile settings simply follow the steps outlined below so after a payment, Google Checkout can send payment notification to the plugin for post payment processing.

Step 1: Log into your Google Checkout Sellers account and go to the “Settings” tab:

Google Checkout Merchant Profile Settings

Step 2: Click on the “Integration” tab:

Google Checkout Merchant Profile Integration Settings

Step 3: Configure the Integration settings as outlined in the screenshot below:

Google Checkout Merchant Profile Integration Settings

Step 4: Hit the save button and now you are ready to use Google Checkout with the WP Payment Gateway Bundle Plugin.

The Amazon S3 integration involves the following two steps:

1. Specify the Amazon S3 API details in the eStore plugin’s settings
2. Specify the URI of your digital asset in the digital product URL field of the product in question

Amazon S3 Integration Details

The amazon S3 integration options can be found under the “AddOn Settings” tab in eStore Settings menu. Once you have configured the amazon S3 access key and secret access key in the S3 settings section under the AddOn Settings tab of eStore you are ready to start using Amazon s3 with WP eStore.

You need to tell WP eStore to redirect encrypted download links to the AWS S3 server using the AS3TP URI in the Digital Product URL field of the product. Basically, enter your Product URL using the following method in the “Digital Product URL” field:

as3tp://bucket.s3.amazonaws.com/folder/object

Here, “bucket” is the name of the S3 bucket containing the digital product, and “folder/object” is the S3 key which points to the digital product.

You may also use “as3tps://” in place of “as3tp://” if you want the S3 download to be SSL encrypted. You also have the option of inserting “public@” before the bucket name, if the S3 object is marked as “public” on the S3 server.

The following screen capture shows how to properly create this URI value

Here are some typical examples of valid AS3TP URI that you can use in eStore:

• as3tp://bucket.s3.amazonaws.com/object
• as3tp://bucket.s3.amazonaws.com/folder/object
• as3tps://bucket.s3.amazonaws.com/folder/folder/object
• as3tps://public@bucket.s3.amazonaws.com/object

Remember to use one of the above URI methods to enter your product URL in the “Digital Product URL” field (Don’t just use the normal amazon S3 URL of the product in that field).

Use of Amazon S3 is completely optional, but provides several advantages for those who use it. The biggest advantage is that your eStore server is relieved of the burden of having to act as an intermediary when processing anonymized downloads. This will enhance the download experience for users, because they are directly downloading files from the higher bandwidth S3 server. And because the redirection is done using an expiring AWS presigned URL request, your digital products are protected; even if the user saves the redirection URL. And, successful downloads are no longer dependent upon the reliability of your hosting provider’s server.

IMPORTANT NOTES:

• Strict S3 bucket naming restrictions are enforced.
• Only virtual hosted style bucket names are supported. Path style bucket name access is not supported.
• CNAME DNS aliases are supported.
• Region specific end points are not supported.
• Use of “public@” tells eStore not to presign URL for public objects. Forgetting to add “public@” to the URI, generates a presigned URL, but no redirection errors will occur.
• Remote hosting (on S3) of PDF Stamper files is not supported