ifthenpay | Payments for WPForms
| 开发者 | ifthenpay |
|---|---|
| 更新时间 | 2026年10月15日 16:53 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
详情介绍:
- One-time payments through WPForms
- Support for orders
- Merchant backoffice (basic sales) on web + mobile
- Automatic payment confirmations (no card numbers stored) All settings are managed within WPForms and your ifthenpay Backoffice. The plugin is designed so store owners can handle payments without requiring advanced technical knowledge.
安装:
- Install: Upload the plugin zip via Plugins → Add New → Upload, or install from WordPress.org and Activate.
- Credentials: Ensure your ifthenpay account has an active WPForms Gateway Key with desired payment methods enabled.
- Setup: Go to WPForms → Settings → Payments and enter your Backoffice Key.
- Form config: Create/Edit a form → Payments tab → Add the Ifthenpay field on your form → enable "ifthenpay | Payment Gateway" and select a Gateway Key.
- Confirmation messages: In the same Payments tab, customize the Popup Confirmation Messages shown to customers for each payment outcome (Paid, Pending, Failed, Cancelled).
屏幕截图:
常见问题:
Does this plugin support recurring payments?
No. This version supports only one-time payments via pay-by-link.
Are payment details stored?
No. The plugin does not store card numbers or full banking details. Only minimal references required for payment matching are stored.
Which payment methods are supported?
Any method enabled on your ifthenpay Gateway Key (e.g. Multibanco, MB WAY, Payshop, Credit Card, Google Pay, Apple Pay, Pix).
How does the payment process work?
Customers submit a WPForm and are redirected to a secure ifthenpay-hosted payment page. After completing payment, ifthenpay sends a callback to update the payment status automatically.
Can I use WPForms coupons?
Yes. WPForms coupon and total fields are fully supported and automatically processed.
What happens if a payment fails?
The entry is marked as Failed. Customers can retry payment depending on your form setup.
Can I customize the payment experience?
Yes. You can configure button label, payment description, and styling via WPForms, plus a separate Popup Confirmation Message for each payment outcome (Paid, Pending, Failed, Cancelled). See "Popup Confirmation Messages" above.
What happens if my form also has another payment gateway field (PayPal, Stripe, Square, Authorize.Net)?
WPForms only allows one active payment method per submission, so the ifthenpay field automatically hides itself (logo, methods, and "Pay now" button) while another gateway's field is visible on the form. It reappears automatically if that other field is hidden again, e.g. by conditional logic. Only PayPal, Stripe, Square, and Authorize.Net fields count as competing gateways; WPForms' own Total, Coupon, and payment item fields do not.
Is there a sandbox?
ifthenpay may provide test entities; if unavailable, use a low-value live test.
How secure is the integration?
All requests are encrypted over HTTPS; no sensitive card data is stored.
Does ifthenpay's addon for WPForms accept WEBHOOKS(Callbacks)?
Yes! ifthenpay's addon for WPForms from version 2.0.0 and future ones accepts webhook(callbacks).
更新日志:
Stable tag in readme.txt to 2.1.2.
Fixed: Updated the version header in the main PHP file to 2.1.2.
2.1.1
Added: Enhanced payment description placeholders & Design change on the status popups.
2.1.0
Added: Title Configuration to the Gateway Configurations.
Fixed: custom Popup Confirmation Messages were replaced by the default text when the form was placed inside a page builder block that rewrites HTML attributes (e.g. Avada's Text Block).
Fixed: workaround for the new ajax verification on wpforms lite 2.0.2.1
Fixed: Function of description was not being wired onto the pay by link.
2.0.3
Fixed: optimize payment confirmation speed on frontend and improve server-side transaction tracking.
2.0.2
Fixed: plugin version metadata (Stable tag, plugin header) was not bumped for the 2.0.1 release; this maintenance release corrects it and re-syncs the WordPress.org listing.
2.0.1
Fixed: Sanitization function bug on the callback url.
2.0.0
Added: full webhook (callback) support — ifthenpay now notifies the site directly when a payment resolves, instead of relying on the customer's browser returning to the site.
Added: customizable Popup Confirmation Messages per payment outcome (Paid, Pending, Failed, Cancelled), configurable per form in the Payments tab. For the Paid outcome, choose a Confirmation Type — show a message in the popup, redirect to a WPForms page, or redirect to a custom URL — plus an optional entry preview shown after the message.
Added: two ready-made ifthenpay form templates (Simple and multi-page Complex), available from Add New Form with branded thumbnails.
Added: an "ifthenpay" light/dark theme preset selectable from WPForms' Themes tab.
Added: a daily cron that automatically expires stale "pending" payments left behind by abandoned or timed-out Pay By Link sessions.
Changed: payments now use a full-page redirect to ifthenpay's hosted payment page instead of the legacy modal/popup display; the unused transaction ID tracking that display relied on was removed.
Changed: when another WPForms payment gateway field (PayPal, Stripe, Square, Authorize.Net) is active on the form, the ifthenpay field now hides itself instead of showing a warning message.
Changed: a saved default payment method is now ignored if it's no longer enabled on the gateway, falling back to an available method instead of keeping a stale default.
Fixed: a real, non-zero order could be rejected with "Amount cannot be lower than 0" — a stray or empty submitted quantity for a field that doesn't actually support quantities (e.g. a payment checkbox) was being trusted and could zero out the total. Quantity is now only read from fields that have quantity enabled, matching WPForms' own core logic.
Fixed: pending, cancelled, and failed Pay By Link attempts now create a real WPForms entry and payment record (previously only completed payments did), so they show up correctly in Payments and Entries.
Fixed: the payment outcome popup no longer reopens on its own after being dismissed, e.g. when switching back to the browser tab, unless the payment status actually changed.
Security: payment completion is now confirmed exclusively via the verified webhook, rather than trusting the customer's browser return.
1.0.0
- Initial release: WPForms integration, ifthenpay payments, multi-method support, modal.