1. Home
  2. Setup
  3. Integrations
  4. Payment Providers
  5. Integrations – Payment Providers – Full, Generic, Simple
  1. Home
  2. Setup
  3. Integrations
  4. Integrations – Payment Providers – Full, Generic, Simple

Integrations – Payment Providers – Full, Generic, Simple

WishList Member offers a Full integration method for a number of online Payment Providers. This is the recommended method of integration with a Payment Provider.

Full integration means if a Member cancels their payment in the online Payment Provider, it will communicate with WishList Member and cancel the Level of that Member.

There is also a Generic Integration option and a Simple Integration option which can be used to integrate with Payment Providers not included in the Payment Providers section of WishList Member.

Below is a list of the WishList Member Full integration options for Payment Providers:

(In alphabetical order)

  • 1ShoppingCart
  • 2Checkout
  • 2Checkout (Legacy)
  • Authorize.net Recurring Billing
  • Authorize.net Simple Checkout
  • ClickBank
  • CloudNet360
  • Cydec
  • eWay
  • Infusionsoft by Keap
  • JVZoo
  • PayBlue
  • PayKickStart
  • PayPal Checkout
  • PayPal Payflow
  • PayPal Payments Pro
  • PayPal Payments Standard (Legacy)
  • plug&paid
  • Recurly
  • RedOakCart
  • SamCart
  • SendOwl
  • Stripe
  • ThriveCart
  • UltraCart
  • WooCommerce

More details on these Integrations can be found in the Payment Providers section of the Knowledge Base.

Below is a description of a typical payment/registration process when a Full integration option Payment Provider has been integrated with WishList Member.

Although, there are some Payment Providers that handle things a bit differently.

  1. User clicks payment link/button on the membership site to begin purchase process of the Membership Level
  2. User is directed to the Payment Provider site and makes payment.
  3. User is redirected to a page on the membership site where they can set their username and password.
  4. User is now a Member and is automatically logged into the membership site
  5. Email is sent to Member with their account info, etc.

The typical user experience is to pay on the Payment Processor site and then set their username and password as they are automatically redirected to the membership site.

As noted, some Payment Providers are a bit different and include functionality that allows payments to be processed on the membership site. Examples of these Payment Providers are Stripe and PayPal Pro. These integrations allow the User registering to stay on the membership site while they pay. This is due to how Payment Providers like Stripe and PayPal Pro function.

Generic Integration:

If you want to integrate a Payment Provider with WishList Member using the Full integration method (and it doesn’t appear in the¬†Setup > Integrations > Payment Providers section of WishList Member), you can look into the Generic integration option.

WishList Member includes a Generic integration option which allows you to set up an integration between your site and an online Payment Provider.

This opens up the playing field and allows site owners to create a gateway themselves by working directly with the Payment Provider of their choice and using the door we open to send information back and forth between their site and the Payment Provider.

Instructions for the Generic integration can be found in WishList Member in the Integration section. Please note that this is quite a technical process and should not be attempted without knowledge of code.

More details on the Generic Integration (including the Documentation) can be found in the Generic Integration section of the Knowledge Base.

You can use the Documentation to work with the Payment Provider in order to set up a Generic integration.

Simple Integration:

As noted, Full integration means if a Member cancels their payment in the online Payment Provider, it will communicate with WishList Member and cancel the Level of that Member.

It also essentially protects the registration link from those who have not paid. The Registration Form is protected and this link cannot be passed around to those who have not paid when using a Full integration option.

With Simple integration, the link used to register will not be protected as it is with a Full integration. So, it is recommended to periodically check the Payment Provider account to ensure members have paid when using Simple integration.

If a Member cancels payment or doesn’t pay for some reason, their access would need to be manually cancelled within WishList Member when using a Simple integration option.

Below is a description of a typical payment/registration process for a Simple integration.

  1. User clicks payment link/button on the membership site to begin purchase process of the Membership Level
  2. User is directed to the Payment Provider site and makes payment.
  3. User is redirected using the “Thank You URL” in the online Payment Provider.
  4. User is redirected to a page on the membership site where they can set their username and password.
  5. User is now a Member and is automatically logged into the membership site
  6. Email is sent to Member with their account info, etc.
Updated on June 11, 2020

Was this article helpful?

Related Articles

Not the solution you were looking for?
Click the link below to submit a support ticket
Submit Ticket