WordPress Pay Per Post Plugin (CMPPP) - Settings - Refund Settings (MicroPayments Only)


Refund Settings

Back to User Guide

MicroPayments Plugin Only

This feature is only available in the WordPress Pay Per Post plugin and MicroPayments plugin integration. It's not available in the EDD/WooCommerce direct payments option.

How it Works

  • Refunds are not moderated - they are automatically granted.
  • You can choose how much time the user has to request the refund.

Flow

User clicks refund button...   

'Refund' button - Pay-Per-Post Plugin
'Refund' button

...Chooses reason...

Choosing a refund reason - WordPress Paywall Plugin
Choosing a refund reason

...Is refunded.

Message about successful refund - Paywall Plugin WordPress
Message about successful refund

Setup

Navigate to the Admin Dashboard → CM Pay Per Posts Pro → Settings.

Navigation to the plugin settings - Best Paywall Plugin for WordPress
Navigation to the plugin settings

Click on the Refund tab.

Refund settings tab - WordPress Plugin Paywall
Refund settings tab
  • Enable refunds - Refunds are available only for posts purchased by MicroPayments plugin - EDD or WooCommerce payments currently are not supported.
  • Refund reasons - Create new refund reason by creating new field and filling unique flag (left field) and text label (right field).
  • Time limit to allow refund - Set the time limit in minutes to allow refund for users that activated a subscription. After this time user won't be able to refund.
Refund settings - Paywalled Content
Refund settings

Once set user will be able to view a refund link on the post / pages he has been subscribed to. Once clicked he will need to mark the reason for the refund before it is applied. 


More information about the WordPress Pay Per Post Plugin

Other WordPress products can be found at CreativeMinds WordPress Store

Let us know how we can Improve this Product Documentation Page

To open a Support Ticket visit our support center
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.