=== SutraPay for Stripe ===
Contributors: fresheradvice
Tags: woocommerce, stripe, payment gateway, apple pay, sepa
Requires at least: 6.4
Tested up to: 7.1
Requires PHP: 8.0
Stable tag: 0.13.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Accept cards, Apple Pay, Google Pay, Link, SEPA Direct Debit, iDEAL, Klarna and more on WooCommerce with Stripe.

== Description ==

SutraPay for Stripe is a free Stripe payment gateway for WooCommerce.

**Payment methods**

* Stripe's Payment Element at checkout: cards (3D Secure 2, SCA-ready), Link, and every local payment method you turn on in your Stripe Dashboard — SEPA Direct Debit, iDEAL, Bancontact, EPS, Przelewy24, Klarna, Afterpay / Clearpay, Affirm, US bank accounts (ACH), Cash App Pay and more. Stripe only shows a method where it suits the customer's country, the currency and the amount.
* Express checkout with Stripe's Express Checkout Element: Apple Pay, Google Pay and Link buttons (plus PayPal and Amazon Pay when enabled in Stripe) above the checkout form, on the cart and on product pages ("Buy now"), with wallet-driven shipping address and rate selection.
* Full support for the WooCommerce Cart and Checkout blocks and the classic checkout, the order "Pay" page and My Account > Add payment method.

**Safe by design**

* The payment is created and confirmed on the server only after WooCommerce has validated the checkout and created the order, for exactly the order total — a refused checkout never charges the customer.
* 3D Secure and bank redirects return to a page that reads the payment's real status from Stripe before the order is marked paid; webhooks finish the order if the customer never comes back.
* Methods that settle later (SEPA Direct Debit, ACH, Bacs) put the order On hold until Stripe confirms the payment.

**Store tools**

* Saved payment methods (cards, SEPA Direct Debit, bank accounts, Link) for logged-in customers, with labels.
* Full and partial refunds and manual capture from the order screen; refunds made in the Stripe Dashboard are recorded on the order.
* WooCommerce Subscriptions: sign-up (including $0 free trials), automatic renewals with any saved reusable method (also for subscriptions bought with Apple Pay / Google Pay), retries, and customer / admin payment method changes.
* Disputes screen with text and file evidence; Payouts screen with the orders in each payout; per-order Stripe fee, net and availability date.
* Webhooks with signature verification and a one-click "create the endpoint for me" button; Stripe Radar reviews put the order on hold.
* One settings app (Dashboard, Settings, Payment Methods, Disputes, Payouts, Webhooks, Logs) with a setup checklist.

== Installation ==

1. Install the plugin from the Plugins screen (or upload the zip) and activate it. WooCommerce must be installed and active.
2. Go to WooCommerce > SutraPay for Stripe > Settings and add your Stripe publishable and secret keys (test mode is on by default). Use "Test connection" to confirm they work.
3. Open Webhooks and click "Create / Sync webhook" (or add the shown URL in your Stripe Dashboard).
4. In your Stripe Dashboard, under Settings > Payment methods, turn on the payment methods you want to offer.
5. Open Payment Methods to set up the express checkout buttons and register your domain for Apple Pay.
6. Place a test order with one of Stripe's test cards to confirm everything works end to end.

== Frequently Asked Questions ==

= Does this require WooCommerce? =

Yes. The plugin shows an admin notice and stays inactive until WooCommerce is installed and active.

= Where do I choose which payment methods appear at checkout? =

In your Stripe Dashboard, under Settings > Payment methods. The Payment Element shows the ones you turned on that are available for the order (country, currency, amount). No setting in WordPress is needed for a new method.

= Why is an order paid with SEPA Direct Debit "On hold"? =

SEPA Direct Debit, ACH and Bacs take a few days to confirm. The order stays On hold until Stripe reports the payment as succeeded (then it moves to Processing / Completed) or failed. This needs the webhook endpoint.

= Is the customer ever charged when the checkout is refused? =

No. The payment details are only collected in the browser; the charge is made on the server after WooCommerce has validated the checkout and created the order.

