Regarding PaymentSheet class

[omertanveer]

Hi.

I am trying to create 2 separate instances of PaymentSheet in an android activity, lets say ActivityA.
So I have 2 separate objects PaymentSheetA and PaymentSheetB

Both of these payment sheets have their own separate createIntentCallbacks i.e, createIntentCallbackA and createIntentCallbackB

However when I call presentWithIntentConfiguration for PaymentSheetA, fill in the card details and press the pay button on the payment sheet, it ends up calling createIntentCallbackB instead of createIntentCallbackA.

Is somehow the PaymentSheet allowing only one payment sheet creation per activity?
If someone tries to create 2 payment sheet objects, does the createIntentCallback get overridden by the latest one?

Would be great if someone can shed some light on this.

[jaynewstrom-stripe]

Hi @omertanveer

This is indeed a current limitation of our implementation when using CreateIntentCallback.

Can you tell us more about your use case, and why you have nested activities that both could call PaymentSheet?

[omertanveer]

I have one single activity.
Not nested activities.

We have a scenario where within a single activity where apart from a regular cart checkout we offer a separate subscription which gives some additional perks.

So in the case if a user decides to sign up for the subscription then I want to use one payment sheet for this purpose.

And then a second payment sheet that can allow user to continue with the regular cart checkout.