#яσчαℓтℓя

1 messages · Page 1 of 1 (latest)

wicked ingotBOT
flint bane
#

@junior raven let's chat here!

junior raven
#

I have recently built an Invoice API integration

#

A page that looked like this, minus the PaymentElement. Essentially, when you clicked Pay Now, it sent a request to the API and the API handled all the invoice creation, sending etc. via the Invoicing API

Screenshot_2023-03-27_at_22.59.44.png
#

however, today I decided that it isn't a good design especially because I need to replicate it across multiple different payment flows

#

So I decided to look down the Checkout flow route

#

Then, I spent all day building the checkout flow to realise that using the post-payment invoices requires you to use the Stripe hosted checkout form (as opposed to the custom form on our own website?)

#

So I was like okay surely this must be achievable some other way. But I guess it isn't? Unless you can point me in the right direction please 🙂 hoping I haven't waste my day of work

#

@flint bane sorry to bother. Here are my basic questions. Is it possible to send an invoice for a one-time payment using a custom-built payment flow with Checkout sessions or PaymentIntent?

flint bane
#

Okay, I don't think I understand your question. "custom-built" means you're not using Checkout

#

Could you rephrase what your goal is?

junior raven
#

Okay, I think you answered my question

#

Ultimately my goal is to build a custom checkout form that takes a one-time payment from a customer and sends them an invoice.

#

I just need to find the path of least resistance. And that is why I decided to (try) to move away from the Invoicing API.

#

@flint bane if that is the case, I have to say the invoice API is a nuisance to implement compared to the Checkout flow. I just don't understand why there isn't the option to have a custom built checkout form that uses the Checkout API to generate invoices...?

flint bane
junior raven
#

I have researched this. It doesn't let you use a custom-built form/flow

#

It forces you into using Stripe's hosted payment page.

flint bane
#

Right, exactly. "Stripe Checkout" refers to our hosted flow, which is why I'm confused by the mix of "custom" and "Checkout API"

wicked ingotBOT
junior raven
#

PaymentIntent API is part of Stripe Checkout API, and that doesn't require you to navigate away from your own site.

#

With the PaymentIntent API, you are able to keep the entire flow, payment and everything within your own website. The only issue with PaymentIntent is it doesn't offer any invoicing features that I am aware of. However, you can create a payment intent via invoice creation.

thin spoke
#

Hi, stepping in and catching up here

junior raven
#

I guess the root problem is that our Invoice API integration relies heavily on Webhooks. We are running auction website, so cronjob events take care of payments alongside webhooks.

We need to keep that isolated away from any manual one-time payments. What would you propose as a solution for managing one-time payments whilst still generating invoices for them?

#

@thin spoke

thin spoke
#

To summarize your ask, you're looking to create one-time invoices for one-time payments and trying to see what would work best here? What are you specifically looking to 'customize'?

junior raven
#

Yes that is exactly it

#

I have found the Invoice API to be rather complicated for simply setting up one-time invoices for one-time payments using a "Pay Now" button

thin spoke
#

Can you share why you're not wanting to use any Stripe hosted solutions?

junior raven
#

We paid a designer to create our custom checkout form

#

And our client has approved the checkout form design

#

Is it possible to have a custom domain for the hosted checkout form?

thin spoke
#

In this case, given that you'd want an invoice your approach of creating Invoices is the way to go.

junior raven
#

I personally think it's a last resourt

thin spoke