#micha-czernek_docs

1 messages ¡ Page 1 of 1 (latest)

austere martenBOT
#

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

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

somber stone
#

Hey ther,e can you share more detail about whats not working like you expect?

#

What is the code you're trying to use and what docs are you referring to?

dire galleon
#

And in them, CustomerSheet.initialize method looks like that:

CustomerSheet.initialize({
  // You must provide intentConfiguration and clientSecretProvider
  intentConfiguration: {
    paymentMethodTypes: ['card'],
  },
  clientSecretProvider: clientSecretProvider,
  headerTextForSelectionScreen: 'Manage your payment method',
  returnURL: 'my-return-url://',
});

Note is accepts an object, with keys like intentConfiguration and clientSecretProvider

#

It doesn't include neither intentConfiguration nor clientSecretProvider

somber stone
#

Hmm yea those docs appear to be quite wrong

dire galleon
#

Thanks, so importantly, we need to have customerEphemeralKeySecret generated by the backend - that is probably the biggest difference between the docs and actual implementation

#

And the problem is that the part describing creation of customerEphemeralKeySecret disappeared, or at least is not linked in mentioned doc anymore

somber stone
#

Sorry about this, I'm pushing on the mobile SDK team to look and get this fixed, its very confusing

austere martenBOT