= Does this support WooCommerce Blocks checkout? =

Yes — the Cart and Checkout blocks are supported, alongside the classic shortcode checkout.

= Does this work with WooCommerce Subscriptions? =

Yes. Sign-up (including free trials with nothing due today), automatic renewals, retries and changing the payment method (by the customer or the store) are supported. Renewals can be paid with cards, wallets and the reusable local methods (SEPA Direct Debit, US bank accounts, Bacs, Link).

= What happens when a customer's bank asks for 3D Secure on a renewal? =

The renewal can't be confirmed while the customer is away, so it fails and the customer gets a "Confirm your payment" e-mail with a link to the renewal's payment page, where they confirm it with their bank (or pay with another card, which the subscription then keeps). You can edit or switch off that e-mail under WooCommerce > Settings > Emails.

= Can another subscription plugin use this gateway for renewals? =

Yes. A plugin that creates its own renewal orders can fire `woocommerce_scheduled_subscription_payment_sutrapay_stripe_card` (the same action WooCommerce Subscriptions uses) with the renewal order, or call the gateway's `process_payment()` from a scheduled task: the order's saved Stripe payment method is charged off-session. The outcome is reported with the `sutrapay_stripe_renewal_payment_result` action; `sutrapay_stripe_renewal_requires_authentication` and `sutrapay_stripe_renewal_paid_by_customer` report the 3D Secure recovery.

= Where do I manage the gateway settings? =

The gateways appear under WooCommerce > Settings > Payments like any other gateway; their configuration — API keys, capture method, appearance, express buttons — lives in WooCommerce > SutraPay for Stripe.

== External Services ==

This plugin connects to Stripe, which is required for it to work. No data is sent until Stripe keys are entered and a customer starts a payment (or an administrator uses the connection test, webhook, refund, dispute or payout tools).

1. Stripe API
* Service URL: https://api.stripe.com
* Purpose: creating and confirming payments (Payment Intents, Setup Intents, Confirmation Tokens), saving payment methods for logged-in customers, refunds and manual captures, disputes and evidence, payouts and balance transactions, creating the webhook endpoint, registering the store's domain for Apple Pay / Google Pay (Payment Method Domains), and the optional Stripe customer portal.
* Data sent: your secret API key (for authentication), the order amount, currency, order number and itemized description, the customer's billing and shipping name, address, e-mail address and phone number, the Stripe customer / payment-method identifiers, and dispute evidence you submit.
* When: when a customer pays or saves a payment method, when an administrator opens the Dashboard, Disputes, Payouts or Webhooks screens or refunds/captures an order, and when a webhook is received.

2. Stripe.js, the Payment Element and the Express Checkout Element
* Service URL: https://js.stripe.com/endive/stripe.js (Stripe.js, on the same Stripe release as the plugin's API version; loaded on the checkout, order "Pay", cart, product and Add-payment-method pages while the gateway is enabled)
* Purpose: renders the secure payment fields and the express checkout buttons, and completes 3D Secure or bank confirmation steps. Payment details are entered into fields hosted by Stripe and never reach your server.
* Data sent: the visitor's IP address, browser information and cookies are sent to Stripe by Stripe.js, as described in Stripe's privacy policy; the amount and currency of the order, and the billing details typed at checkout when a payment is submitted.

3. Webhooks (incoming)
* Stripe sends event notifications to the webhook URL shown in the plugin settings; each request's signature is verified with your webhook signing secret before it is processed.

Terms of Service: https://stripe.com/legal/ssa
Privacy Policy: https://stripe.com/privacy

== Changelog ==

= 0.13.0 =
* Changed: every internal name (code, settings, gateway id, webhook address, styles, scripts) is now sutrapay_stripe; earlier builds used fsp.

= 0.12.0 =
* Changed: the plugin is now called SutraPay for Stripe and lives in the sutrapay-for-stripe folder. Settings, webhooks and saved payment methods are kept; a copy in the previous folder (flex-stripe-payments) is switched off and can be removed with one button.
* Changed: updates come through WordPress's Updates screen when MemberSutra (website download) or MemberSutra Pro for WooCommerce is active.

