Error: missing_required_customer_field: address->line2

  • Marco

    (@mcbus94)


    5 days, 11 hours ago

    We’re seeing this exact issue today (2026-10-02) and last days on WooCommerce Stripe Gateway v11.0.0.

    • Error: missing_required_customer_field: address->line2
    • Payment method: Apple Pay (confirmed via Stripe Dashboard logs — "tokenization_method": "apple_pay")
    • Classic checkout (not Blocks)
    • Backtrace goes through StoreApi/Routes/V1/Checkout.php, consistent with the Express Checkout (wallet) flow bypassing our normal billing form validation
    • Both $_POST and WC()->customer had complete billing data at the time of failure
    • Applied the wc_stripe_create_customer_required_fields workaround suggested in this thread (unsetting address.line2) as a temporary fix

    I was able to reproduce this myself and can confirm the bug reported by customers. Apple Pay consistently fails to populate address->line2, even though Apple Pay checkout works fine on other sites of mine — so this doesn’t seem to be a general Apple Pay limitation, but something specific to how this plugin handles it.

    Happy to share the raw woocommerce-gateway-stripe log entry (order ID, timestamps, full JSON) privately if useful for debugging.

    Further information here: https://pastebin.com/Y3Hps6aA

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Marco

    (@mcbus94)

    5 days, 11 hours ago

    I have added this code as work around:

    add_filter( 'wc_stripe_create_customer_required_fields', 'workaround_relax_stripe_customer_required_fields', 10 );
    function workaround_relax_stripe_customer_required_fields( $fields ) {
    if ( isset( $fields['address']['line2'] ) ) {
    unset( $fields['address']['line2'] );
    }
    return $fields;
    }

    Plugin Support Thu P. a11n

    (@thup90)

    13 hours, 55 minutes ago

    Hi @mcbus94,

    Thanks for sharing the workaround! I’ve replicated this bug and reported it to our devs.

    For now, you can use the workaround and keep an eye out for a release that will address this issue.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.