Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions
| 开发者 |
Mammothology
CoastMountain themeisle |
|---|---|
| 更新时间 | 2025年5月30日 16:50 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.8 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
标签
下载
详情介绍:
安装:
- Uninstall any previous version of the plugin (No data will be lost)
- Download this plugin.
- Login to your WordPress admin.
- Click on the plugins tab.
- Click the Add New button.
- Click the Upload button.
- Click "Install Now", then Activate, then head to the new menu item on the left labeled "Full Pay" and "Settings".
- Make sure you go through the Connect Account flows for both Live and Test modes.
- During the connect flow you can either connect to an existing Stripe account or create a new one
常见问题:
Do I need coding skills to use WP Full Pay
No, absolutely not! You can get your first payment form up and running with just a few clicks. However, if you have special requirements, you might want to customize the appearance with CSS styles, or hire a developer to develop extensions or integrations with other systems.
Do you offer trial or free plan?
Yes! You can use all of WP Full Pay for free, including all supported payment methods. The free version includes an application fee instead of a traditional license fee. We don't offer a trial version, but we do have a 14 day refund policy when buying a licen, so you can buy with confidence. The license will remove the application fee and give you access to one-to-one lightening fast, priority email support.
Can I upgrade my license?
Yes, you can upgrade any time, and you'll just pay the difference in license cost.
Does WP Full Pay work on a subscription basis?
When you purchase the plugin, you get a license for 12 months which covers also support (plugin versions v6.0) & updates. The plugin will continue to work on your site, even after your license expires. If you'd like to ensure uninterrupted access to support & updates, you should renew your license.
Does WP Full Pay work on WordPress.com?
Yes, WP Full Pay can be installed on WordPress sites hosted on WordPress.com
Does WP Full Pay work on WordPress multisite?
Yes, it works on WordPress multisite, and it requires a Business or Agency license.
Are there any transaction fees associated with using WP Full Pay?
No, WP Full Pay doesn't impose any extra transaction fees. However, it's important to note that users without a valid license incur an additional fee of 5%. Also, keep in mind that while using WP Full Pay is free of extra charges, Stripe has its own transaction fees as per their standard rates.
Do you offer support if I need it?
Certainly! We are always here to assist you. Support is provided to all users with a valid and active license key for plugin versions v6.0 and above. To help you get started, we've developed a comprehensive range of resources including plugin guides, knowledge base articles, and instructional videos. Additionally, for more personalized assistance, you're welcome to submit a ticket through our support helpdesk.
Can I use WP Full Pay for WooCommerce?
No, WP Full Pay is a standalone plugin, it's not a WooCommerce add-on. However, it can run alongside WooCommerce just fine.
Which payment forms I can create with WP Full Pay?
With WP Full Pay, you can create various types of payment forms, including one-time payments form, subscription forms, donation forms, etc. Here, you can learn more about creating payment forms.
Can I customize the payment forms created with WP Full Pay?
Totally! You can modify various elements like fields, buttons, and labels, and also integrate custom CSS for more advanced styling.
Can I select which payment methods show for my customers with WP Full Pay?
Yes! With version 7.1 and onwards, you can select which payment methods to make available to your customers. Note though that you can only suggest payment methods; Stripe will determine which payment methods are available to the customer based on their location and other parameters.
Is there a maximum amount that can be collected per payment?
There is no maximum amount set by WP Full Pay. However, Stripe may have its own limits depending on your account type and verification status. For high-value transactions, consult Stripe's documentation.
Can I accept credit card payments on mobile?
Absolutely! All payment forms created with WP Full Pay are fully responsive and mobile-optimized. Your customers can make payments from any device - smartphones, tablets, or desktop computers.
Can I create multiple payment forms?
Yes, you can create unlimited payment forms with WP Full Pay. Each form can have different settings, payment options, and designs to suit various needs across your website.
Where can payment forms be embedded?
Payment forms can be embedded anywhere on your WordPress site using shortcodes or our Gutenberg block. This includes pages, posts, sidebars, footers, or anywhere else you can add content on your site.
What are the fees for collecting payments?
The free version of WP Full Pay has a 5% application fee per transaction. If you upgrade to a licensed version, this fee is removed. Stripe's standard processing fees still apply to all transactions.
Can I collect more than just payment data from my customers?
Yes, WP Full Pay allows you to add custom fields to your payment forms to collect additional information from customers. This can include anything from product preferences to delivery instructions or any other data you need.
Can I accept recurring donations with WP Full Pay?
Yes! WP Full Pay supports recurring donations through Stripe's subscription system. This allows you to convert one-time donors into regular supporters, creating a reliable stream of income for your nonprofit or cause.
Can I create fundraising campaigns with goals?
Yes, with WP Full Pay you can set fundraising goals and display progress directly on your donation forms. This creates a sense of urgency and encourages donors to contribute to help reach your target.
Does WP Full Pay work with my theme?
Yes, WP Full Pay is designed to work with all standard WordPress themes. It has been specifically tested with popular themes including Astra, Neve, OceanWP, GeneratePress, and Kadence, ensuring seamless integration with these widely-used themes.
Is WP Full Pay secure?
Absolutely! WP Full Pay uses Stripe's secure Payment Element to collect card information. Your customers' sensitive payment data is sent directly to Stripe (PCI Level 1 certified) and never touches your WordPress server. This ensures maximum security and PCI DSS compliance without additional work on your part.
How does WP Full Pay handle SCA compliance?
WP Full Pay fully supports Strong Customer Authentication (SCA) requirements for European transactions through Stripe's implementation. When a payment requires 3D Secure authentication, the customer will be prompted automatically. This ensures your payments remain compliant with regulations like PSD2 in Europe.
更新日志:
Version 8.2.4 (2025-05-30)
- Improve upgrade checkout experience
- Fixed incorrect amount issue in payment details
- Updated dependencies
- Fixed _load_textdomain_just_in_time notice.
- Enhanced upgrade experience for Pro version users.
- Fixes an issue with the settings page not opening if the user has migrated from a version older than 8.0
- Fee Recovery Support – Added an option to pass Stripe and plugin fees to customers, either as an optional or required checkbox. This allows website owners to recover processing fees, ensuring they receive the full intended amount.
- Reporting Dashboard – Introduced a new reporting feature with key insights into transactions and revenue.
- Added an edit icon to the form listing screen for easier and more intuitive editing.
- Reverted the default form type from external to inline for better usability.
- Improved the admin status menu to remain visible at all times, regardless of test or live mode. Added a submenu for quick access to Forms, Transactions, and Settings. Adjusted visual cues for test and live modes for better clarity.
- Revamped the Settings Page for smoother navigation—introduced tabs and sub-tabs to make it easier to access different sections without returning to the main page.
- Streamlined Form Settings by moving site-wide settings to a global options section, reducing clutter in individual form settings while still allowing granular control when needed.
- Automatic Stripe Product Creation – Forms now automatically create a linked Stripe product, reducing setup steps for one-time and subscription payments.
- Fixed an issue where form preview did not reflect changes immediately. Users are now informed when a save is required before previewing, preventing confusion.
- Fixed an issue where save card forms did not work with external checkout. Now, selecting a save card form automatically switches to inline checkout and hides the checkout type setting to prevent confusion.
- Fixed a missing notice for Stripe connection status—users are now properly informed when disconnected from Stripe, both immediately after disconnection and on the Settings > Stripe page.
- Fixed a critical error when editing forms after disconnecting from Stripe. Now, instead of a fatal error, users see a clear message instructing them to reconnect their Stripe account. Admins also receive guidance when previewing or displaying forms on the frontend.
- Fixed an issue where custom amount fields caused an error for /bin/sh products, ensuring proper validation when allowing users to enter a custom amount.
- Fixed an issue where adding custom fields to save card forms did not work, ensuring proper functionality for collecting additional user information.
- Fixed an issue where decimal values were ignored in the Custom Amount option, preventing unintended overcharges and ensuring correct payment amounts.
- Fixed an issue where donation forms using inline checkout did not have a default product name, preventing the form from being saved. Now, it uses the same default name as checkout mode.
- Fundraisers can now set a donation goal and display progress directly on the form.
- Added a webhook feature available for all plans, allowing users to configure webhooks per form with a custom URL, request type, and headers. Webhooks trigger on successful transactions, and a test button is included for easy setup.
- Added a form preview feature, allowing users to quickly view their forms in a modal without manually inserting shortcodes on a page.
- Introduced a basic block for selecting and inserting available forms, eliminating the need to copy and paste shortcodes manually.
- Added compatibility with Stripe’s Customer Portal, allowing users to enable a setting that redirects customers to Stripe for subscription management, including upgrades, downgrades, and pauses.
- The setup notice can now be dismissed and includes a direct connection option for easier onboarding.
- The connection page has been simplified with a cleaner design, correct fee display based on user status, and button styling matching Stripe branding.
- The license key field has been moved to the plugin’s settings page for a more intuitive setup experience.
- Added transaction count bubbles in tab corners for better visibility and navigation.
- Renamed Forms to Payment Forms in the sidebar for better clarity.
- Updated the form creation flow to guide users when Stripe is not connected.
- Removed the Add-ons sub-menu, as add-ons are now part of plans.
- Added a simple onboarding flow to streamline Stripe connection and form creation.
- Added a test mode alert on forms and payment buttons, ensuring users know when transactions are in test mode, with a direct link to disable it.
- Simplified form creation by setting the default payment type to checkout for quicker setup and replacing the mode column with a shortcode that can be copied with one click.
- Fixed an issue where Stripe receipts were not being sent when the option was enabled.
- Improved loading behavior on the WordPress plugin page for a smoother experience.
- Improve error messages and error handling
- The Payments Plugin is now under the ownership of Themeisle.
- Breaking Change: This version requires users to reconnect their Stripe account. This step is necessary to ensure full compatibility with the latest updates.
- Fixes various PHP errors.
- Fix: corrected error regarding liveEventTitle on new installs
- Fix: improve javascript to avoid browser console errors
- Fix: get rid of undefined array key warning
- Fix: fixing cases of invalid format of custom amounts
- Fix: include email in checkout forms if configured
- Feat: Include full address for Stripe auto-tax calculations
- Fix: Fixing cases where charge cannot be found
- Fix: Errors showing up on custom fields with more than one form on the same page
- Fix: Case of error thrown when customer tried to undo a cancellation
- Updated name of plugin to show source of download (FM=Freemius, WP=wordpress.org)
- Fix: fixed issue where Stripe settings wouldn't save
- Fix: fixed issue where using a custom value caused issues loading the form
- Fix: fixed issue where amount would end up in an invalid format
- Fix: Upgraded Freemius SDK to 2.7.4
- Updated supported WordPress version to 6.6
- Fix: Fixed issue with missing account ID
- Fix: Fixed sending subscription related test emails
- Fix: "Invalid Integer" error has been fixed
- Fix: Save card forms works again after clearing and re-connecting Stripe
- Fix: Fixed issue when saving some forms
- NOTE: existing one-off forms default to support cards and Link.
- NOTE: To use the new payment methods you must have gone through the "Connect Live Account" flow via Full Pay -> Settings -> Stripe Account.
- Feature: Support for new payment methods on one-off forms: Bancontact, BLIK, EPS, iDEAL, Przelewy24, TWINT
- Feature: Select which payment methods to show (or not). Includes credit cards, AliPay, Amazon Pay, Bancontact, BLIK, Cash App Pay, EPS, GrabPay, iDEAL, Stripe Link, MobilePay, Przelewy24, Revolut Pay, TWINT, and WeChat Pay
- NOTE: existing forms default to support cards and Link.
- NOTE: To use the new payment methods you must have gone through the "Connect Live Account" flow via Full Pay -> Settings -> Stripe Account.
- Fixed: Updated customer portal to not load invoices if customers don't have access to see invoices
- Fixed: addressed a couple of warnings and unnecessary log messages
- Fixed: updated handling of coupon codes on subscriptions to reflect Stripe's changes
- Fixed: fixed issue causing 'validLicense' error
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: Fixed issue with test vs live on a few requests around invoices and customer
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: Solved an issue for a few requests to list prices
- Fixed: "Bad request" error caused by not finding some donations plans
- Fixed: Issue with customer not found when creating some subscriptions
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: Prevent showing unnecessary errors messages before completing Stripe Connect flow
- Hotix: Issue with mismatch of Stripe keys found in 7.0.20, please upgrade
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Feature: migrated to new and faster Connect backend that will speed up the overall user experience
- Fixed: improved speed of listing forms in the admin view
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- fixed: corrected when "restricted soon" error is shown for Stripe account status
- fixed: corrected logic around updating payment intents
- fixed: corrected handling of live and test account IDs to address deprecation notice in logs
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- fixed: implemented nonce check on admin urls to prevent Cross-Site Request Forgery (CVE-2023-47667)
- fixed: corrected issue on calculating billing cycle
- fixed: corrected issues when refunding transaction
- deprecation: removed DemoMode option
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: corrected issue around subscribing customers to plan
- Fixed: only shows reminder notice of live mode account hasn't been connected; test mode is not strictly necessary
- Fixed: Upgraded Freemius SDK to 2.7.2
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: corrected issue in checkout causing "redirect-url" error
- Fixed: Stripe account status Enabled and Connected now both count as having completed the account setup
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: corrected issue with checkout-style subscriptions with setup fees
- Fixed: Use built-in WordPress method for getting time zone
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: corrected help link around setting up customer portal
- Fixed: added/improved spinners on customer portal to let customers know something is happening
- Fixed: improved migration from v5.x
- Fixed: error throw on missing payment intent
- Fixed: unblock editing of one-time forms
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: resolved issue when reactivating cancelled Subscription
- Fixed: don't check for CVC for ApplePay, GooglePay, and other wallets
- Fixed: improved default styling of form fields to match default stripe payment element style
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: Issue saving card using Stripe Link
- Updated supported WordPress version to 6.5
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Added: ability to clear Test/Live Stripe setup. This can help connect to a different account
- fixed: settings page not available for some configurations
- fixed: bug around null or whitespace
- Improved onboarding
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: brought back the Account page
- Improved onboarding
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: increased timeout for some requests that needed more time
- Fixed: 3DSecure issue that kept customers waiting
- Improved onboarding
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: Issue with coupons not applying
- Fixed: Stripe client was missing for customer portal customizations. Note that customizations still require the Stripe secret key to be added to the configuration.
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: bug in customer portal
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Replaced customer portal stripe card elements with stripe payment element for updating payment method
- Fixed: bug when updating customers in stripe
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: bug in retrieving customers
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Use "card holder name" instead of "billing name" when sending card data to Stripe. This will provide more accurate date for Stripe's Radar product and other anti-fraud measures
- Fixed: bug with stripeAccount
- Fixed: bug getting prices
- Fixed: bug getting prices in non-connect integration
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: issue in non-connect integration
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: Checkout bug
- Fixed: bug in customer portal
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Fixed: bug in customer portal
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Added support for AliPay, ApplePay, GooglePay, and Stripe Link
- Replaced old Stripe Elements with the new Stripe Payment Element
- Connects more securely to Stripe via Stripe Connect. This also allows our support team to better assist you with issues that cross over to Stripe.
- Updated knowledge base with improved search. Access from the "?"-menu in the admin views
- Fixed: a number of smaller bugs
- NOTE: For v7.0 and onwards, FullPay will work without an active license, but will add an application fee of 5% per transaction. To avoid application fees make sure to always have an active license.
- NOTE: If upgrading from a previous version, your forms will continue to work while you go through the Stripe connect flow
- Added support for future amount placeholders for subscriptions with a trial period. %PLAN_FUTURE_AMOUNT_NET%, %PLAN_FUTURE_AMOUNT_VAT%, and %PLAN_FUTURE_AMOUNT_GROSS%
- Added option to select an image on checkout donation forms
- Fixed bug where Stripe only returns some prices
- Include Washington DC as a state
- Fixed a critical security issue.
- Fixed a checkout form crash when billing and shipping fields are turned on.
- Fixed some minor bugs
- Stripe Tax is supported on one-time payment forms and subscription forms.
- Both exclusive and inclusive tax rates can be used for tax calculations.
- Form fields can be set via URL parameters.
- Price selectors of inline forms always display gross prices, and update the prices when the form changes.
- Log messages are stored in the WordPress database, and log messages can be downloaded from WP admin.
- Phone number can be collected on checkout forms.
- Updated the display languages and translations of checkout forms.
- The plugin is now called WP Full Pay.
- Javascript files are excluded automatically from Rocket Loader of Cloudflare.
- Fixed: Promotion codes applied to inline forms are redeemed as promotion codes, not as discounts.
- Fixed: The customer portal redirects to the login page if the portal is accessed without being logged in.
- Fixed: Upgraded the Freemius SDK to v2.5.3 for greater compatibility with PHP 8.1.
- Fixed: The customer portal displayed incomplete subscriptions.
- Fixed: The customer portal didn't display the default card if the card was added on the Stripe dashboard.
- Fixed: The customer portal displayed only the last 10 invoices of the customer.
- Fixed: The subscription summary on the customer portal wasn't up-to-date until the focus left the quantity stepper.
- Fixed: The 'amount' property of the $params array of after-payment action of inline subscriptions wasn't set when 3DS was used.
- Fixed: The 'currency' property of the $params array of after-payment action of subscriptions (inline, checkout) wasn't set.
- Fixed: Some translations were missing from all language bundles.
- Fixed: Coupons couldn't be applied to products on one-time payments forms if there was only one product added to the form.
- Fixed: Long transaction description could cause sql insert error on one-time payment and donation forms.
- Fixed: A javascript error occurred when the prices were recalculated on checkout payment and subscription forms.
- Fixed: Some checks were not working properly for the minimum subscription quantity on the customer portal.
- Fixed: The fullstripe_after_subscription_charge action received a NULL Stripe subscription object after 3DS/SCA authentication (caused a problem in WP Full Stripe Members as well).
- Fixed: Promotion codes were case-sensitive on inline payment and subscription forms.
- Fixed: Fixed-amount coupons didn't work on inline payment forms with the custom amount option selected.
- Custom field values are stored in the WordPress database, and are displayed on the transaction details page.
- Coupons can be redeemed only for supported products on inline forms.
- Added the %IP_ADDRESS% placeholder for the IP address of the customer.
- Added a section dedicated to add-ons on the 'Full Stripe / Settings' page in WP admin.
- Implemented minimum quantity for buying subscriptions (buying subscriptions in bulk).
- Added filters to display additional information on the top and bottom of the customer portal page.
- Added option to show/hide the 'Subscriptions' section on the customer portal.
- Added option to toggle scrolling on the customer portal.
- Fixed: When logging in to the customer portal, the email address was case-sensitive for customers stored in the WordPress database.
- Fixed: Redeeming promotion codes was case-sensitive on inline forms.
- Fixed: Fixed-amount coupons on custom-amount one-time payment forms couldn't be redeemed.
- Fixed: The 'stripeSubscription' parameter of the 'fullstripe_after_subscription_charge' action was null when called after an SCA 2nd-factor authentication.
- Fixed: Some subscriptions started on checkout forms remained in the "Incomplete" state in WP admin.
- Fixed: Custom amount payments on inline one-time payment forms generated a PHP notice.
- Fixed: The "Full Stripe / Transactions" page for subscriptions generated a PHP notice when the WordPress timezone wasn't a named one but an UTC offset.
- Customer portal with account selector (multiple Stripe customers using the same email address).
- Customer portal filters out and hides zero-amount invoices.
- Shortcodes are resolved in plugin email templates.
- Minimum donation amount option on donation forms.
- Minimum payment amount option on one-time payment forms.
- Generating invoices for donations.
- Logging and displaying the IP address of customers on the plugin dashboard.
- Facility to send plugin emails for testing purposes.
- WordPress filter to add URL parameters to thank you page URLs.
- WordPress filter to restrict the list of billing and shipping countries.
- Portuguese translation for all customer-facing UI.
- The Stripe PHP client has been upgraded to v7.114.0 .
- The Freemius SDK has been upgraded to v2.4.3 .
- Reversed the order of Google reCaptcha fields so that it matches the order on the Google settings page.
- Fixed: WordPress timezone settings taken into account when displaying dates and times in WP admin
- Customer portal with account selector (multiple Stripe customers using the same email address).
- Customer portal filters out and hides zero-amount invoices.
- Shortcodes are resolved in plugin email templates.
- Minimum donation amount option on donation forms.
- Minimum payment amount option on one-time payment forms.
- Generating invoices for donations.
- Logging and displaying the IP address of customers on the plugin dashboard.
- Facility to send plugin emails for testing purposes.
- WordPress filter to add URL parameters to thank you page URLs.
- WordPress filter to restrict the list of billing and shipping countries.
- Portuguese translation for all customer-facing UI.
- The Stripe PHP client has been upgraded to v7.114.0 .
- The Freemius SDK has been upgraded to v2.4.3 .
- Reversed the order of Google reCaptcha fields so that it matches the order on the Google settings page.
- Fixed: WordPress timezone settings taken into account when displaying dates and times in WP admin
- IMPORTANT: There are breaking changes if you're upgrading from v5.5.x or earlier, check out our blog post
- Fixed: The customer portal didn't work with some WordPress themes and page builders due to a HTML escaping issue.
- Fixed: The plugin threw an error when activating it on a WordPress site powered by PHP v8.1.
- IMPORTANT: There are breaking changes if you're upgrading from v5.5.x or earlier, check out our blog post
- Fixed: A high-priority security issue.
- Fixed: When using payment in installments -type plans on checkout subscription forms, the charge count didn't get refreshed in certain cases.
- IMPORTANT: There are breaking changes if you're upgrading from v5.5.x or earlier, check out our blog post
- Fixed: Inline one-time payment forms charged the wrong amount when a one-time payment was followed by a subscription for the same Stripe customer.
- Fixed: When the custom amount payment option was combined with a single product added to a payment form then the custom amount selector wasn't displayed.
- Fixed: The fullstripe_modify_email_message filter didn't work for the member registration email of WP Full Stripe Members.
- IMPORTANT: There are breaking changes if you're upgrading from v5.5.x or earlier, check out our blog post
- Added option to turn off invoice generation on one-time payment forms (turned off by default).
- Fixed: The tax id wasn't saved to the Stripe customer in some cases on inline subscription forms.
- IMPORTANT: There are breaking changes if you're upgrading from v5.5.x or earlier, check out our blog post
- Added filter for the post types supported by Thank you pages.
- Added Romanian translation (thanks monk Theologos)
- Added Portuguese (partial) translation (thanks João Gonçalo Dias)
- Fixed: Default billing country couldn't be selected if no tax is collected.
- Fixed: The donation email template of the plugin was reset when the plugin was updated.
- Fixed: When the applied coupon was applicable only for certain number of recurring charges, the "Payment details" popover was empty.
- Fixed: The length of custom field labels wasn't validated.
- Fixed: For live transactions, the plugin displayed 'Test' API mode label in the "Transaction details" side pane.
- Fixed: Shortcodes weren't resolved within the "Thank you" page shortcodes.
- IMPORTANT: There are breaking changes if you're upgrading from v5.5.x or earlier, check out our blog post
- Fixed: The payment details popover was empty when plans of different recurring intervals were listed on subscription forms.
- Fixed: Stripe email receipts weren't sent on inline one-time payment forms.
- Fixed: The payment amount was always appended to the payment button text, even in absence of the {{amount}} placeholder, on one-time payment forms.
- Fixed: The "Other" payment option (custom amount) wasn't localized properly.
- Fixed: The query to populate the thank you pages dropdown on the "General" tab of forms could run out of memory when there were pages/posts with lot of metadata.
- Fixed: The product name was fixed as "My product" when a custom amount was entered on one-time payment forms.
- Fixed: There was "null" displayed as country for tax rates with no country specified.
- IMPORTANT: There are breaking changes if you're upgrading from v5.5.x or earlier, check out our blog post
- Fixed: Forms weren't displayed on the "Manage forms" page of some websites.
- Fixed: The webhook endpoint returned ERR 500 when a test webhook event was sent from the Stripe dashboard.
- Fixed: The interval label of subscriptions was wrong in some cases on the "Full Stripe / Transactions / Subscriptions" page.
- Fixed: A full-blown error with stack trace was shown if there was no product or plan on the form.
- Fixed: 3D Secure authentication didn't work properly on inline one-time payment forms in some cases.
- IMPORTANT: There are breaking changes if you're upgrading from v5.5.x or earlier, check out our blog post
- Fixed: Forms weren't displayed on the "Manage forms" page of some websites.
- Fixed: The "Settings" link didn't work properly on the "Plugins" page.
- Fixed: Freemius customers received an "Access denied" error when tried to open the "Full Stripe / Settings" page.
- Fixed: The "Terms and condition" label wasn't loaded properly when it contained double quotes.
- IMPORTANT: There are breaking changes if you're upgrading from v5.5.x or earlier, check out our blog post
- Fixed: One-time payment forms with the 'Custom amount' payment type couldn't be saved.
- IMPORTANT: There are breaking changes if you're upgrading from v5.5.x or earlier, check out our blog post
- Completely redesigned admin/dashboard experience
- Tax calculations use Stripe tax rates (exclusive) on one-time payment and subscription forms, inline and checkout alike.
- One-time payment forms use Stripe products, just like subscription forms do.
- Coupon field option added to all one-time payment and subscription form types.
- Shipping address option added to checkout one-time payment and checkout subscription forms.
- The "Manage subscriptions" page has been renamed to "Customer portal".
- Customers can upgrade/downgrade subscriptions on the "Customer portal" page.
- Administrators can configure whether subscriptions are cancelled at the end of period or immediately on the Customer portal.
- The plugin generates invoices also for one-time payments.
- The one-time donation frequency is now optional on donation forms.
- Business, Agency, and Unlimited licenses can be network-activated with a singe click.
- Completely redesigned/extended function signatures for before/after payment action hooks.
- Action/filter hooks can throw a user-friendly exception shown as a banner error on payment forms.
- New webhook URL added while keeping the legacy webhook URL as well.
- Forms can be cloned on the "Manage forms" page.
- Placeholder tokens can be used in email subjects.
- The Stripe PHP client has been upgraded to v7.67.0 .
- The Freemius SDK has been upgraded to v2.4.1 .
- Full support for tax calculations based on Stripe tax rates (exclusive) on one-time payment and subscription forms, inline and checkout alike.
- Completely redesigned admin/dashboard experience
- The Stripe PHP client has been upgraded to v7.67.0 .
- The Freemius SDK has been upgraded to v2.4.1 .
- One-time payment forms use Stripe products, just like subscription forms do.
- Coupon field option added to checkout subscription forms.
- Coupon field option added to inline and checkout one-time payment forms.
- Shipping address option added to checkout one-time payment and checkout subscription forms.
- The "Manage subscriptions" page has been renamed to "Customer portal".
- Customers can upgrade/downgrade subscription plans on the "Customer portal" page.
- Administrators can configure the Customer portal so that subscriptions are cancelled at the end of period, not immediately.
- The plugin generates invoices also for one-time payments (except auth & capture forms).
- The one-time donation frequency is now optional on donation forms.
- Business, Agency, and Unlimited licenses can be network-activated with a singe click.
- Completely redesigned/extended function signatures for before/after payment action hooks.
- Action/filter hooks can throw a user-friendly exception shown as a banner error on payment forms.
- New webhook URL added while keeping the legacy webhook URL as well.
- Placeholder tokens can be used in email subjects.
- New placeholder token for the coupon code applied: %COUPON_CODE%.
- New placeholder token for payment amount with a coupon applied: %AMOUNT_DISCOUNTED%.
- New placeholder token for donation frequency: %DONATION_FREQUENCY%.
- New placeholder token for the Stripe invoice number: %INVOICE_NUMBER%.
- New placeholder token for the Stripe subscription receipt: %RECEIPT_URL%.