#xzzd-paymentlink-customfields
fallen schooner
stiff oar
For example "T-shirt color"
drifting swift
Unfortunately payment links don't really support that if you are looking for something like having a T-shirt payment link and allowing the user to select different colors or sizes of the same T-shirt.
To do that with payment links you would need a link for each color which I understand could get cumbersome. Trying to think if there is another way to do something like this
Do you need this to be a no code solution like payment links or are you open to low code things like Checkout or even things like creating a custom page with Elements?
stiff oar
I'm open to a little coding
drifting swift
Gotcha. Checking in to what your options are there.
stiff oar
Thanks!
drifting swift
Unfortunately I am not seeing a good way to configure this for PaymentLinks/Checkout. It may be best to allow the user to select their shirt color on your page and then direct them to a page with the price for that shirt pre-selected.
Like I said with payment links that would likely include making a new link per shirt color. With Checkout you could likely have just one Product and have your server generate a Checkout Session with the appropriate line items
drifting swift
Apologies for that diversion. It looks like I was right the first time. You can't get to the price IDs from the PaymentIntent. If you only want to look at the payment intent based events then the invoice field is a great thing to check in your scenario. Otherwise you might want to listen to the checkout.session.completed and invoice.paid events to directly check whether this was a one time or recurring payment.
stiff oar
The thing is, I don't need to field to select a specific product, it is just for me to see some sort of a note
To sort my customers and know if I need to send red or blue for example, but they would all buy the same product basically
drifting swift
Ah gotcha. I think you can do that via URL parameters for the payment link, or you could set it as the description for things if you are using Checkout. I will double check on those (one caveat being that it wouldn't be in the UI for the user)
nimble cloak
👋 catching up on this! if you opt to use Checkout, you can also store information in metadata (this won't be shown to your customers): https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-metadata
stiff oar
I think I'll just add 0$ add-on products and customers will just choose
The crosselling option
No it does not work since I can only add one option
nimble cloak
I'm not sure I follow. In your t-shirt color example, would you like your customers to choose between a red or blue t-shirt before they submit payment?
stiff oar
Exactly, some field that would not change anything to payment but at least I'll see what color did they choose once the payment is done
that's it
nimble cloak
If customers should choose between colors, I think what Pompey recommended earlier makes the most sense: create a Product and Price for each color, since fulfillment on your end will differ based on what a customer chooses.
stiff oar
It's fine i figured out a way on my website