Vlado Grcic

<p>Page Restrict for WooCommerce is a plugin that sells access to pages, posts and custom post types through WooCommerce. It’s been built with Gutenberg in mind as well as the classic editor. You can restrict pages in two ways. Restrict an entire page or restrict sections on the page. In case you want to restrict sections on the page you can use blocks for the Gutenberg editor and using shortcodes for the classic or similar editors. If you want to restrict entire pages you can use enable the sidebar in the More tools & options in the Gutenberg editor or use the page metabox in the classic editor. You can also restrict all of your pages in one place in the Pages plugin menu.</p>
<h4>Requirements</h4>
<ul>
<li>WooCommerce to be installed and active</li>
<li>Guest checkout needs to be disabled</li>
<li>PHP 7.0.25+. </li>
</ul>
<h4>Features</h4>
<ul>
<li>Restrict content from pages, posts and custom post types based on if they have purchased a specific WooCommerce product</li>
<li>Restrict entire page or just sections of it</li>
<li>Use one or multiple products to restrict it and choose whether you want to require the user to buy all of them to access or at least one of the products that restrict. </li>
<li>Restrict by time – Set a time limit for the user after which they won’t be able to see the content.</li>
<li>Restrict by views – Set a view count for the user after which they won’t be able to see the content ( currently only if you want to restrict entire pages ).</li>
<li>Use other pages or posts for specific pages as Restricted Messages</li>
<li>Use default pages or posts for all restricted pages as Restricted Messages</li>
<li>Redirect to the chosen page instead of just showing the other pages content</li>
<li>Built for use with the latest Gutenberg editor as well as the classic one</li>
<li>Use either Gutenberg blocks or shortcodes to restrict sections on a page or post</li>
<li>Plugin menu page to handle all pages you need to restrict in one place called Pages</li>
<li>Plugin menu page to get an overview of all users that bought a product required to access an restricted page which either is still valid or already expired called User Overview.</li>
<li>Similar feature to User Overview for the frontend for each user to have an overview of their pages where they bought products in order to access them.</li>
<li>A Quick Start menu page to get you started on using this plugin</li>
</ul>
<h4>Blocks</h4>
<p><strong>page-restrict-wc/restrict-section</strong><br />
Section Restrict for WooCommerce – Restricts a section on the page using this grouping element.</p>
<p><strong>page-restrict-wc/restricted-pages-list</strong><br />
Restricted Pages List – Shows a table of restricted pages for the current user which have had bought products for.</p>
<h4>Shortcodes</h4>
<p>[prwc_is_purchased products=”1,2″ days=”25″ hours=”2″ minutes=”45″ seconds=”15″ inverse=”false” defRestrictMessage=”Restrict Message” notAllProductsRequired=”false” defaultPageNotBoughtSections=”4″ defaultPageNotLoggedSections=”5″]</p>
<ul>
<li>Restricts the content using the chosen options. </li>
<li>products – choose which products to restrict with. Add product IDs separated by a comma.</li>
<li>Timeout options for this are days, hours, minutes, seconds.</li>
<li>inverse – using the inverse option you can choose inverse=”false” to hide the content in order for the user to not see it. Choose inverse=”true” for the user to see it in order to show them instructions on what to do to access the desired content you chose using inverse=”false”</li>
<li>defRestrictMessage – is the message you want to show if the user didn’t buy the product.</li>
<li>notAllProductsRequired – set to true if the user doesn’t need to buy all products.</li>
<li>defaultPageNotBoughtSections – you can choose a page to show instead of a message like in defRestrictMessage.</li>
<li>defaultPageNotLoggedSections – you can choose a page to show if the user isn’t logged in.</li>
</ul>
<p>[prwc_restricted_pages_list table=”time” disable_table_class=”false”]</p>
<ul>
<li>Shows a table of restricted pages for the current user which have had bought products for.</li>
<li>Using the table attribute you can choose which table of restricted page you will show. It can show pages that are restricted either by time or view count.</li>
<li>Using disable_table_class attribute you can choose whether to kepp or not to keep the default plugin style for the tables.</li>
<li>You can show restricted pages that timeout either by time or view. </li>
</ul>
<h4>Coming soon</h4>
<ul>
<li>Restrict categories</li>
<li>Restrict authors</li>
</ul>


Page Restrict for WooCommerce

Restrict access to your WordPress pages using WooCommerce products.

KosTeams

