noirid_api

[flint iris]

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

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

[solar sonnet]

Hello, that would place a higher PCI compliance burden on you than using Stripe Elements. The fact that you are handling the raw CC info in your code and passing it back to your server will do that

Elements works because it prevents your code from even being able to see the CC info. Because you are only handling tokenized versions of the info, not the info itself, that lessens the PCI requirements

[cold stone]

I see, thank you for that! From what I understand, there is no dedicated Stripe Elements functionality that will allow my customers to just manage their payment methods (view, create, update). Therefore, if I wanted to offer such functionality I believe that using the API would be the only way to do that. Is that correct?

To be more specific, I want this functionality in a section of my app called "Manage payment methods". So this customer action won't be related to a checkout

[solar sonnet]

Correct, we have the customer portal but we don't currently have a pre-built elements component for this (though that is on the roadmap). So for now for the least PCI compliance burden you would want to use the payment element with a setup intent and a list of the user's existing saved PMs and can work with the PM IDs