#dbueno_hiberus
rose imp
sonic sedge
hi! it should work, you're probably using an old version of the Java library
wintry basalt
Hi, i'm using stripe 21.0.0
wintry basalt
ok, thank you, I'm right now checking 21.13
sonic sedge
maybe it's not in the library(I'm looking and couldn't immediately find it), but it should be. The API itself supports this fine at least
if the method doesn't exist on the builder in the latest version let me know, there are other ways to pass it if the library hasn't added it
wintry basalt
I have checked version 21.12 (21.13 is still beta in mvn repository) and I couldn't find it
the thing is that it appears in the PaymentIntentCreateParams.PaymentMethodOptions.Card, but not in the SessionCreateParams.PaymentMethodOptions.Card
sonic sedge
ack, then for now you can do
.putExtraParam("payment_method_options[card][capture_method]", "manual")
on the SessionCreateParams.builder() and that will work
I'll raise with the SDK team to check into why this doesn't seem to be natively supported and hopefully they'll release a new version soon with a fix
wintry basalt
thank you very much for your help!
sonic sedge
no worries; let me know if that does end up working
wintry basalt
I'll try it right now
sonic sedge
yeah I notice this is not in the API reference either, which is weird
and related, since the library is autogenerated from the same data source as the API reference
wintry basalt
Error creating Stripe session: : com.stripe.exception.InvalidRequestException: Received unknown parameter: payment_method_options[card][capture_method]
i'm sorry but it didn't worked
sonic sedge
I might have taken the wrong approach actually, I thought we supported this parameter in general and it was just the library but maybe we don't
was there a specific guide you were reading that mentioned passing that parameter or was it just that you thought it should work(I think it should too but I'm checking if we actually built support for this(capturing some payment methods and not others, I thought we did))?
wintry basalt
I've read it here: https://stripe.com/docs/payments/place-a-hold-on-a-payment-method
but its always related to the PaymentIntent
not for the checkout session
bronze lance
👋 taking over for my colleague. Let me catch up.
sonic sedge
yeah sorry
I checked and we don't support this on Checkout, it was only built for PaymentIntents.
please write to https://support.stripe.com/?contact=true to mention that you want this and register the feature request(the team didn't build support as they didn't see demand, so it helps to register interest)
so without that, you unfortunately can't do this, you can only have the CheckoutSession have a 'global' capture method choice , which then limits the payment methods that can be chosen(i.e. if you pick manual then only Cards(and Klarna) are options).
wintry basalt
ok
I had already registred this on the support before opening this chat
as a workaround, If I implement the custom payment flow explained here: https://stripe.com/docs/payments/quickstart
this approach does not use checkout sessions right? Should I then be able to configure just card as MANUAL?
bronze lance
yes that's what my colleague was trying to suggest when they said it was only built for PaymentIntents