Difference between revisions of "PaidListings Add-on Payment Handlers"

From JReviews Documentation
Jump to: navigation, search
(Payment Handlers)
Line 1: Line 1:
 
== Payment Handlers ==
 
== Payment Handlers ==
 
'''It is not possible to test the add-on on localhost when you use it to make payments with Paypal, 2checkout and other payment processors. These send a reply back to your site to update the order information so the site needs to have a valid reachable domain.'''
 
  
 
PaidListings Add-on comes with these payment handlers:
 
PaidListings Add-on comes with these payment handlers:
  
 
+
[[File:payment-handlers.png]]
[[File:PLPaymentHandlers.png]]
+
 
+
  
 
For other payment handlers, a plugin can be written.
 
For other payment handlers, a plugin can be written.
  
 +
'''It is not possible to test the add-on on localhost when you use it to make payments with Paypal, 2checkout and other payment processors. These send a reply back to your site to update the order information so the site needs to have a valid reachable domain.'''
  
 
=== Paypal ===
 
=== Paypal ===
  
[[File:PLPaypal.png]]
+
[[File:paypal.png]]
  
 
PayPal payment handler has 3 states: '''Disabled''', '''Enabled''' and '''Sandbox'''.
 
PayPal payment handler has 3 states: '''Disabled''', '''Enabled''' and '''Sandbox'''.
  
Sandbox is used for testing. To use it, you must first get PayPal developer account here:
+
Sandbox is used for testing. To use it, you must first get a PayPal developer account here:
 
*<span style="color: blue">https://developer.paypal.com</span>
 
*<span style="color: blue">https://developer.paypal.com</span>
 
  
 
=== 2Checkout ===
 
=== 2Checkout ===
  
[[File:PL2CO.png]]
+
[[File:2checkout.png]]
  
 
3 states: '''Disabled''', '''Enabled''' and '''Sandbox'''
 
3 states: '''Disabled''', '''Enabled''' and '''Sandbox'''
  
 
'''Secret word''' can be found under Account => Site Management in the 2CO site
 
'''Secret word''' can be found under Account => Site Management in the 2CO site
 
  
 
=== Authorize.net ===
 
=== Authorize.net ===
  
[[File:PLAuthorize.png]]
+
[[File:authorize.png]]
  
 
3 states: '''Disabled''', '''Enabled''' and '''Sandbox'''
 
3 states: '''Disabled''', '''Enabled''' and '''Sandbox'''
Line 41: Line 36:
 
'''Secret word''' is configurable value in the Authorize.net Account Settings, required for authentication. Leave empty for development accounts.
 
'''Secret word''' is configurable value in the Authorize.net Account Settings, required for authentication. Leave empty for development accounts.
  
 +
=== Offline Payments ===
 +
 +
[[File:offline.png]]
 +
 +
2 states: '''Disabled''' and '''Enabled'''.
 +
 +
After users submit a listing and order a certain plan, they will be redirected to a page with Payment instructions.
 +
 +
== JomSocial Points ==
  
=== Offline ===
+
[[File:jomsocial-points.png]]
  
[[File:PLOffline.png]]
+
If you use JomSocial extension and enable the JomSocial Points as payment handler, users will be able to "pay" for listing plans using the points they earned on your site.
  
2 states: '''Disabled''' and '''Enabled'''
+
== AlphaUserPoints ==
  
If you enable '''Subscription''', you will need to manually charge the user every month
+
[[File:alphauserpoints.png]]
  
After the user submits a listing and orders certain plan, he will be redirected to a page with '''Payment instructions'''
+
If you use AlphaUserPoints extension and enable the AlphaUserPoints as payment handler, users will be able to "pay" for listing plans using the points they earned on your site.
  
== Payment Button ==
+
== Changing payment buttons ==
  
For every payment handler you can change the button image by entering the '''Path to image'''
+
When users order a plan, they will see the buttons of all payment handlers that you enabled. This is how payment handler buttons look like by default:
  
Default payment buttons look like this:
+
[[File:payment-buttons.png]]
  
[[File:PLPaymentButtons.png]]
+
For every payment handler you can change the button image by entering the '''Path to image''' in the handler's settings:
  
 +
[[File:payment-buttons2.png]]
  
  
 
[[Category:JReviews]]
 
[[Category:JReviews]]
 
[[Category:PaidListings Addon]]
 
[[Category:PaidListings Addon]]

Revision as of 19:11, 20 November 2013

Payment Handlers

PaidListings Add-on comes with these payment handlers:

Payment-handlers.png

For other payment handlers, a plugin can be written.

It is not possible to test the add-on on localhost when you use it to make payments with Paypal, 2checkout and other payment processors. These send a reply back to your site to update the order information so the site needs to have a valid reachable domain.

Paypal

Paypal.png

PayPal payment handler has 3 states: Disabled, Enabled and Sandbox.

Sandbox is used for testing. To use it, you must first get a PayPal developer account here:

2Checkout

2checkout.png

3 states: Disabled, Enabled and Sandbox

Secret word can be found under Account => Site Management in the 2CO site

Authorize.net

Authorize.png

3 states: Disabled, Enabled and Sandbox

Testing can be done with the production or test gateways. For the test gateway you need an Authorize.net developer account, but if Sandbox is selected above you can still perform test transaction on the production gateway.

Secret word is configurable value in the Authorize.net Account Settings, required for authentication. Leave empty for development accounts.

Offline Payments

Offline.png

2 states: Disabled and Enabled.

After users submit a listing and order a certain plan, they will be redirected to a page with Payment instructions.

JomSocial Points

Jomsocial-points.png

If you use JomSocial extension and enable the JomSocial Points as payment handler, users will be able to "pay" for listing plans using the points they earned on your site.

AlphaUserPoints

Alphauserpoints.png

If you use AlphaUserPoints extension and enable the AlphaUserPoints as payment handler, users will be able to "pay" for listing plans using the points they earned on your site.

Changing payment buttons

When users order a plan, they will see the buttons of all payment handlers that you enabled. This is how payment handler buttons look like by default:

Payment-buttons.png

For every payment handler you can change the button image by entering the Path to image in the handler's settings:

Payment-buttons2.png