#extraCo.Co-paymentlink
1 messages · Page 1 of 1 (latest)
Yup! How can we help?
I'm trying to sell my inventory or liscense keys. I put them in the metadate, but I don't see it on the receipt
product that i used a payment link for
Can you share the request id where you passed the metadata? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
I found the log, which one do I give you
From what you're describing, you're setting the metadata on the product object and not on the Payment Intent, https://stripe.com/docs/api/payment_links/payment_links/create#create_payment_link-payment_intent_data-metadata
You can share the request where you created the payment link
extraCo.Co-metadata
POST /v1/payment_links
Stepping back, why do you expect the metadata to show on the receipt?
The request id would start with req_ abc123, what you shared is the path
i actually have no idea what i am doing. i'm trying everything to sell my liecense keys. I moved my store from woo commerce to payhip and thought i could embed a stripe button on the payhip site.
oops i thought i pasted it before typing that...hold on
I see, you'd want to reach out to payhip, https://help.payhip.com/article/65-connecting-your-stripe-account as they own this integration.
req_8rfO3GrjXKmmF7
no, payhip's interface doen't offer what i need. i went to the stripe site, made products and buttons and used the generic embedd option on the page builder
I see, looking
To be clear, metadata is not surfaced to your customer, https://stripe.com/docs/payments/payment-intents#storing-information-in-metadata. It is for you to store additional details so you can use it for tracking/ reconciliation etc. Is your use case to include a custom text to your customers?
No worries!
am i trying to do something that stripe cannot do?
I'm unsure what you're really trying to do. You can send an invoice for one time payment and can pass custom fields to show on the invoice, https://stripe.com/docs/api/payment_links/payment_links/create#create_payment_link-invoice_creation-invoice_data-custom_fields for instance. However, I'm not sure what your use case is here and what you're looking for exactly. Can you share more details?
yeah sure, usually customers buy one of our books and get a code in the back to enter on our website inorder to take an assessment. when they do not want to wait on amazon and take the assessment instantly, they can come to my site and buy the code. they should receive their unique liscense key via email or receipt right away.
If you do not want to send an invoice, you can pass a description, https://stripe.com/docs/api/payment_links/payment_links/create#create_payment_link-payment_intent_data-description on the payment_intent_data which will be displayed to users.
Is this code unique to each customer?
yes and there are 3 different types of assessments they choose from
The intent of a payment link is to have shareable URL that will take your customers to a hosted payment page and can be used multiple times. Although you can limit the number of customer that can use the payment link for completed payments, https://stripe.com/docs/api/payment_links/payment_links/create#create_payment_link-restrictions-completed_sessions-limit I do not think Payment Link will solve your business use case as you scale. As you scale, I recommend that you start with our low code, https://stripe.com/docs/checkout/quickstart integration instead.
Otherwise, you can pass a description, https://stripe.com/docs/api/payment_links/payment_links/create#create_payment_link-payment_intent_data-description on the payment_intent_data which will be displayed to users. We talk about this here, https://stripe.com/docs/receipts?payment-ui=payment-links#customizing-receipts
are you able to help me in layperson terms. these are a lot of pages and hard for me to look at
Which part? These are very important for you to read and will provide a good explanation. The summary is that as you scale in your business, I recommend that you use a different integration with our low code Checkout Sessions. In the meantime, you can pass a description, on the payment_intent_data which will be displayed to users. This custom text will be the authorization code. Does this help?
yes i think i understand, not lazy- they aren't very assessible
extraCo.Co-paymentlink
there are several that start with payment intent data and this doesn't seem like a procedure. is this a glossary page? when i scroll i can't see where i started so i have to go back to the linke and re open
i don't not understand what this is telling me to do?
Ah, it looks like you're using the Dashboard to create the Payment Link. You'd need to use the API, , https://stripe.com/docs/api/payment_links/payment_links/create#create_payment_link-payment_intent_data-description to make this call to pass that information. I do not think it is possible if you use the Dashboard. This chat is focused on developers and technical questions, and I recommend that you reach out to uur support team that will be able to assist you better than I can: https://support.stripe.com/contact.
My battery is low and it's getting dark.
this is the only help i could get that wasn't just pages of instructions i could hardly read. there isn't even an email option. thanks anyway
You should be able to email them directly, https://support.stripe.com/contact/email.
thank you so much!
Sure!
what is api i need to ask about instead of license keyy?
I do not understand what you're asking here. Are you asking what API and what parameter to pass to share with your customer?