#alan-tse_api

1 messages · Page 1 of 1 (latest)

steep tundraBOT
#

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

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

magic wraith
#

sorry it's me again

tiny karma
#

hi! I think you can use that yes, you get a Token tok_xxx object at the end and then you have to convert that to a PaymentMethod to use

steep tundraBOT
magic wraith
#

Why stripe hides this solution?Is there a history document for stripe? I'm afraid I'm missing something else to watch out for. For example, radar may miss data,just like ip useragent Without using elements.

tiny karma
#

it's hidden because most merchants will find it easier and more effective to use our documented integrations and don't have to go and setup libraries and developer accounts with other providers. It's more of a bespoke option you might work with our sales/integrations teams on when you have strong requirements.
I don't think it has any impacts on the things you mention since the information comes from the Token object.

magic wraith
#

Thank you. I know how.