#josula_api

1 messages · Page 1 of 1 (latest)

fathom pumiceBOT
#

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

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

silk marlin
#

What would be the right way to think about this? Maybe we are also misunderstanding some concepts here

#

In a nutshell: I need a paid invoice for an already paid transaction (think Paypal or CC) and I want to be able to connect both (so our tax layer can connect both)

wanton epoch
silk marlin
#

ok thanks will look into this

silk marlin
#

Ok I am still puzzled.

Right now, I simply create a paymentIntent and I capture it later. I just want to send a "paid" invoice at the same time. Why is this so complicated 🤔. Option 1 is not really an option because the customer pays it right away via e.g. CC. seems like a weird way of solving this.

option 2 costs additional 0.4% for basically generating a PDF (not an option for us)

option 3 seems extremely hacky and not the right way for us I think (not a native solution)

Regarding option 1: What would the flow look like here?

  1. Customer enters their payment method in a multistep checkout.
  2. We Create the customer if they do not exist in stripe
  3. We Create a Payment Intent with the chosen payment method (e.g. Paypal or CC)
  4. The customer reviews their order summary and hits "buy now". We then capture the payment.

How would above flow look like using payment as an invoice (option 1)? I cannot wrap my head around it.

wanton epoch
#

well Invoices don't support capture_method=manual yes, so that limits options if you have that requirement.

option 2 costs additional 0.4% for basically generating a PDF (not an option for us)
you'd be paying that in option 1 too, it's the cost of using the Invoice product.

For option 1 the correct way is what's the in the docs — you create and finalize and Invoice on the backend. That Invoice now has a payment_intent that it has created. You confirm that PaymentIntent on the frontend with Elements, to process the payment. You don't create your own PI.

#

with your requirements the only real options seem like option 3, or using your own bespoke code/a third party service to generate and send an invoice to the customer in your required format.

silk marlin
#

Ok I wonder what the most common approach is... I mean basically everyone in Germany has that requirement...

#

Thanks for your reply

#

I mean we just want to send a PDF saying "this is your paid invoice" with the payment. I do not see why we would have to pay extra on a payment we have already been charged for

wanton epoch
#

can't really discuss pricing, it's a technical channel; again I think given your requirements, if you require manual auth-and-capture option 1 and 2 don't work so to me the real solution is building your own bespoke solution/third party

silk marlin
#

Ok thanks! Sorry about that

#

Can you answer this though: Say we create an invoice, you pay it in the CO with CC, will we then get charged 0.4% for the invoice plus the stripe CC fee? Just for my understanding

wanton epoch
silk marlin
#

ok thanks!