conrad-paymentlinks | Stripe Developers | Page 1

calm topaz Feb 21, 2022, 6:07 PM

#

I can't think of any solution that doesn't require using either the PaymentLinks or CheckoutSession APIs, or other custom code approaches, I'm afraid.

rotund ore Feb 21, 2022, 6:10 PM

#

Does the payment link API have capability to accept extra data? I'm not seeing anything on the docs

calm topaz Feb 21, 2022, 6:12 PM

#

I was thinking of https://stripe.com/docs/api/payment_links/payment_links/create?lang=ruby#create_payment_link-metadata .

Stripe API reference – Create a payment link – Ruby

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

#

but I guess you actually meant, you wanted the Stripe-hosted page to collect some arbitrary custom information from the customer

rotund ore Feb 21, 2022, 6:13 PM

#

no I'll collect the data, I just need to submit it

calm topaz Feb 21, 2022, 6:13 PM

#

which we don't support at all today(but a feature request we're keenly tracking). You'd have to have a web page that collects the info, and then redirects to Checkout/a PaymentLink

#

ok if you have the data then you could add it as metadata. If it's dynamic for each customer though you want to create CheckoutSessions directly I would think

rotund ore Feb 21, 2022, 6:14 PM

#

yeah it would be unique per order

calm topaz Feb 21, 2022, 6:15 PM

#

then in that case it probably makes most sense that when the customer is on your site and hits the "Pay now" button for their order, you create a CheckoutSession, pass metadata to it, and then redirect to the CheckoutSession. The metadata can be accessed in the webhooks after the payment. It's the standard integration https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=checkout

rotund ore Feb 21, 2022, 6:17 PM

#

ah ok, that looks reasonable enough

#conrad-paymentlinks