= 0.11.4 =
* Changed: renamed to Flex Stripe Payments (formerly MemberSutra). The plugin now lives in the flex-stripe-payments folder (text domain flex-stripe-payments). Installing this version next to the old flexwoo-stripe-payments copy switches the old copy off and keeps all settings and data; a notice then offers to remove the old copy safely.

= 0.11.3 =
* Fixed: the daily cleanup job is scheduled on init, so activating the plugin no longer causes "translation loading ... triggered too early" notices.

= 0.11.2 =
* Changed: the plugin's home page and author links point to https://sutraplugins.com.
* Changed: translations load through WordPress.org language packs (no load_plugin_textdomain()).
* Security: the accepted card brands and the rate limiter's IP address are sanitized before use.

= 0.11.1 =
* Changed: the admin menu and main page are named "SutraPay for Stripe" (was "Stripe Payments by MemberSutra"), matching the plugin name; the readme's setup steps say so too.
* Maintenance: production-readiness review with MemberSutra 1.42.0 (security review, Plugin Check clean, full regression). No functional changes.

= 0.11.0 =
* Changed: the plugin is now named SutraPay for Stripe (author MemberSutra), like the other MemberSutra plugins. The folder, slug and text domain stay sutrapay-stripe-payments, so updating replaces the installed copy and settings are kept.
* Maintenance release: production-readiness review with MemberSutra 1.41.0 (Plugin Check clean, full regression including live Stripe test-mode subscriptions). Its scheduled cleanup job is listed under MemberSutra > Tools > Cron Jobs. No functional changes.

= 0.10.0 =
* Added: subscription plugins can run subscriptions in Stripe Billing through new filters (sutrapay_stripe_billing_subscription_create, _adjust, _cancel, _reactivate, _pause, _unpause, _set_payment_method, _get, _invoices and sutrapay_stripe_billing_invoice_paid_out_of_band). These create a subscription for a saved card that starts billing at the next renewal, adjust a renewal invoice to the plugin's own total, and keep the subscription in step with the plugin. Each subscription is listed in the Stripe Dashboard's Subscriptions tab.
* Added: the webhook endpoint also listens for invoice.created, when a renewal invoice can still be adjusted. The Webhooks screen and the setup checklist show when the endpoint needs "Create / Sync webhook" to add new events; the endpoint and its signing secret stay the same.
* Added: sutrapay_stripe_billing_invoice_collect finalizes and charges a renewal invoice still in draft. Stripe keeps a draft until every endpoint listening for invoice.created has answered, which can take up to 72 hours when the site cannot be reached.
* Fixed: an invoice marked paid outside Stripe is recognised under the current Stripe API version (invoice payments) as well as earlier ones.

= 0.9.0 =
* Changed: the plugin now uses Stripe's current release (Endive). Every server request is pinned to API version 2026-09-30.endive (was 2026-02-25.clover), and the bundled Stripe PHP library is version 22.0.0 (was 19.4.1, a major version Stripe no longer updates).
* Changed: Stripe.js is loaded from https://js.stripe.com/endive/stripe.js, the versioned script for the same release, as Stripe recommends. Before, js.stripe.com/v3 was used, which has no fixed API version (its requests used the Stripe account's default version).
* Fixed: the Payment Element's radio-button option used a true/false value that newer Stripe.js versions refuse, which would stop the card form from appearing.
* Fixed: a "Save payment method" tick (or a shipping change in Apple Pay / Google Pay) made just before paying is now always applied before the payment is sent.
* Improved: network errors are retried safely. Each request is sent with an idempotency key, so a retry can never charge, refund or create a customer twice, and refunds have their own key.
* After updating: open Webhooks and use "Re-create endpoint". Stripe does not allow changing an existing endpoint's API version, and the setup checklist shows this step until it is done.

