RyanPay Card Payments with accept.blue for Formidable
| 开发者 | ryanplugins |
|---|---|
| 更新时间 | 2026年6月19日 17:11 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
Secure Form Checkout 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.
This is the free Lite version.
What's Included in Lite
- Credit card payments via accept.blue Hosted Tokenization iFrame — card data never touches your server
- Test / Sandbox mode — safely test payments with accept.blue sandbox credentials before going live
- Test Connection — verify your API credentials without leaving WordPress
- Debug logging — dedicated per-month log file with an in-admin log viewer, gated behind a settings toggle
- card authentication — optional EMV card authentication browser-based authentication per Form Action
- Per-form API credential override — run different forms against different accept.blue merchant accounts
- Processing overlay — animated spinner shown on form submit while payment processes
- Minified assets — production-ready JS and CSS; source files served automatically when WP_DEBUG is on
- Recurring payments & subscriptions — automatic recurring billing on a schedule, managed directly from accept.blue
- Installment plans — split a charge into scheduled installments
- Saved cards / Customer vault — let returning customers reuse a saved card without re-entering details
- Digital wallets — accept Google Pay at checkout in addition to manually entered cards
- ACH / eCheck payments — accept bank transfers in addition to cards
- Full transactions dashboard — searchable, filterable transaction history inside WordPress with refund and sync actions
- Priority support
- WordPress 6.0 or higher
- PHP 7.4 or higher
- Formidable Forms Pro (required for payment fields)
- An active accept.blue merchant account (sign up at https://accept.blue)
安装:
- Upload the plugin folder to /wp-content/plugins/ or install via Plugins > Add New > Upload Plugin.
- Activate via Plugins > Installed Plugins.
- Go to Formidable > Global Settings > Accept.Blue.
- Enter your credentials:
- API Key — from your accept.blue portal under API Keys
- PIN — if your API key requires one (optional)
- Hosted Tokenization Key — from accept.blue Settings > Hosted Tokenization
- Click Save Changes and use the Test Connection button to confirm your credentials work.
- Create or open a Formidable Form.
- Drag the Accept.Blue Card field onto the form canvas.
- Open Form Actions and add the Accept.Blue Payment action.
- Set your amount and currency.
- Click Update and publish your form.
常见问题:
Does this store card numbers on my server?
No. Card data is tokenised entirely within the accept.blue Hosted Tokenization iFrame. Your server only ever receives a short-lived nonce token. No card numbers, CVVs, or expiry dates are stored on your server or in your database.
Can I use this in test/sandbox mode?
Yes. Enable Test / Sandbox Mode in Formidable > Global Settings > Accept.Blue and use your accept.blue sandbox credentials. No real charges are made. Disable the setting and switch to live credentials when you are ready for production.
What statuses does the plugin use?
complete — charge captured and settled; auth — authorised but not yet captured; failed — charge declined or errored; voided — authorisation cancelled before capture; refunded — charge refunded in full or in part.
Does debug logging store sensitive data?
API request and response bodies are logged when debug logging is enabled. Card numbers are never present (they are handled by the accept.blue iFrame and never reach your server), but disable debug logging once you have finished troubleshooting. No card data is stored on your server. All sensitive payment data is handled exclusively by accept.blue's PCI-compliant infrastructure.
更新日志:
1.0.9
- New: Added "Settings" and "Upgrade to Pro" links to the plugin row on the Plugins screen.
- New: Added an upgrade notice with a link to the Pro version on the Accept.Blue settings tab.
- Docs: Added a Lite vs Pro feature comparison to the readme.
- Docs: Removed Paay external service section from readme. Replaced all "3D Secure" references with "card authentication".
- Fix: Added phpcs:ignore annotations for frm_payment_status_complete (Formidable Forms own hook) and $frmProErrors (Formidable Forms core global) — these cannot be renamed as they are part of Formidable Forms API.
- Fix: All plugin identifiers (functions, classes, constants, options, transients, AJAX actions, script/style handles, shortcodes, DB table) renamed from frm_ab_lite_ / Frm_AB_Lite_ / FRM_AB_LITE_ to ryancapa_ / Ryancapa_ / RYANCAPA_ to satisfy the WordPress.org 4-character unique prefix requirement.
- Fix: Include files and asset files renamed to match new prefix (class-ryancapa-*.php, ryancapa-card.js, ryancapa.css).
- Fix: Dependency notice (Formidable Forms required) now shown only on the Plugins screen instead of every admin page, complying with Guideline 11.
- Fix: Card config delivery rewritten to be JS-optimizer-proof. Configs are now collected across all card fields on the page and output as a single
wp_add_inline_script( 'before' )block that travels with the registered script handle, preventing WP Rocket / Autoptimize / LiteSpeed from stripping or deferring it.wp_localize_scriptretained as a secondary fallback for strict-CSP environments.
- Fix: Replaced raw inline
<style>tag in card field output withwp_add_inline_style()per WP enqueue best practices. - Fix: Replaced raw inline
<script>config output (printf) withwp_add_inline_script()per WP enqueue best practices. - Fix: Added nonce verification (
wp_verify_nonce) to the log viewer GET handler; all log viewer links updated to usewp_nonce_url(). - Docs: Updated External Services documentation.
- Fix: Multisite / Network activation — payments table now created for every subsite; settings stored per-site so each subsite has independent API credentials.
- Fix: Card iframe now loads correctly on all themes — CSS overrides prevent themes from collapsing the iframe to zero height; MutationObserver forces visibility the instant the SDK injects the iframe.
- Fix: JS config (ryancapaCardConfigs) output as a direct inline script in form HTML, immune to WP Rocket / Autoptimize / LiteSpeed JS optimizers stripping wp_localize_script data.
- Fix: Nonce refresh via admin-ajax (same session context) instead of REST endpoint, preventing -1 / HTTP 403 errors after authentication challenge.
- Fix: AJAX payment call migrated from jQuery.post() to fetch() with X-Requested-With header, preventing Apache 403 blocks on some server configurations.
- Fix: 10-second ready timeout with actionable error message; HTTP detection shows clear admin notice when page is not HTTPS.
- Tested: Verified working on WordPress Multisite with Network activation.
- Fixed: Added nonce verification to settings save path in route() to prevent CSRF
- Fixed: Removed recurring, installment, and trial fields from prepare()/get_defaults() — recurring is not implemented in Lite and was dead code
- Fixed: Updated accept.blue Terms of Service and Privacy Policy URLs to correct paths (/terms-of-use/ (contains both terms and privacy policy))
- Fixed: Updated admin upsell notice and readme to accurately reflect which features are in Lite vs Pro
- Fixed: card authentication and per-form API credential override are fully functional in Lite — moved from Pro-only list to Lite feature list
- Fixed: Removed recurring-related JavaScript toggle code from admin panel (no recurring UI in Lite)
- Fixed: Removed screenshot reference to recurring payment settings panel (no such UI in Lite)
- Initial Lite release based on Pro v1.0.0
- Core credit card payments via accept.blue Hosted Tokenization iFrame (PCI-minimised)
- Debug logging with in-admin log viewer and Clear Log function
- card authentication browser-based authentication per Form Action
- Per-form API credential override for multi-merchant support
- Licensing system fully removed
- All PHP identifiers prefixed with _lite (classes, functions, constants, options, hooks, DB tables)
- Plugin entry file renamed to formidable-acceptblue-lite.php
- All include files renamed to class-ryancapa-*.php