#josula_api

1 messages · Page 1 of 1 (latest)

quartz scarabBOT
#

👋 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/1484567277159452742

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

inland sundial
#

Hello, looking in to this and will get back to you with what I can find.

fringe beacon
#

So maybe a more detailed view on our flow. Maybe you have a general idea what would be the cleanest way to do this:

  1. The customer finishes their purchase using a BNPL payment method, Billie, which creates an authorized payment intent.
  2. We also create a draft invoice based on the order.
  3. As soon as we ship the order, we capture the payment, finalize the invoice, and we attach the payment to the invoice so that they are connected in Stripe.

=> For some reason this creates multiple payment intents in our transaction dashboard, which is extremely cluttered and hard to understand now. Ideally we only have one payment intent and one invoice per purchase

inland sundial
#

Gotcha, and is there a specific reason you are creating the payment intent before the invoice is finalized?

fringe beacon
#

I am not quite sure I understand. The payment intent is created so that the customer can pay in the checkout. The invoice can only be finalized as soon as the goods ship. We are selling heavy industrial spare parts that sometimes take one week to be shipped so between order entry and shipment a whole week passes.

#

You finalize the invoice in e-commerce as soon as you ship the goods not when the payment is made

#

That is why we don't use the payment intent of the invoice because to get the payment intent of the invoice the invoice needs to be finalized. At the moment where we need the payment intent, which is when the customer pays the invoice, it cannot be finalized yet

inland sundial
#

Interesting. Is that a regulatory requirement in your industry?

fringe beacon
#

This is standard European law?

#

When you order on Amazon, you always get your invoice the moment they are shipping the goods, not when you pay. Check your emails 😉

#

The payment itself is not the actual provision of goods or services. This only happens once you ship it hence you have the delay between finalizing the invoice and capturing the payment.

#

hello?

#

I mean regardless of the state of the law, is there any way I can solve this cleaner?

#

Would be very appreciated

inland sundial
#

I am not in the EU, but that is good to know! I'm not finding specific guidance on this for our invoicing, but it may be worth double checking this with our support team if you haven't already. Sometimes regulatory requirements don't apply to Stripe objects in the way you would think.
To get to your actual question from the thread, unfortunately I am not finding a way to attach these intents by default or to delete the original intent on the invoice. I can file feedback about this being a helpful feature though

fringe beacon
#

Thank you, all good. I will find a way