= 0.8.1 =
* Fixed: with WooCommerce Subscriptions active, a payment could stop with a fatal error while its description was built (a WooCommerce Subscriptions method that does not exist was called).
* Removed: checks for a WooCommerce Subscriptions function that does not exist.

= 0.8.0 =
* New: renewals charged while the customer is away work for any subscription engine, not only WooCommerce Subscriptions: the renewal action and the gateway's process_payment() from a scheduled task charge the order's saved method off-session (this also fixes renewals of MemberSutra Pro for WooCommerce's token billing, which failed with "Please enter your payment details").
* New: when the bank asks for 3D Secure on a renewal, the customer is e-mailed a "Confirm your payment" link to the renewal's payment page (a WooCommerce e-mail you can edit or switch off). Before, the renewal just failed.
* New: paying a failed renewal with another payment method moves the subscription to it; deleting a saved method (in My Account, or in Stripe) moves its subscriptions to the customer's default method.
* New: saved payment methods remember whether they were added in test or live mode; methods of the other mode are hidden and never charged.
* Fixed: a SEPA Direct Debit / ACH renewal that failed days later was not counted as a failed attempt, so the retry was answered with the old "processing" result instead of a new charge.
* Fixed: renewal orders are recorded like checkout orders (charge id, Stripe customer, fees, payment method title); a renewal is only charged to a payment method of the subscriber's own Stripe customer, and only with that method's own type.
* Fixed: a $0 renewal (for example a 100% coupon cycle) is completed without a Stripe payment; a renewal below Stripe's minimum amount fails with a clear note. The Stripe decline code of a failed renewal is kept on the order.

= 0.7.0 =
* New: Stripe's Payment Element replaces the card field. Checkout offers every payment method enabled in your Stripe Dashboard (Link, SEPA Direct Debit, iDEAL, Bancontact, Klarna, Afterpay, US bank accounts and more), in the classic checkout, the Checkout block, the order "Pay" page and My Account > Add payment method.
* New: payments are created and confirmed on the server after WooCommerce accepts the order, for exactly the order total. A checkout WooCommerce refuses never charges the customer (this replaces the refund-on-retry safeguard of 0.6.0).
* New: 3D Secure and bank redirects return to a page that checks the payment with Stripe before the order is marked paid.
* New: methods that settle later (SEPA Direct Debit, ACH, Bacs) put the order On hold until Stripe confirms or fails the payment.
* New: Stripe's Express Checkout Element replaces the deprecated Payment Request Button: Apple Pay, Google Pay and Link (plus PayPal / Amazon Pay when enabled in Stripe) above the checkout form, on the cart, on product pages and in the Cart / Checkout blocks.
* New: saved SEPA Direct Debit, bank account and Link payment methods (iDEAL / Bancontact / Sofort payments save the SEPA mandate they create) for later purchases and subscription renewals.
* New: webhook handling for processing, authorized, 3D Secure-pending, Setup Intent, card auto-update and Stripe Radar review events. The webhook endpoint is created on the plugin's Stripe API version; a "Re-create endpoint" button upgrades an existing one.
* New: a setup checklist on the main page and a "Payment methods at checkout" panel linking to the Stripe Dashboard.
* WooCommerce Subscriptions: subscriptions bought with Apple Pay / Google Pay now renew automatically; a retried renewal is really charged again (it was answered with the first failure for 24 hours); delayed-settlement renewals wait On hold; the admin payment token field on the subscription is read and validated; customers and admins can change the payment method; the Checkout block offers the gateway for subscription carts.
* Fixed: the product page "Buy now" button sent the selected variation incorrectly. It is hidden for guests when the store requires an account.
* Removed: the sutrapay_stripe_sync_intent, sutrapay_stripe_sync_wallet_billing and sutrapay_stripe_express_prepare AJAX endpoints (payments are no longer started in the browser); sutrapay_stripe_express_state replaces them for the express buttons.

= 0.6.0 =
* Fixed: My Account > Payment methods crashed (PHP error) for any customer with a saved payment method; the card label ("Add label" / "Rename") now works there.
* Fixed: a filled-in "Statement descriptor" made Stripe refuse every card payment. The text is now sent as Stripe's statement descriptor suffix, and both descriptor fields are validated on save.
* Fixed: a card could be charged twice when WooCommerce refused the first checkout attempt (for example a missing field). A retry now reuses the payment already made; if the cart changed in between, the earlier payment is refunded automatically.
* Fixed: Google Pay / Apple Pay from the cart, product page and Cart / Checkout blocks charged the total before shipping and tax, so the order was then refused. The final total is now calculated from the wallet's address before the card is charged, and a changed total is shown to the shopper instead of charged.
* Security: the "Buy now" wallet button now runs WooCommerce's add-to-cart validation (members-only products, purchase limits) and the express checkout runs the store's checkout rules and registration requirement.
* Security: the wallet billing step only accepts the shopper's own PaymentIntent.
* Security: changing a WooCommerce Subscriptions card is limited to the subscription's own customer; the customer portal respects its on/off setting.
* Fixed: refunds made in the Stripe Dashboard are now recorded on the WooCommerce order (a full refund sets it to Refunded, which ends access granted by the order).
* Fixed: refunding an authorized but not captured order releases the authorization instead of failing.
* Fixed: uploaded dispute evidence files were never attached to the dispute.
* Fixed: the Checkout block preselected a saved card by the wrong id, so paying with it failed.
* Fixed: the privacy exporter and eraser missed the Stripe Customer IDs (wrong meta key) and cards saved through Google Pay / Apple Pay.
* Fixed: the "payment failed" e-mail for Stripe invoices is no longer sent twice for MemberSutra subscriptions, for a subscription's first invoice, or for invoices of other sites; the customer's e-mail address is no longer written to the log.
* Fixed: payment details required by this plugin at checkout now follow the store's own checkout fields (stores without address fields could not take card payments).
* Changed: Apple Pay domain registration uses Stripe's Payment Method Domains API and is tracked per mode and domain.
* Changed: the Support page links to the plugin website and copies diagnostic details instead of a ticket form that sent nothing; Documentation links to the plugin website.
* Changed: the Dashboard's 30-day volume counts paid orders only, net of refunds.
* Accessibility and translation: toggles are named switches, labels are tied to their fields, and every checkout and admin script text is translatable (languages/sutrapay-stripe-payments.pot).
* Uninstall also removes this plugin's transients, scheduled event and, on multisite, every site's data. `WC tested up to` 11.1.2.

= 0.5.11 =
* Security: the "Manage payment methods" redirect only follows an https URL on a stripe.com host.
* Verified against Stripe test mode: test-card payment, refund and webhook signature checks.
* Fixed: the card field never mounted on the classic checkout ("Can only create one Element of type card"); the previous Element is now destroyed before a new one is created.
* Fixed: switching to Live mode with empty live keys, a key in the wrong slot, an invalid colour/radius/font size, or unchecking every card brand was accepted and reported as "Settings saved."; the form is now validated and refused with a message.
* Fixed: the Logs screen used WooCommerce log helpers deprecated since 8.6.
* Added: "External services" disclosure in readme.txt. `WC tested up to` 11.1.1.

= 0.5.10 =
* Maintenance and stability release: verified card tokenization, webhook signature validation, and compatibility with MemberSutra 1.35.2.

= 0.5.9 =
* Maintenance and stability release: comprehensive payment processing, webhooks, and refund lifecycle verification.

= 0.5.5 =
* Maintenance update and compatibility verification for WooCommerce 9.0+ and WordPress 6.7+.

= 0.5.4 =
* Renamed the plugin to MemberSutra Stripe Payments for WooCommerce (display name only — the slug/text-domain remains sutrapay-stripe-payments).

= 0.5.3 =
* Renamed the plugin to MemberSutra Stripe Payments for WooCommerce (slug/text-domain: sutrapay-stripe-payments), including the plugin folder, main file, admin menu slugs, and all translation strings.

= 0.5.2 =
* Security hardening pass: Stripe secret keys and the webhook signing secret are now masked in the admin UI (only the last 4 characters are ever rendered into page HTML) instead of the raw value; saving settings without touching a masked field leaves the stored secret unchanged.
* Log entries are now scanned and redacted for anything that looks like a Stripe API key, webhook secret, or card-like number before being written to the log file.
* Added a database-backed webhook idempotency ledger (new table, unique-constrained on the Stripe event id) so a retried or replayed webhook delivery is now a guaranteed no-op instead of relying solely on each individual handler being independently idempotent.
* Webhook requests now have a bounded maximum body size.
* Added per-IP rate limiting to the public (logged-out) AJAX endpoints used during checkout (intent sync, wallet billing sync, shipping rate lookups, express checkout) to bound abuse/cost exposure from scripted traffic.
* Dispute evidence file uploads now verify the file was a genuine PHP upload, sniff the actual file content type rather than trusting the filename/browser-supplied type, and validate image structure for JPG/PNG evidence.
* Added uninstall.php so deleting the plugin (not just deactivating it) cleanly removes only this plugin's own options and its new event-ledger table.

= 0.5.1 =
* Reviewed against an external static-analysis security audit (8 findings, all across nonce verification, input sanitization, and output escaping). Manual review confirmed 7 of 8 were false positives from pattern-matching that couldn't see nonce checks implemented via a shared helper method rather than inline; one genuine hardening opportunity was found and fixed (an early $_POST read with no local nonce check, previously safe only by relying on a caller's guard rather than checking directly). Verified tested up to WordPress 7.0.2 and PHP 8.5, including a check for PHP 8.5's newly deprecated non-canonical casts and PHP 8.1+'s null-to-internal-function deprecations (added defensive null-coalescing on several Stripe API object properties as a precaution, even though those fields are required by Stripe's API schema).

= 0.5.0 =
* Subscription payment method change is now supported — detected via WooCommerce Subscriptions' own request flag (with the change_payment_method query var as a backup signal), reusing the existing SetupIntent verification flow. A defensive fallback submit-handler was added on the #order_review form in case the checkout_place_order event doesn't fire identically there.
* Fixed a real bug: a subscription with a free trial and no sign-up fee (i.e. $0 due today) would previously fail to check out at all, since Stripe PaymentIntents require a positive amount. This now falls back to a SetupIntent (verifies and saves the card with no charge), scoped specifically to subscription carts.
* Dispute evidence now supports file uploads (receipts, delivery confirmations, customer communication — PDF/JPG/PNG, 5MB max) via Stripe's File Upload API, alongside the existing text evidence fields.
* Payouts now have a "View orders" reconciliation view, listing the specific orders bundled into a given payout by matching each of the payout's balance transactions back to its charge.
* Dashboard now shows subscription summary cards (active count, count needing attention, next renewal date) when WooCommerce Subscriptions is active, and the order screen shows which saved card is on file for a subscription.

= 0.4.0 =
* WooCommerce Subscriptions support (only active if that plugin is installed): subscription sign-up reuses the existing card checkout flow, cards are always saved automatically for subscription purchases, and scheduled renewals are charged off-session against the saved card. Cancellation, suspension, reactivation, and amount/date changes are handled entirely by WooCommerce Subscriptions' own scheduling — no separate Stripe-side subscription object is created.
* Not included in this pass: changing a subscription's payment method from the customer's account. That flow depends on WooCommerce Subscriptions' own page markup, which wasn't something that could be verified without a live install of that plugin.
* Every saved card is now associated with the specific order it was saved on (via WooCommerce's own payment-token/order association), not just the customer's account — this is what lets subscription renewals find the right card.

= 0.3.0 =
* New Disputes screen: every dispute on the account, fetched live from Stripe, correlated to its WooCommerce order, with an inline text-evidence submission form and an "Accept dispute" action. File evidence (receipts, delivery confirmations) isn't supported yet — add those directly in the Stripe Dashboard alongside what's submitted here.
* New Payouts screen: the account's actual bank payouts with arrival dates, fetched live from Stripe.
* Every order now records the Stripe fee (commission), net amount, and the date those funds become available — shown on the order edit screen, the Dashboard's recent transactions table, and used for the new Dashboard summary cards (open dispute count, next payout date).
* Webhook handling extended to cover the full dispute lifecycle (created/updated/closed/funds withdrawn/funds reinstated). If you already had a webhook configured before this update, re-run "Create webhook automatically" in Webhooks (or add the new event types manually in your Stripe Dashboard) so these new events actually get sent to your site.

= 0.2.0 =
* Google Pay / Apple Pay now works as a true one-click purchase on the Cart block, Checkout block's express-payment area, and product pages — including full wallet-driven shipping address and rate selection for physical goods, with no separate checkout page visited. Registered via WooCommerce Blocks' Express Payment Method API rather than the regular payment method list.
* New shared shipping-rate calculation service, built on WooCommerce's own shipping zone/package logic so third-party shipping plugins continue to work.
* This is a substantial new code path (wallet-driven shipping selection, direct order creation outside the normal checkout form). Please test thoroughly — a physical-goods purchase via Google Pay/Apple Pay from the Cart block and from a product page, in particular — before relying on it in production.

= 0.1.2 =
* Added pre-charge validation of checkout details: required fields, email format, and terms-and-conditions acceptance are now checked before a card is charged (not just before the order is marked paid), for both the card form and the Google Pay/Apple Pay button. A server-side check also runs immediately before any order is finalized as a backstop.

= 0.1.1 =
* Security fix: a successful PaymentIntent could previously be replayed against a second, different order with a matching total and get it marked as paid without a second charge. Orders are now checked against any other order already claiming the same PaymentIntent before being finalized.
* Compatibility metadata updated for current WordPress (tested up to 7.0).

= 0.1.0 =
* Initial release: card payments (Payment Intents, 3DS2, saved cards, refunds, manual capture), Google Pay/Apple Pay via Payment Request Button, webhooks, and the Dashboard/Settings/Payment Methods/Webhooks/Logs admin app.

== Upgrade Notice ==

= 0.13.0 =
First build under the SutraPay code names. Not an update from older builds: settings, orders and webhooks made with an earlier version are not carried over. Install on a new site (or start fresh) and connect the payment provider again.

= 0.12.0 =
Renamed to SutraPay for Stripe (new folder; settings are kept). No functional change.

= 0.11.4 =
Renamed to Flex Stripe Payments in a new folder (flex-stripe-payments). Settings and data are kept; remove the old copy with the button in the notice.

= 0.11.3 =
Schedules its daily cleanup on init. No functional changes.

= 0.11.2 =
WordPress.org review hardening. No functional changes.

= 0.11.1 =
Menu renamed to Flex Stripe Payments. No functional changes.

= 0.11.0 =
Maintenance release, no functional changes. If you are updating from 0.9.x, read the 0.10.0 notice: sync the webhook after updating.

= 0.10.0 =
Adds Stripe Billing subscriptions for subscription plugins. After updating, open Webhooks and click "Create / Sync webhook" to add the invoice.created event. No database changes.

= 0.9.0 =
Moves to Stripe's current release (API 2026-09-30.endive, Stripe PHP library 22.0.0, versioned Stripe.js). After updating, open Webhooks and use Re-create endpoint. No database changes.

= 0.8.1 =
Fixes a fatal error on payments while WooCommerce Subscriptions is active. No database changes.

= 0.8.0 =
Subscription renewals: 3D Secure recovery e-mail, correct retries of late SEPA failures, and renewals for subscription plugins other than WooCommerce Subscriptions. No database changes.

= 0.7.0 =
Payments are now charged on the server after WooCommerce accepts the order, and checkout offers every payment method enabled in your Stripe Dashboard. Open Webhooks and use Re-create endpoint if it is shown.

= 0.6.0 =
Fixes a My Account crash, blocked checkouts with a statement descriptor, double charges on retried checkouts and wallet totals. No database changes.
