• I’ve been with Stripe support about the pre-auth issue, below is their reply: (I gave an example in test mode where there is a uncaptured transaction of £150)

    Support:
    I’m comparing the two transactions and I found out that the capture_method on the test mode is manual while on the live mode it’s automatic

    If you check here https://dashboard.stripe.com/payments/pi_3QwWr8RsC06agrkg09ZsTF5L and you scroll down to the all activity,

    Click on where it says “A new payment pi_3QuBQPRsC06agrkg1htsSPzN for £150.00 was created” you will see on the event data that the “capture_method”: “manual” is on the test mode.

    But here on the live mode https://dashboard.stripe.com/payments/pi_3QwWr8RsC06agrkg09ZsTF5L. If you click this “A new payment pi_3QwWr8RsC06agrkg09ZsTF5L for £107.50 was created” you will see that the “capture_method”: “automatic_async” is the one used.

    Me:
    Can I just implement what you mentioned above?

    Support:
    you can easily do that if you’re creating the charge using the Stripe API, that’s why I was asking earlier how was the charge created. But since this was created through WooCommerce, they actually have their own set of API codes on their end and also some that they use to integrate with Stripe’s codes.

    And that one we cannot just edit or at least not that I know of since I’m not an expert with the process that WooCommerce have for their codes.

    Me:
    So I will check with woo-commerce regarding the settings?

    Support:
    Yes and if they determine that it still needs Stripe intervention, you can have them contact us directly and provide the Case ID 20442591 for this conversation for reference, provide your account id(acct_1Qb96CRsC06agrkg) as well and we will work with them to solve your concern.

    • This topic was modified 3 days, 9 hours ago by humnanaeem.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Moses M. (woo-hc)

    (@mosesmedh)

    Hi @humnanaeem,

    Thank you for the detailed explanation. It seems the support rep assumed you were using Stripe Payment Gateway for WooCommerce.

    To clarify, WooCommerce doesn’t process transactions directly. Payments are handled by a payment processing plugin based on the method you use. For Stripe, there are multiple plugins available. To better understand your setup, please share your System Status Report from WooCommerce > Status > Get Report > Copy for Support.

    This appears to be more of a feature request than an issue. Once you provide the SSR, I’ll review your setup and direct you to the appropriate channel.

    Thread Starter humnanaeem

    (@humnanaeem)

    <br>### WordPress Environment ###<br><br>WordPress address (URL): https://welwynprestigehire.com<br>Site address (URL): https://welwynprestigehire.com<br>WC Version: 9.6.2<br>Legacy REST API Package Version: The Legacy REST API plugin is not installed on this site.<br>Action Scheduler Version: ? 3.9.0<br>Log Directory Writable: ?<br>WP Version: 6.7.2<br>WP Multisite: –<br>WP Memory Limit: 512 MB<br>WP Debug Mode: –<br>WP Cron: ?<br>Language: en_US<br>External object cache: ?<br><br>### Server Environment ###<br><br>Server Info: Apache<br>PHP Version: 8.2.27<br>PHP Post Max Size: 100 MB<br>PHP Time Limit: 3600<br>PHP Max Input Vars: 10000<br>cURL Version: 7.81.0<br>OpenSSL/3.0.2<br><br>SUHOSIN Installed: –<br>MySQL Version: 8.0.40-31<br>Max Upload Size: 50 MB<br>Default Timezone is UTC: ?<br>fsockopen/cURL: ?<br>SoapClient: ?<br>DOMDocument: ?<br>GZip: ?<br>Multibyte String: ?<br>Remote Post: ?<br>Remote Get: ?<br><br>### Database ###<br><br>WC Database Version: 9.6.2<br>WC Database Prefix: wp_<br>Total Database Size: 14.19MB<br>Database Data Size: 8.54MB<br>Database Index Size: 5.65MB<br>wp_woocommerce_sessions: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_woocommerce_order_items: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_woocommerce_order_itemmeta: Data: 0.11MB + Index: 0.14MB + Engine InnoDB<br>wp_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_actionscheduler_actions: Data: 0.13MB + Index: 0.14MB + Engine InnoDB<br>wp_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_actionscheduler_logs: Data: 0.06MB + Index: 0.03MB + Engine InnoDB<br>wp_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_comments: Data: 0.06MB + Index: 0.09MB + Engine InnoDB<br>wp_e_events: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_e_notes: Data: 0.02MB + Index: 0.17MB + Engine InnoDB<br>wp_e_notes_users_relations: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>wp_e_submissions: Data: 0.02MB + Index: 0.27MB + Engine InnoDB<br>wp_e_submissions_actions_log: Data: 0.02MB + Index: 0.11MB + Engine InnoDB<br>wp_e_submissions_values: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_jetpack_sync_queue: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_options: Data: 2.42MB + Index: 0.06MB + Engine InnoDB<br>wp_postmeta: Data: 4.19MB + Index: 2.97MB + Engine InnoDB<br>wp_posts: Data: 0.36MB + Index: 0.09MB + Engine InnoDB<br>wp_term_relationships: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_term_taxonomy: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_termmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_terms: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_usermeta: Data: 0.06MB + Index: 0.06MB + Engine InnoDB<br>wp_users: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>wp_wc_admin_note_actions: Data: 0.06MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_admin_notes: Data: 0.06MB + Index: 0.00MB + Engine InnoDB<br>wp_wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_wc_customer_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_download_log: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_order_addresses: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_wc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_order_operational_data: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_order_product_lookup: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_wc_order_stats: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>wp_wc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_orders: Data: 0.05MB + Index: 0.11MB + Engine InnoDB<br>wp_wc_orders_meta: Data: 0.06MB + Index: 0.11MB + Engine InnoDB<br>wp_wc_product_attributes_lookup: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_product_download_directories: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_product_meta_lookup: Data: 0.02MB + Index: 0.11MB + Engine InnoDB<br>wp_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wpfm_backup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br><br>### Post Type Counts ###<br><br>attachment: 85<br>chbs_booking: 97<br>chbs_booking_extra: 8<br>chbs_booking_form: 8<br>chbs_coupon: 1<br>chbs_driver: 2<br>chbs_email_account: 1<br>chbs_geofence: 19<br>chbs_location: 7<br>chbs_price_rule: 19<br>chbs_route: 6<br>chbs_tax_rate: 5<br>chbs_vehicle: 5<br>chbs_vehicle_attr: 8<br>custom_css: 2<br>customize_changeset: 24<br>elementor_library: 13<br>elementor_snippet: 3<br>envato_tk_import: 1<br>nav_menu_item: 12<br>page: 24<br>post: 5<br>revision: 2<br>shop_order_placehold: 76<br>wp_font_face: 36<br>wp_font_family: 12<br>wp_global_styles: 1<br>wp_navigation: 1<br><br>### Security ###<br><br>Secure connection (HTTPS): ?<br>Hide errors from visitors: ?<br><br>### Active Plugins (15) ###<br><br>Chauffeur Taxi Booking System for WordPress: by QuanticaLabs – 8.2<br>Duplicate Page: by mndpsingh287 – 4.5.4<br>Elementor Pro: by Elementor.com – 3.27.4<br>Elementor: by Elementor.com – 3.27.6<br>Envato Elements: by Envato – 2.0.16<br>Genesis Blocks: by StudioPress – 3.1.6<br>Jeg Elementor Kit: by Jegtheme – 2.6.11<br>Make Column Clickable Elementor: by Fernando Acosta – 1.4.0<br>MetForm: by Wpmet – 3.9.4<br>Temporary Login Without Password: by StoreApps – 1.8.5<br>Trustpilot-reviews: by Trustpilot – 2.5.925<br>WooCommerce Stripe Gateway: by Stripe – 9.2.0<br>WooPayments: by WooCommerce – 9.0.0<br>WooCommerce: by Automattic – 9.6.2 (update to version 9.7.0 is available)<br>WP File Manager: by mndpsingh287 – 8.0.1<br><br>### Inactive Plugins (6) ###<br><br>Akismet Anti-spam: Spam Protection: by Automattic - Anti-spam Team – 5.3.7<br>Force Strong Passwords - WPE Edition: by Jason Cosper – 1.8.0<br>WP Engine Cache Plugin: by WP Engine – 1.3.3<br>WP Engine Seamless Login Plugin: by WP Engine – 1.6.1<br>WP Engine Security Auditor: by wpengine – 1.1.1<br>WP Engine System: by WP Engine – 6.4.1<br><br>### Dropin Plugins () ###<br><br>advanced-cache.php: advanced-cache.php<br>object-cache.php: Memcached<br><br>### Must Use Plugins (5) ###<br><br>Force Strong Passwords - WPE Edition: by Jason Cosper – 1.8.0<br>WP Engine Cache Plugin: by WP Engine – 1.3.3<br>WP Engine Seamless Login Plugin: by WP Engine – 1.6.1<br>WP Engine Security Auditor: by wpengine – 1.1.1<br>WP Engine System: by WP Engine – 6.4.1<br><br>### Settings ###<br><br>Legacy API Enabled: –<br>Force SSL: –<br>Currency: GBP (£)<br>Currency Position: left<br>Thousand Separator: ,<br>Decimal Separator: .<br>Number of Decimals: 2<br>Taxonomies: Product Types: external (external)<br>grouped (grouped)<br>simple (simple)<br>variable (variable)<br><br>Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)<br>exclude-from-search (exclude-from-search)<br>featured (featured)<br>outofstock (outofstock)<br>rated-1 (rated-1)<br>rated-2 (rated-2)<br>rated-3 (rated-3)<br>rated-4 (rated-4)<br>rated-5 (rated-5)<br><br>Connected to WooCommerce.com: –<br>Enforce Approved Product Download Directories: ?<br>HPOS feature enabled: ?<br>Order datastore: Automattic\WooCommerce\Internal\DataStores\Orders\OrdersTableDataStore<br>HPOS data sync enabled: –<br><br>### Logging ###<br><br>Enabled: ?<br>Handler: Automattic\WooCommerce\Internal\Admin\Logging\LogHandlerFileV2<br>Retention period: 30 days<br>Level threshold: –<br>Log directory size: 2 MB<br><br>### WC Pages ###<br><br>Shop base: #23683 - /shop/<br>Cart: ? Page contains both the [woocommerce_cart] shortcode and the woocommerce/cart block.<br>Checkout: #23685 - /checkout/ -  Contains the woocommerce/checkout block<br>My account: #23686 - /my-account/<br>Terms and conditions: ? Page not set<br><br>### Theme ###<br><br>Name: Hello Elementor<br>Version: 3.3.0<br>Author URL: https://elementor.com/?utm_source=wp-themes&utm_campaign=author-uri&utm_medium=wp-dash<br>Child Theme: ? – If you are modifying WooCommerce on a parent theme that you did not build personally we recommend using a child theme. See: How to create a child theme<br>Theme type: Classic theme<br>WooCommerce Support: ?<br><br>### Templates ###<br><br>Overrides: –<br><br>### WooPayments ###<br><br>Version: 9.0.0<br>Connected to WPCOM: Yes<br>WPCOM Blog ID: 240302001<br>Account ID: ? Not connected<br>Logging: Enabled<br><br>### Admin ###<br><br>Enabled Features: activity-panels<br>analytics<br>product-block-editor<br>coupons<br>core-profiler<br>customize-store<br>customer-effort-score-tracks<br>import-products-task<br>experimental-fashion-sample-products<br>shipping-smart-defaults<br>shipping-setting-tour<br>homescreen<br>marketing<br>mobile-app-banner<br>onboarding<br>onboarding-tasks<br>pattern-toolkit-full-composability<br>product-custom-fields<br>remote-inbox-notifications<br>remote-free-extensions<br>payment-gateway-suggestions<br>printful<br>shipping-label-banner<br>subscriptions<br>store-alerts<br>transient-notices<br>woo-mobile-welcome<br>wc-pay-promotion<br>wc-pay-welcome-page<br>launch-your-store<br><br>Disabled Features: product-data-views<br>experimental-blocks<br>coming-soon-newsletter-template<br>minified-js<br>product-pre-publish-modal<br>settings<br>async-product-editor-category-field<br>product-editor-template-system<br>blueprint<br>reactify-classic-payments-settings<br>use-wp-horizon<br>add-to-cart-with-options-stepper-layout<br>blockified-add-to-cart<br><br>Daily Cron: ? Next scheduled: 2025-02-27 13:49:58 +00:00<br>Options: ?<br>Notes: 74<br>Onboarding: skipped<br><br>### Action Scheduler ###<br><br>Complete: 305<br>Oldest: 2025-01-29 08:23:45 +0000<br>Newest: 2025-02-27 04:55:59 +0000<br><br>Failed: 1<br>Oldest: 2025-02-21 11:22:52 +0000<br>Newest: 2025-02-21 11:22:52 +0000<br><br>Pending: 2<br>Oldest: 2025-02-27 08:19:39 +0000<br>Newest: 2025-02-27 10:34:11 +0000<br><br><br>### Status report information ###<br><br>Generated at: 2025-02-27 08:17:47 +00:00<br>
    Plugin Support Jonayed (woo-hc)

    (@jonayedhosen)

    Hi @humnanaeem ,

    I understand you’re seeing differences between test and live transactions in your WooCommerce Stripe integration, specifically with the capture_method setting.

    Here’s a quick breakdown of how capture_method works:

    • Automatic Capture: Charges are captured immediately upon authorization.
    • Manual Capture: Charges are authorized but require manual capture within a set timeframe (typically seven days) before the authorization expires.

    It looks like in test mode, capture_method is set to manual, while in live mode, it’s automatic_async. To ensure Automatic Capture is enabled for both, head over to:

    WooCommerce > Settings > Payments > Stripe

    Then, check the “Issue an authorization on checkout, and capture later” setting. If this is checked, it means payments require manual capture. Unchecking it will ensure payments are captured automatically.

    I hope this helps!

    Thread Starter humnanaeem

    (@humnanaeem)

    It is already checked since the start

    Plugin Support Jonayed (woo-hc)

    (@jonayedhosen)

    Hi @humnanaeem ,

    Thanks for checking the Issue an authorization on checkout, and capture later setting. By default, this option is usually unchecked for automatic capture. If it was enabled after switching to test mode, that might be affecting the behavior.

    Could you try unchecking the option again and testing the checkout process in both live and test modes to see if the issue persists?

    Additionally, I noticed from your system status report that you have both WooCommerce Stripe Gateway (v9.2.0) and WooPayments (v9.0.0) installed. Could you clarify whether the logs are being generated by one of these plugins or both? Also, which one is currently active for processing payments?

    Let us know what you find, and we’ll be happy to assist further!

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.