#jaybabu_code
quick lightBOT
👋 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/1480774787340046347
📝 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.
- jaybabu_best-practices, 6 days ago, 59 messages
⛔️ Stripe developers have stepped away for a short while
Please leave your questions here, and we’ll respond as soon as we're back! If you need help urgently, you can contact Stripe support for help.
pulsar tinsel
Avoiding most sensitive information. This is an example of where attached a stripe customer. had the customer pay and got the same payment information multiple times. the fingerprint is the same
We would like to collect all their different card information hence just stopping after collecting one payment method isn't correct either
quick lightBOT
lone belfry
avoid creating duplicate payment methods for the same card on a customer? We don't know the card details until the customer taps their card which is after the process call
Instead of process_payment_intent, you can do collect_payment_method
At this point, you can access attributes like card brand, funding, and other useful data from the PaymentMethod.
When you use collect_payment_method, you should be able to access attributes from the PaymentMethod, of which, you can access the fingerprint [0] and check if it is the same as an existing payment method attached to the Customer
pulsar tinsel
These all cost RPS which Stripe won't allocate more of to my platform account
I have 100 RPS limit for my entire platform which consists of 100s of active clients hence I cannot allocate more API calls in the sync path of collecting payments. For everything else, i listen to webhooks which avoid additional stripe api invocations
lone belfry
These all cost RPS which Stripe won't allocate more of to my platform account
Apologies, what does RPS stand for?