#mclowrider_api

1 messages · Page 1 of 1 (latest)

storm streamBOT
#

👋 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/1461719421864378368

📝 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.

cerulean fractal
#

Hi there, looking into this now. Do you have a link to the documentation you used regarding ephemeralKeySecret with the PaymentSheet? I will look to see if there is a migration guide or other documentation specific to your integration

versed basin
#

It has an anchor link on the text below that doesnt work

To use the latest features, we recommend migrating your existing integrations from customer ephemeral keys to Customer Session.

cerulean fractal
#

Got it, looking into it now

versed basin
#

Thanks 👍🏾

cerulean fractal
#

Can you let me know which platform are you using? (iOS, Android, React Native)

versed basin
#

iOS and Android

cerulean fractal
#

So not using React Native?

versed basin
#

No we are not

cerulean fractal
#

Got it

versed basin
#

Swift and Kotlin

cerulean fractal
#

Didn't find any additional documentation unfortunately. Conferring with a colleague to answer these questions:

If yes, are there any unintended side effects when migrating from ephemeralKeySecret to the customerSessionClientSecret?
There aren't any side effects, but the exact UI flow is going to change when you move to mobile PaymentElement + customer session, compared to the payment sheet UI. So you'll need to test everything out

Can we start populating the mobile_payment_element settings in the customer session in the backend before the native apps clients migrate?
You can start creating and consuming customer sessions in a dev app while your existing version works as before. If you production backend continues to serve ephemeral keys to existing clients, then there won't be any issue using the sessions in parallel

versed basin
#

the exact UI flow is going to change

In what way? Are they referring to the customer session settings or something else?

cerulean fractal
#

Let me double check. Can you share sample code where you were using ephemeralKeySecret so I can provide that exact context?

#

the exact UI flow is going to change
What they meant here was that some UI will change, such as the way saved payment methods are surfaced. So you should run through everything to make sure it acts as you would expect. Broadly speaking, you should be able to make this change without issue

versed basin
#

Ah great. I assume it would be based on any new customer session settings?

cerulean fractal
#

Yes, that's my understanding. Overall the migration should work without issue, you should just go through everything thoroughly to double check

versed basin
#

Ok Thanks nobs 👍🏾