Card details not complete after dangerouslyUpdateCardDetails

[FeDev9]

Describe the bug
When attempting to create a payment method after updating card details with dangerouslyUpdateCardDetails, a StripeException is thrown with the error "Card details not complete" despite the card information being entered in the card field. This issue appeared spontaneously without updating any package versions.

To Reproduce
Steps to reproduce the behavior:

1. Enter card number "4242-4242-4242-4242" into the custom card field
2. Call await stripe.dangerouslyUpdateCardDetails(cardDetails) to save the card details
3. Attempt to create a payment method using:

return await stripe.createPaymentMethod(
  params: stp.PaymentMethodParams.card(
    paymentMethodData: stp.PaymentMethodData(
      billingDetails: stp.BillingDetails(name: cardOwner),
    ),
  ),
);

4. Observe the following exception:

StripeException(
  error: LocalizedErrorMessage(
    code: FailureCode.Failed, 
    localizedMessage: Card details not complete, 
    message: Card details not complete, 
    stripeErrorCode: null, 
    declineCode: null, 
    type: null
  )
)

Expected behavior
The payment method should be created successfully after the card details are updated via dangerouslyUpdateCardDetails, or a more specific error should indicate which card detail fields are missing/invalid (e.g., expiration date, CVV).

Smartphone / tablet

• Device: Multiple iPhones
• OS: iOS 26.2
• Package version: 12.1.1 - 12.2.0
• Flutter version 3.35.7 - 3.38.7

Additional context
This issue started occurring without any package version updates or code changes

The error occurs specifically after calling dangerouslyUpdateCardDetails but before createPaymentMethod

It's unclear if the issue is due to missing card details (expiry, CVV) or if dangerouslyUpdateCardDetails isn't properly storing the card information

The error message lacks specificity about which card detail fields are incomplete

This suggests a potential issue with Stripe's backend API changes or native SDK updates

[asadamatic]

We’re seeing the same thing: a user reported it, and we couldn’t reproduce it in test mode. It started after we upgraded to 12.2.0 and only happens on iOS.

What we found ( We found this using Cursor AI )

On iOS, when we use a custom card form (no Stripe CardField on screen) and call dangerouslyUpdateCardDetails(), then createPaymentMethod() with only billing details, we get “Card details not complete.” On Android, the same flow works.
In the iOS plugin, the internal card field is held with a weak reference. If there’s no CardField in the widget tree, that internal view isn’t retained by anything else, so it can be deallocated. By the time createPaymentMethod() runs, the plugin no longer has the card details and throws that error. So the issue is on the iOS side: the headless path doesn’t keep the card state alive.

Workaround that worked for us

We kept our custom UI and our existing dangerouslyUpdateCardDetails + createPaymentMethod calls, and only ensured a Stripe CardField exists somewhere in the tree on the screen where we add a payment method—so the plugin has something to retain. We hide it with Offstage so it doesn’t affect layout or appearance:

Offstage(  offstage: true,  child: CardField(onCardChanged: (_) {}),)

We added that as a sibling (e.g., in the same Column as our form) on the add-payment-method screen. No Stack, no visible change; it just keeps the internal card field alive on iOS, so createPaymentMethod() succeeds.
Hope that helps others and gives the maintainers a clear repro path and a temporary fix until the plugin keeps the headless card state on iOS without needing a hidden CardField.

P.S: I figured out this workaround after asking the Cursor AI to examine the plugin code.

[FeDev9]

That's great!
I tested and it works!
Thanks 🙏🏻

[asaarnak]

Thanks for a workaround.
We had the same issue on iOS.

[remonh87]

This will be fixed in the next release

[remonh87]

Fixed in v12.3.0

[asaarnak]

@remonh87
We tested adding new credit card on 12.3.0 and seems this is not fixed.
Same error and the workaround works.

[remonh87]

@asaarnak I could locally reproduce the failure and my fix fixed one of the issues. I noticed #2347 is opened that provide more context so I will use that one to debug further.

[asaarnak]

Tested that the flutter_stripe: 12.4.0 fixed this issue for us.

[CoderNamedHendrick]

Tested in flutter_stirpe: 12.5.0, the issue is back