#nobody_api

1 messages ¡ Page 1 of 1 (latest)

small sandalBOT
#

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

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

lament vergeBOT
#

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.

worldly coyote
#

const cardId = 'ic_1ITi6XKYfU8ZP6raDAXem8ql';

#

^ this is the card id im referring to

hasty light
#

Yeah, Card IDs (along with most object IDs) are totally safe to use in the front end

worldly coyote
#

Perfect thank you!

#

And these would only be used if a customer enabled "setup_future_usage" right?

#

(cus otherwise you wouldn't have a payment method to retrieve for them ?)

hasty light
#

You'd still have a Payment Method, but it might not be usable if it wasn't setup for future usage

worldly coyote
#

So after payment intents, it still saves the method to the customer object without setup_future_usage?

#

I'm asking to figure out the best way to manage customer payment methods without accidentally using a payment I'm not allowed to