<p>This plugin adds popular Yandex payment methods to your WooCommerce store:<br />
– <strong>Yandex Pay</strong>: Instant card payment without entering card details.<br />
– <strong>Yandex Split</strong>: Interest-free installments for up to 6 months.<br />
– <strong>Combined payment</strong>: Pay part by card and the rest in installments.</p>
<h4>Modern Technology Compatibility</h4>
<ul>
<li><strong>Full WooCommerce Block Editor support</strong> — the plugin works with both classic and block checkout</li>
<li><strong>Gutenberg compatible</strong> — integration with modern WordPress themes</li>
<li><strong>React components</strong> — modern architecture for fast performance</li>
</ul>
<p>For advanced features (installment badges, widgets in cart and catalog), the <a href="https://kosteams.com/plugins/bejdzhi-i-vidzhety-yandex-split-i-yandex-pay-dlya-wordpress/" rel="nofollow ugc">Pro version</a> is available.</p>
<h3>Important Fiscalization Information</h3>
<p><strong>Please note:</strong> When using Yandex Pay and Yandex Split, you must comply with Russian legislation requirements for payment fiscalization.</p>
<h4>54-FZ Requirements</h4>
<p>According to the Federal Law “On the Application of Cash Register Equipment” (54-FZ):<br />
– Fiscal receipts must be issued for all forms of non-cash payments<br />
– Yandex Pay and Yandex Split do not send fiscal receipts automatically<br />
– The seller is responsible for complying with fiscalization requirements</p>
<h4>Possible Solutions</h4>
<p>To ensure 54-FZ compliance, consider the following options:<br />
– Integration with online cash registers (ATOL, Evotor, OFD, etc.)<br />
– Using specialized plugins for automatic receipt generation<br />
– Setting up API integration with your fiscal service provider<br />
– Consulting with certified cash register integrators</p>
<h4>Penalties for Non-Compliance</h4>
<ul>
<li>For individual entrepreneurs: from 10,000 rubles per violation</li>
<li>For legal entities: from 30,000 rubles per violation</li>
<li>Business operations may be suspended for up to 90 days</li>
</ul>
<p><strong>Recommendation:</strong> Be sure to set up fiscalization before accepting payments via Yandex Pay. For detailed advice, consult your accountant or online cash register service provider.</p>
<h3>Version Features</h3>
<p><strong>Free version includes:</strong><br />
– Yandex Pay and Yandex Split support<br />
– Combined payment (card + installments)<br />
– Configuration through the WooCommerce interface<br />
– Compatibility with both classic and Gutenberg block editor</p>
<p><strong>Pro version adds:</strong><br />
– Installment/cashback badges on product pages<br />
– Installment/cashback badges in the product catalog<br />
– Payment widgets in cart and catalog<br />
– Yandex payment button on the checkout page<br />
– 20+ element positioning options</p>
<h3>Recommended Add-ons</h3>
<p>To ensure full compliance with Russian legislation and extend functionality, the following solutions are recommended:</p>
<h4>Payment Fiscalization (required for 54-FZ compliance)</h4>
<p><strong><a href="https://kosteams.com/plugins/atol-receipts-yandex-v4/" rel="nofollow ugc">KosTeams ATOL Receipts</a></strong> — A specialized plugin for automatic fiscalization of payments via Yandex Pay and Yandex Split.</p>
<p>Key features:<br />
– Automatic fiscal receipt generation via ATOL Online for every payment<br />
– Full support for ATOL API v4 and v5<br />
– Automatic detection of Yandex Pay and Split payments<br />
– HPOS (High-Performance Order Storage) support<br />
– Automatic refund receipts when orders are cancelled<br />
– Real-time fiscalization status monitoring<br />
– Detailed logging for diagnostics</p>
<p><strong>Why this plugin:</strong><br />
– Designed specifically for integration with Yandex payment systems<br />
– Automatically detects payments that require fiscalization<br />
– Fully compliant with 54-FZ requirements<br />
– Tested together with this plugin</p>
<h4>Alternative Fiscalization Solutions</h4>
<ul>
<li>Other ATOL Online integration plugins</li>
<li>Evotor integration solutions</li>
<li>Modules for connecting to other OFD providers</li>
<li>API integration with your cash register service provider</li>
</ul>
<h4>Conversion Improvement</h4>
<p><strong><a href="https://kosteams.com/plugins/bejdzhi-i-vidzhety-yandex-split-i-yandex-pay-dlya-wordpress/" rel="nofollow ugc">KosTeams Payments for Yandex Pay and Yandex Split for WooCommerce Pro</a></strong> — Extended version of this plugin with additional features:<br />
– Installment/cashback badges on product pages and in the catalog<br />
– Payment widgets in cart and on product pages<br />
– 20+ element positioning options<br />
– Advanced design and behavior settings</p>
<p><strong>Important:</strong> Regardless of the fiscalization solution you choose, setting it up is mandatory before accepting payments via Yandex Pay to comply with 54-FZ requirements.</p>
<h3>Links</h3>
<ul>
<li><a href="https://kosteams.com/plugins/bejdzhi-i-vidzhety-yandex-split-i-yandex-pay-dlya-wordpress/" rel="nofollow ugc">Setup Documentation</a></li>
<li><a href="https://kosteams.com/plugins/bejdzhi-i-vidzhety-yandex-split-i-yandex-pay-dlya-wordpress/" rel="nofollow ugc">Buy Pro Version</a></li>
<li><a href="https://www.consultant.ru/document/cons_doc_LAW_42359/12a6477d0e22968564d9416e594a80202a7024db/" rel="nofollow ugc">Information about 54-FZ and Fiscalization</a></li>
</ul>
<h3>License</h3>
<p>This plugin is distributed under the GPLv2 license. Advanced features are available in the Pro version.</p>
<h3>Support and Security</h3>
<h4>Payment Security</h4>
<ul>
<li>All transactions are processed through Yandex secure servers</li>
<li>Card data is not stored on your site</li>
<li>PCI DSS compliant</li>
</ul>
<h4>Legal Compliance</h4>
<ul>
<li>The plugin provides technical integration with payment systems</li>
<li>Fiscalization compliance (54-FZ) requires additional solutions</li>
<li>Consulting with lawyers and accountants is recommended</li>
</ul>
<h4>Getting Support</h4>
<ul>
<li>Technical support through official channels</li>
<li>Documentation and FAQ on the developer’s website</li>
<li>User community for experience sharing</li>
</ul>


KosTeams Payments for Yandex Pay and Yandex Split for WooCommerce

Accept payments via Yandex Pay, Yandex Split, or a combination of both. Increase conversion with flexible payment options using the KosTeams plugin.

Page Restrict for WooCommerce vs KosTeams Payments for Yandex Pay and Yandex Split for WooCommerce