srxwebdesign

<p>Contact Form 7 mollie integration helps you to integrate Mollie in your Contact Form 7. Please follow the guides carefully. Thanks.</p>
<h4>Docs and support</h4>
<ol>
<li>
<p>Go to settings and navigate to CF7 mollie Settings. Give your mollie API key and select forms you want to integrate. Select currency and Give redirect url.</p>
</li>
<li>
<p>Make a contact form 7 form.</p>
</li>
</ol>
<p>[text* your-email placeholder “Your Email”]<br />
[number* payment-amount placeholder “Payment Amount”]<br />
[submit “Pay with Mollie”]</p>
<ol>
<li>Now go to the page you added the contact form 7. You are good to go.</li>
</ol>
<h3>Demo</h3>
<p>https://test.srxwebdesign.com/cf7-mollie/</p>


Integration for CF7 and Mollie

Just another contact form 7 mollie integration. Simple but flexible.

Marcin Wosinek

<p>Fair Payments Connector is the money layer of the Fair Event plugin suite. It handles Mollie payment processing, stores transactions with line items, and provides a ledger for budgets and bank-import reconciliation.</p>
<p>Features:</p>
<ul>
<li>Mollie payment gateway with test/live modes, application fees, and webhook handling</li>
<li>Transactions with itemized line items, linked to posts, event dates (fair-events), and participants (fair-audience)</li>
<li>Status lifecycle (<code>draft</code> <span aria-hidden="true" class="wp-exclude-emoji">→</span> <code>pending_payment</code> <span aria-hidden="true" class="wp-exclude-emoji">→</span> <code>paid</code>/<code>failed</code>) with action hooks (<code>fair_payment_paid</code>, etc.)</li>
<li>Proactive status sync to recover stuck pending payments</li>
<li>Budgets and financial entries ledger with split entries, event linkage, and import deduplication</li>
<li>Many-to-many reconciliation between bank-import entries and transactions</li>
<li>Token-authenticated data sharing API so satellite sites can pull their own transaction data from a hub site</li>
<li>Telegram notifications on payment events</li>
<li>Gutenberg “Simple Payment” block (amount, currency, description) for standalone use</li>
<li>Admin pages for transactions, budgets, entries, reconciliation, API tokens, connected sites, and settings</li>
</ul>
<p>Public PHP API for integration from other plugins:</p>
<ul>
<li><code>fair_payment_create_transaction( $line_items, $args )</code></li>
<li><code>fair_payment_initiate_payment( $transaction_id, $args )</code></li>
<li><code>fair_payment_get_transaction( $transaction_id )</code></li>
<li><code>fair_payment_sync_transaction_status( $transaction_id )</code></li>
</ul>
<h3>Development</h3>
<ul>
<li>GitHub Repository: https://github.com/marcin-wosinek/fair-event-plugins</li>
<li>Report Issues: https://github.com/marcin-wosinek/fair-event-plugins/issues</li>
<li>Contribute: https://github.com/marcin-wosinek/fair-event-plugins/pulls</li>
</ul>
<h3>External services</h3>
<p>This plugin relies on the following third-party services. Data is only sent to a service when you enable and configure the related feature.</p>
<h4>Mollie payment gateway (api.mollie.com)</h4>
<p>Used to process payments. When a customer initiates a payment through the plugin (for example by submitting the Simple Payment block, or when another plugin calls <code>fair_payment_initiate_payment()</code>), the plugin contacts the Mollie API to create the payment and later to retrieve its status (including via Mollie webhooks and periodic status sync). Data sent includes: payment amount and currency, description, redirect/webhook URLs of your site, customer billing email when provided, and your Mollie access token. Mollie is operated by Mollie B.V.</p>
<ul>
<li>Terms of service: https://www.mollie.com/legal/user-agreement</li>
<li>Privacy policy: https://www.mollie.com/legal/privacy</li>
</ul>
<h4>Fair Event Plugins OAuth proxy (fair-event-plugins.com)</h4>
<p>Used only if you connect Mollie through the built-in OAuth flow instead of pasting a personal API key. The plugin redirects you to <code>https://fair-event-plugins.com/oauth/authorize</code> to authorize access to your Mollie account, and later calls <code>https://fair-event-plugins.com/oauth/refresh</code> to refresh the Mollie access token when it expires. Data sent includes: the OAuth refresh token stored in your site and, during initial authorization, the parameters Mollie returns to the proxy. The proxy is operated by the plugin author (Marcin Wosinek) and exists because Mollie OAuth requires a registered client secret that cannot ship in a public plugin.</p>
<ul>
<li>Terms of service: https://fair-event-plugins.com/terms/</li>
<li>Privacy policy: https://fair-event-plugins.com/privacy/</li>
</ul>
<h4>Telegram Bot API (api.telegram.org)</h4>
<p>Used only if you configure a Telegram bot token and chat ID in the plugin settings to receive payment notifications. When a payment event occurs (such as a payment being marked as paid or failed), the plugin sends an HTTP request to <code>https://api.telegram.org/bot<token>/sendMessage</code> containing the notification text (transaction id, amount, status, and a link back to the admin transaction page) and the configured chat id. The Telegram Bot API is operated by Telegram FZ-LLC / Telegram Messenger Inc.</p>
<ul>
<li>Terms of service (Bot API): https://telegram.org/tos/bot-developers</li>
<li>Privacy policy: https://telegram.org/privacy</li>
</ul>
<h4>Other WordPress sites you connect (hub / satellite data sharing)</h4>
<p>If you use the connected-sites / data-sharing feature, the plugin will send authenticated REST requests to the WordPress site URLs you explicitly enter in the “Connected sites” admin page so it can pull transaction data. No data is sent to those sites unless you configure them yourself. There are no third-party terms for this feature — the remote endpoint is another WordPress site running this same plugin, under your control.</p>


Fair Payments Connector

Mollie-based payments and bookkeeping for WordPress events.

Integration for CF7 and Mollie vs Fair Payments Connector