WP-Biz (Ryan)

<p>The “honeypot” technique for SPAM protection is invisible to humans, and tricks robots into filling out an invisible form field. Then, if that invisible field has been filled, the form cannot be submitted. Easy, non-instrusive SPAM protection.</p>
<p>No settings to set, this honeypot is added to all Formidable forms on your site, unless the user is logged in. When SPAM is suspected, the form will not be submitted and the visitor will be alerted to this fact.</p>
<p>Tested to work with both <strong>Formidable</strong> (free) and <a href="http://www.wpbiz.co/go/forms" rel="nofollow ugc">Formidable Pro</a> (best bet for awesome form power!)</p>
<p><strong>A note to Formidable Pro users:</strong> You paid to receive extra features in the Formidable plugin. Me too, it’s well worth it. This Honeypot plugin, and Ryan (the developer) are not connected to Formidable in any way. Since this adds another very helpful feature to Formidable, I ask you to send a <a href="http://wpbiz.co/donate/" rel="nofollow ugc">donation at WPbiz.co</a> to say thanks and encourage future developemnt.</p>


Formidable Honeypot

Add SPAM protection to your Formidable forms without annoying your visitors with Captchas, math, or other fields.

Ryan Tipones

<p><strong>Secure Form Checkout</strong> connects your Formidable Forms payment forms to the accept.blue payment processing platform. All card data is handled inside a secure accept.blue Hosted Tokenization iFrame — it never passes through your server, keeping your site PCI-compliant.</p>
<p>This is the <strong>free Lite version</strong>.</p>
<h4>What’s Included in Lite</h4>
<ul>
<li><strong>Credit card payments</strong> via accept.blue Hosted Tokenization iFrame — card data never touches your server</li>
<li><strong>Test / Sandbox mode</strong> — safely test payments with accept.blue sandbox credentials before going live</li>
<li><strong>Test Connection</strong> — verify your API credentials without leaving WordPress</li>
<li><strong>Debug logging</strong> — dedicated per-month log file with an in-admin log viewer, gated behind a settings toggle</li>
<li><strong>card authentication</strong> — optional EMV card authentication browser-based authentication per Form Action</li>
<li><strong>Per-form API credential override</strong> — run different forms against different accept.blue merchant accounts</li>
<li><strong>Processing overlay</strong> — animated spinner shown on form submit while payment processes</li>
<li><strong>Minified assets</strong> — production-ready JS and CSS; source files served automatically when WP_DEBUG is on</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 6.0 or higher</li>
<li>PHP 7.4 or higher</li>
<li>Formidable Forms Pro (required for payment fields)</li>
<li>An active accept.blue merchant account (sign up at https://accept.blue)</li>
</ul>
<h3>Source code</h3>
<p>The unminified source files for all JavaScript and CSS are included in the plugin’s assets/ directory alongside the minified production files. No separate build step is required to review the source.</p>
<h3>External Services</h3>
<p>This plugin connects to the accept.blue payment processing platform. Two distinct accept.blue services are contacted:</p>
<h4>1. accept.blue Payment API</h4>
<p>Used to authorise and capture credit card payments. When a visitor submits a payment form, the plugin sends a server-side request to the accept.blue API to process the charge.</p>
<p>Data sent: a short-lived card nonce token (generated by the Hosted Tokenization iFrame — never the raw card number or CVV), the payment amount, currency code, and the site’s accept.blue API credentials.</p>
<p>When data is sent: only when a visitor submits a payment form and the tokenization step has completed successfully.</p>
<ul>
<li>API endpoint (live): https://api.accept.blue/api/v2/</li>
<li>API endpoint (sandbox): https://api.sandbox.accept.blue/api/v2/</li>
<li>accept.blue website: https://accept.blue</li>
<li>API documentation: https://docs.accept.blue/api/v2</li>
<li>Terms of Service / Privacy Policy: https://accept.blue/terms-of-use/</li>
</ul>
<h4>2. accept.blue Hosted Tokenization Service</h4>
<p>Used to securely capture card details inside an iFrame. When a visitor views a payment form, the browser loads a secure iFrame from accept.blue’s tokenization service. The visitor enters their card number, expiry, and CVV directly into this iFrame. That card data is sent from the visitor’s browser directly to accept.blue — it never passes through your WordPress server.</p>
<p>Data sent: raw card details (card number, expiry, CVV) sent from the visitor’s browser directly to accept.blue’s tokenization servers. Your server receives only a short-lived nonce in return.</p>
<p>When data is sent: when the visitor enters card details and submits the payment form.</p>
<ul>
<li>Tokenization endpoint (live): https://tokenization.accept.blue/tokenization/v0.3/</li>
<li>Tokenization endpoint (sandbox): https://tokenization.sandbox.accept.blue/tokenization/v0.3/</li>
<li>Terms of Service / Privacy Policy: https://accept.blue/terms-of-use/</li>
</ul>


RyanPay Card Payments with accept.blue for Formidable

Accept credit card payments through accept.blue directly inside your Formidable Forms.

Formidable Honeypot vs RyanPay Card Payments with accept.blue for Formidable