#sindev_unexpected
brave orioleBOT
đ 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/1295433284469133415
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- sindev_unexpected, 3 hours ago, 13 messages
- sindev_unexpected, 3 days ago, 8 messages
wooden bridge
Hello, looking in to this. Can you send me a quick screenshot of what the PaymentSheet looks like for you now? Also I assume it goes back to the standard one-step sheet if you turn off Amazon Pay?
Amazon Pay doesn't seem to change my payment sheet significantly and I am having trouble finding info on the two step sheet that you are describing
Once I have a screenshot I should be able to look up what the SDK is doing and find if there is a way to go back to the other behavior
wooden bridge
Ah gotcha, I am trying to remember what exactly triggers that screen. Can you send me your RN code where you define the payment sheet and its props?
teal furnace
const { error } = await initPaymentSheet({
paymentIntentClientSecret: stripeIntent?.clientSecret || '',
customerEphemeralKeySecret: stripeIntent?.clientSecret || '',
applePay: {
merchantCountryCode: 'LU',
},
googlePay: {
merchantCountryCode: 'LU',
currencyCode: 'EUR',
testEnv: Boolean(+(Config.STRIPE_TEST_ENV ?? 0)),
},
allowsDelayedPaymentMethods: true,
merchantDisplayName: 'test.com',
returnURL: 'test://payment',
customFlow: true,
});
this one
easier this way
but I don't really control anything in the client side, mostly backend and stripe dashboard take care of the content inside the payment sheet
wooden bridge
Gotcha, thank you for the code, still looking in to this. I think this is more a factor of our saved payment methods functionality
Ah yep, that is exactly it. When I add the ephemeral key to my code I see the same thing
Checking to see if it is possible to start on the add payment method screen when passing an ephemeral key
teal furnace
but how is it possible, if apple pay is removed for example, I see the classical screen
but on countries where all these payment methods are supported, this two-step view is shown
it's like it started behaving like that our of the blue, the only change we did was adding Amazon Pay in stripe dashboard
wooden bridge
I am not quite clear on what you mean. As far as I know, that screen should always show up if the customer has a saved payment method. are you saying it shows up even if Customers don't have a saved PM but only for certain countries?
And if so, can you tell me a country that sees each behavior so I can reproduce?
teal furnace
yes, it shows even though there are no saved payment methods. The example I showed you in screenshots is from Ukraine
I can clarify more details tomorrow with the person who found this
I can't reproduce, because in Albania the Apple Pay is not supported, therefore I see just one-step payment sheet like normally