#wizzmotion
1 messages · Page 1 of 1 (latest)
Hi 👋
Currently the Pricing Table only allows the passing of a customer email parameter: https://stripe.com/docs/payments/checkout/pricing-table#customer-email
But this won't assign the purchase to the existing Customer AFAIK.
Correct
So the only way is to create my own custom pricing table?
then I can create a payment using my own customers id?
Yes, the Pricing Table operates similarly to Payment Links and neither one is Customer specific.
What you can do to reduce the amount of overhead would be to create a Pricing Table UI but use Stripe Checkout Sessions to create the link that each button would use
That would be linked to your customer
In fact if I build my own pricing table I can charge users withou leave my Desktop app correct?
How would you collect payment method information?
Using UI elements provided by Stripe?
in my React Application.
My App runs into Chromium.
I'm not 100% certain of our ability to support Chromium. Have you built and tested this workflow?
https://stripe.com/docs/js/element/payment_element
I mean using this.
my Chromium is just a embedded webBrowser.
My application in fact is a simple webApp in react
I understand that. And I am asking if you have a complete end-to-end test workflow built
what you mean to use stripe Checkout session? can I change the method of Pricing table? or you mean create my own custom UI and use a stripe button only to finalize purchase?
Yes I'll test it...
Just trying to find a easier path... befor this.
The approach i am suggesting with the Checkout Session would involve you building the front-end that looks like a pricing table. Your back-end would create the Customer specific Checkout Session for each of the options they have and you would use the Session URL to redirect your customers to the Stripe Checkout page: https://stripe.com/docs/payments/accept-a-payment
ok. I got what you mean.
I guide user on my side until he click to pay, then redirect him to a stripe checkout page.
That's it?
And is possible to have a Tier option into that checkout page? or a Monthly/Yearly option?
or already add a discount code when I send him to a Checkout page?
You would build any tiers or upselling into your Price models. But you can configure the Checkout Session to make that visible to the customer following this guide: https://stripe.com/docs/payments/checkout/upsells
You can also add discounts either directly on your server or provide the Customer with a promotion code they can apply.
So if I show the discount previously in my own pricing table ui, or user provide me a valid discount code (that I can check before, using api), When I send him to a checkout page, is possible to already pre-fill a discount code field?
Yes that is possible
You would add those to the discounts parameter when creating the Checkout Session: https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-discounts
Do you think I'll have more conversions, making users leave my APP, and finalizing purchase into browser? Or if i can use Stripe UI elements inside my desktop app, this will make no difference?
Unfortunately I can only advise on how you implement Stripe tech using our APIs. I dont' have any insight into conversion rates.
Sure... sorry for that question
No worries,
I just don't understand how can I send a user to a page with variable tiers, or monthly/yearly offers...
If I'll send him with a pi already filled.
What do you mean "a pi already filled"?
The Checkout Session doesn't create a Payment Intent until the user makes their selection
mmm, so I can send him to a checkout session and then display all my products there?
but if he decide this purchase will be using my own customer id?
almost the same of a Pricing Table, but with control?
No I'm sorry I think you are confusing the level of customization here.
Checkout is in between these two options