drackmord_unexpected | Stripe Developers | Page 1

shrewd mistBOT Jul 1, 2025, 12:48 PM

#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1389588556116262944

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

nova anvil Jul 1, 2025, 12:51 PM

#

Hi there 👋 I'm not familiar with what iDeal changes you're referring to offhand, could you elaborate a bit?

brave pivot Jul 1, 2025, 12:53 PM

#

Hi there! We got an official communication from Stripe that the implementation for iDeal was changing starting 30th of May because iDeal brought the bank selection a step forward, in their own web hub that is displayed in the final steps of the payment, so old implementations with Stripe needed not to implement that step natively like previously required and instead just pass an empty string as bank name in the api.

Moreover, it was stated that using any stripe-provided UI like Stripe Elements on web or PaymentSheet on Android would require no change on our part since that would be already managed.

And yeah we noticed that the web version correctly updated to avoid the bank selection step, while Android didn't

#

I've been going back and forth with Stripe support via email for over a month but I don't see it getting anywhere, then I remembered about this discord server 😄

#

This is our website that automatically removed the bank selection within the Stripe UI

#

And this is the PaymentSheet in Android still requesting the bank, which is also re-requested to the user in the iDeal hub an instant later

#

And this how we display the PaymentSheet in Jetpack Compose:

// In the activity onCreate
val paymentSheet = PaymentSheet(
    activity = activity,
    createIntentCallback = createIntentCallback,
    paymentResultCallback = paymentResultCallback)

// When the user clicks pay now
paymentSheet.presentWithIntentConfiguration(
    intentConfiguration =
        PaymentSheet.IntentConfiguration(
            mode =
                PaymentSheet.IntentConfiguration.Mode.Payment(
                    amount = amount.toLong(), currency = currency),
            paymentMethodTypes = listOf(PaymentMethod.Type.Ideal.code)),
    configuration =PaymentSheet.Configuration(
        merchantDisplayName = MerchantDisplayName,
        defaultBillingDetails = PaymentSheet.BillingDetails(name = userData.fullName, email = userData.email),
        shippingDetails = null,
        billingDetailsCollectionConfiguration =
            PaymentSheet.BillingDetailsCollectionConfiguration(
                name = CollectionMode.Automatic,
                phone = CollectionMode.Never,
                email = CollectionMode.Automatic,
                address = AddressCollectionMode.Never,
            ),
        appearance = PaymentSheet.Appearance(
            // Appearence config
        ),
    )
)

nova anvil Jul 1, 2025, 12:59 PM

#

I'm still trying to find details about this change. I'm not surprised that a web integration wouldn't need an update, since it'll pull our most recent version of stripe.js, but I am surprised to hear the Payment Sheet wouldn't need an update. While I suspect the shape of the integration would stay the same, I'd expect you to need to pull in a newer version of our SDK to pull in the revised UI.

brave pivot Jul 1, 2025, 1:00 PM

#

I figured as much, but we did update the library (despite Stripe support telling us it was not needed) and kept updating as new versions were released, trough June, and still nothing

#

I felt odd that Stripe contacted us in a matter of urgency specifying that if we had an old implementation, we needed to change it in order to maintain a good UX, and then being late a month in updating their own PaymentSheet implementation.

nova anvil Jul 1, 2025, 1:15 PM

#

Alright, a teammate was able to point me to this, which seems to align with what you're describing.
https://support.stripe.com/questions/make-required-changes-to-your-ideal-api-integration

From that, I'm getting the impression that mobile integrations will require updates, which aligns with my thinking of this flow.

What version of stripe-android are you using?

#

Okay, think I found the ticket for this internally, looks like we haven't implemented the UI change in the Payment Sheet yet.

brave pivot Jul 1, 2025, 1:31 PM

#

Ohhh got it, thanks!

#

So for now we'll just keep an eye on future releases and try to update as soon as the release notes mention the PaymentSheet update

#

A little bit of transparency on this would have saved us a month worth of back and forth in email, if that's some feedback you could pass on.
Thank you again!

#drackmord_unexpected