[Drop-in] BLIK payment: Missing loader overlay on first CTA click causes double submission in v5.8.0+

[wrozwad]

Description

After upgrading to SDK version 5.8.0, there's a regression in the Drop-in BLIK payment flow where the loader overlay doesn't appear immediately on the first CTA ("Pay"/"Zapłać") button click. This creates a poor UX where users think nothing happened and click the button again, resulting in double payment submission and "Ticket Used" errors.

Refused ER_TIC_USED The BLIK code was already used within the last 180 seconds.

Expected behavior: Loader overlay should appear immediately after clicking the pay button to prevent multiple submissions.

Actual behavior:

1. First click: No loader overlay appears, keyboard hides (since v5.9.1), SessionDropInService.onSubmit() is triggered 1st time
2. 1. Bottom sheet disappears after X seconds, then loader appears
      OR
   2. User assumes nothing happened and clicks again
   3. Second click: Loader overlay appears correctly and SessionDropInService.onSubmit() is triggered 2nd time, causing payment failures
   4. Bottom sheet disappears after X seconds, next loader appears

Steps to Reproduce

1. I am able to consistently reproduce this issue: Yes
2. Steps to reproduce the issue:
   1. Initialize Drop-in with BLIK payment method
   2. Enter BLIK code in the payment form
   3. Click the "Pay"/"Zapłać" CTA button once
   4. Observe no immediate loader overlay (keyboard hides if v5.9.1+)
   5. User clicks the button again thinking nothing happened
   6. Check logs for double onSubmit() calls
3. Screenshots or a screen recording:

App.2.20.1.Adyen.5.6.0.mp4

App.2.21.0.Adyen.5.14.0.-.single.click.mp4

[araratthehero]

Hi @wrozwad, thank you for the report.

We followed your steps but couldn't reproduce the issue on our side.
Could you please help us with the following?

• Could you try upgrading to the latest version of the SDK and try again.
• Do you have any UI customizations that might be hiding the loading screen?
• Is this problem specific to Blik, or does it affect other components too?

Let us know what you find.

[wrozwad]

Hi @araratthehero, here are my answers:

• I'm already using the latest SDK version 5.14.0
• I double-checked, and our UI customizations don't affect this behavior
• The issue seems specific to Blik and Card payment sheets — likely all drop-in sheets that involve soft keyboard input. I'm using these payment types as single-payment options in Drop-in with skipListWhenSinglePaymentMethod set to true

[araratthehero]

Hi @wrozwad, thanks for the additional information. I’m still unable to reproduce the issue.

Could you share the following details?

• Device type: emulator or physical device
• Android version
• Whether you’ve tested on multiple devices with different Android versions and if the issue occurs on all of them
• Does it only occur when the payment methods list is skipped in Drop-in? Try again without skipping the list by setting the skipListWhenSinglePaymentMethod flag to false.

[wrozwad]

@araratthehero

• Device type: physical Samsung S10e and emulator (API 35)
• Android versions: 12 and 15
• Yes, the problem occurs on all devices
• Change skipListWhenSinglePaymentMethod flag value does't change anything

Currently, on the emulator, I can see that the initial loader appears for a second and then disappeared. Only the second one remains permanently.

Additionally when:

• skipListWhenSinglePaymentMethod is set to false
• you open the payment sheet (BLIK or Card) from the Drop-In list
• click the "Pay" CTA on the payment sheet
• then go back to the Drop-In list and open the payment sheet again

...the "Pay" CTA triggers a permanent loader on the first click.

Can you try a simple implementation of SessionDropInService.onSubmit()) that just returns true?

override fun onSubmit(state: PaymentComponentState<*>) = true

[araratthehero]

Hi @wrozwad,

I tried a simple implementation of SessionDropInService.onSubmit(), but I still couldn’t reproduce the issue.

Could you share:

• A screen recording showing the cases you mentioned above
• More details about what you mean by the first, second and permanent loaders

[github-actions]

This issue is now stale because it has been open for 14 days with no activity. Please provide the requested information or the issue will be closed automatically.