ml2e_api

[hexed badge]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1270755215288700999

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[lusty needle]

Hello, looking in to this. This may be restricted to cards at the moment but I am double checking

[lusty needle]

Unfortunately as far as I can tell this behavior does not support PayPal at the moment and there isn't another way to prefill address info.

[rapid parcel]

Okay 😦 Thank you for clarification.

But what are my options? Our upcoming business relates on customers ordering credits as often as possible.

Having them fill out the billing address for each order is a big no go for conversion rates.

Do i have to fully embed and integrate the API and get rid of stripe checkout? Will this then work with paypal?
And if so whats the status to listen to in a webhook [invoice.paid] or [payment_intent.succeeded] or [invoice.payment_succeeded] or [charge.succeeded]?
Currently i relay on [checkout.session.completed] cause i dont have async payments.
Thats a little bit confusing for me.

Any ideas? Maybe any tutorial? Thank you!

My goal is that they can order with paypal witout filling out everything again for each order.

ALso what happens if i disable the option to enter billing_adress in checkout at all and i remove ('billing_address_collection' => 'required', ) what billing address will be on the invoice then for paypal orders?

[lusty needle]

Trying to figure out your options now. Can you tell me more about what you are using the billing address for here? Is this tax or something else?

[rapid parcel]

Mainly for the invoice for the customers so they can define billing address on their invoices

i am using billing portal and checkout with 'invoice_creation' => enabled

billing portal for subscriptions, checkout for one time payments to purchase credits

for tax im using your auto mode

[lusty needle]

From my testing, one thing that may help would be that if the customer object has a billing address set, that will be transferred to the invoice even though it doesn't show up on the Checkout page. So it would be disjointed but you could set address collection to auto if you know you have an address for the customer. Unfortunately that would mean there would be no address field at all for payment methods that don't require and address and a completely blank set of address fields for the ones that do.
Otherwise, it does look like the address element allows you to programmatically prefill address details, so moving to an elements integration could give you the interface you want here though I do understand that elements is a bigger lift than Checkout.
https://docs.stripe.com/js/elements_object/create_address_element#address_element_create-options-defaultValues

[rapid parcel]

Question to assure if i got that right:

If set 'billing_address_collection' => 'auto', for paypal payments it will use the billing address already set for the customer for the invoice if it exists?
That would help so i could do 'required' if no billing address is set and 'auto' if its set already cause i have the customer object in sync with stripe.

About that address element im not sure if i got that. Can i attach such an element to a checkout session?

[lusty needle]

If set 'billing_address_collection' => 'auto', for paypal payments it will use the billing address already set for the customer for the invoice if it exists?
That would help so i could do 'required' if no billing address is set and 'auto' if its set already cause i have the customer object in sync with stripe.
Correct, that would be the workaround for Checkout, though I should mention that this would be the address set on the Customer object's address property. Though Checkout can update that if you set customer_update.address to auto

[rapid parcel]

Great. That should work. 👍
Can you please give me another hint about that "Address Element" ? Can that be used with checkout ? Im not sure if i understood its use.

[lusty needle]

Sorry meant to speak to that but got distracted by another thread. The Address Element can only be used for non-Checkout elements flows as far as I am aware but I am double checking that

So I was slightly wrong, you can use the Address Element by itself, so you technically can have Embedded Checkout along with the Address Element but that would mean that embedded checkout would still show empty address fields for any payment method that requires address details. So if you are moving to a custom elements page, it would make more sense to do this with the Payment Element + Embedded Checkout, because the Payment Element knows to hide its address fields if the Address Element is on the same page.
https://docs.stripe.com/elements/address-element?platform=web#use-address-element-with-other-elements

[rapid parcel]

Okay got it. Awesome, you helped me a lot, with a workaround and a possible solution to do it better later on. Thanks for that !!!
Maybe just one last question. To you have any kind of official roadmap, issuetracker or uservoice account where to submit new feature requests.
Cause i stumbled upon a few missing features already while implementing Stripe for the fist time.

[lusty needle]

If you are interested in making your own elements page, I'd recommend reading through these docs. Basically because you want to have an invoice at the end of this, your page would do these flows except for instead of creating a PaymentIntent directly, you would create an Invoice and use the PaymentIntent that it creates.
https://docs.stripe.com/payments/accept-a-payment?platform=web&ui=elements
https://docs.stripe.com/payments/accept-a-payment-deferred?platform=web&type=payment
https://docs.stripe.com/payments/build-a-two-step-confirmation

If you reach out to our support team they can file feature requests for you. I don't think we have a formal issue tracker outside of things like the issues page on our github for our client libraries. Our support team can keep you updated on feature requests but fair warning for a lot of them we can't guaruntee if or when they will be added https://support.stripe.com/?contact=true

[rapid parcel]

of course, must be a huge backlog 🙂 Great you really helped me thanks a lot and have a great day!