#dennis_de-metered
1 messages ยท Page 1 of 1 (latest)
hi! possibly using Checkout directly (https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=checkout) in a page/code you right yourself, though I'd have to check if Checkout itself supports metered prices.
yep seems like it does, so that's the good alternative.
hi this is not subscription, it is simple payout which was working before
also, what exactly means metered price?
@spark pebble Wrong thread ๐
Hmm... I honestly wanted to just send the user to you guys and then back. So the payment links are actually fitting.
But if this is not supported, I guess I'll have to think of something else....
well Checkout is mostly that, it's the same thing really.
I'm looking at it right now.
it's just that you have to build the page that contains the link the user can press to pay and then call the API to create the Session and redirect them to it
the actual payment page is the same, PaymentLinks are just a way to have a static link to go to a Checkout page.
Yeah, I'm looking at it right now.... is basically really just another end point... thank you!
I think you helped me with this ๐
@bleak pulsar For a checkout session, is there an option to create a one-part invoice only by the 1st of the next month? Example: Today someone uses Checkout Session and subscription is created, should be billed only 15.07 - end of the month and then from 01.08 - last day of August. Do you understand what I mean? Prorated topic.
yeah I think what you're asking is if you can set the billing_cycle_anchor (i.e. you want https://stripe.com/docs/billing/subscriptions/billing-cycle#new-subscriptions to have "a billing cycle anchor in the future and a prorated invoice until the anchor,") , which is not possible on Checkout today unfortunately since it doesn't support billing_cycle_anchor yet.
What would be your recommendation then? How we should implement the checkout?
We could theoretically create the subscription ourselves, but we would have to enter the payment method beforehand.
well it depends if that latest requirement is an absolute must have. If it is then you can't use Checkout and would have to directly build the payments page using Elements etc(the other tab on that integration guide , https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements )
Ok, thanks
@brittle chasm Could you share your Stripe account ID?
We're tracking merchant requests for those particular workflows with Checkout so I can log your interest
Do you have a beta for me? ๐
Ahhh ok
We have several accounts (from customers) that are interested in it, moment.
acct_1KGSMZCkcPaspCvs
acct_1LEBdEKSCBaxYA7a
acct_1KItHkLx20s3WIYn
acct_18zRphLzi9jCfKfX
Nothing to share just yet! But if we do, you'll likely be first to hear now I've logged your interest
good to know!
We love Stripe, especially as developers, but it's always sobering when you have a feature in mind and then realize that Stripe again doesn't work at that point like it does at another endpoint... if Stripe has a weakness, that's it, somewhere.
It's not like Stripe can't do that.... just not at the one place again...
Yep, not every payment UI supports every payment flow. Often about striking a balance between complexity and usability
I understand... is still frustrating ๐
Checkout is intended to be on the lower end of complexity, but we're always keen to hear about use cases we don't currently cover!
And because you just don't know what "not yet" means at Stripe, so it means "soon" or "more like in 3 years." There is a lack of transparency in the roadmap, so that customers know in which direction they can prepare themselves.
If I knew now that you were working on it and it followed promptly, then I could weigh which way to go.
Whether we transition to billing on the 1st of the month or invest the effort.
Hmm... I miss here the payment option of the bank transfer (SEPA Credit Transfer Europe)? @hearty ginkgo
Where is 'here'?
How can I provide them during a checkout? So that the IBAN is generated and stored in the customer?
Sorry.
Checkout Sessions Create
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Yep, SEPA CT is built on Sources API which Checkout does not support
Not really no as Sources are an older API that we no longer support on payment UIs
Are there any plans to bring the bank transfer to a new API? When Sources is phased out?
In Germany, the bank transfer is still a strong means of payment. It would be good if the customer could choose the payment method besides credit card and direct debit.
Especially in the B2B environment.
Yep, we just released a new PM for bank transfers: https://stripe.com/docs/payments/bank-transfers
Doesn't support Checkout currently
ETA for support?
Or if there is no ETA yet, can you also express our interest here and let us know as soon as that changes?
I can share that feedback with the team, yep!
Thanks