#bk_confirmationtokens-customers-addresses
eternal cometBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1256308630446407862
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
sour kraken
Not explicitly. I think I was assuming that under the hood, when you do an intent, it is creating some sort of customer to go along with the payment? Is that not the case?
hollow current
No that is not the case
You can pass back address information without a Customer, but only billing addresses will be saved to the Payment Method.
From the sound of your integration, I think it would make the most sense to create a Customer and include them in the flow
You can get all these details from the Payment Intent itself but you would not have them associated with any Cutomer object
sour kraken
Yea. Potentially. Do you have any recommendations on when to create a customer? Like, if I use createConfirmationToken and then send the info and create the customer on the backend, is that the desired flow? Do I need to then attach the intent to the customer?
hollow current
For instance, I just added the shipping address code to my Finalize on Server integration and I can see the address I passed in the successful Payment Intent
sour kraken
You can get all these details from the Payment Intent itself but you would not h...
Oh. Interesting. This may be all that I need then. We basically only need the billing details (name, address, etc) so that we can send it to Salesforce from the backend. So I just need to get those from either our frontend or from you all. But if it's part of the intent, then I likely don't need to include it on my API call too. I can just grab it from the intent on the backend.
Are there any benefits from creating a customer vs just getting things from the intent? Right now, we sort of have a generic donation form, but if we, at some point, put this inside a login, would it be more helpful to have it on a customer so we can route through the customer for keeping payment info for future use?
hollow current
If you see yourself going to a future with repeat customers (especially with authentication) then it can be pretty helpful to have Customer objects as part of your flow. It will make it easier to link payments with specific individuals
sour kraken
Cool. I appreciate your help on this!
hollow current
Sure thing! Happy to help 🙂
sour kraken
One more quick question for you. How does this change when the mode for creating a token is subscription instead of payment or intent?
We have sort of a 2 pronged donation flow where folks can set it to be recurring or one-time.
hollow current
It would change what objects the data is saved to.
sour kraken
as in paymentIntent vs whatever the subscription is?
hollow current
The Subscription object. Honestly I recommend building a super basic version of this integration. If you have Stripe API keys you can get something basic & hard-coded up and running within an hour
Then you can poke at it and see what the API responds with
sour kraken
Cool. I will play around with it. Appreciate you! Have a good day/weekend
hollow current
You too! 👋
eternal cometBOT