#bongo-checkout-php

1 messages · Page 1 of 1 (latest)

tranquil palmBOT
shut orbit
#

Hey there

#

When you say "invoices", is this for Subscriptions or just one-off invoices?

fringe kettle
#

sorry, one off invoices

#

our platform facilitates bookings for a DJ or band for a gig for example

#

there's quite a few limitations with the stripe invoicing API that are causing us issues, so we need to move to host the invoice page and logic ourselves, and use stripe for accepting payments on these invoices we create, only.... does that make sense?

#

I've fully built out the invoicing intergration using PHP, so im looking for advice on how to transition that on to payments accepting only

shut orbit
#

Oh okay so you don't want to actually create invoices in Stripe

#

You just want to take payments

#

Then you will create your own invoices to correspond

fringe kettle
#

yeah exactly -we didn't initially want to do this, but have to due to issues we have with limitations on the invoices api for our business use case. But yeah, now we need to create our own invoice logic and page, and we will use stripe to accept the payments (for our users who will still be connected accounts I assume)

#

im assuming we create payment links, or payment pages now via the API instead of invoices? is that what you'd recommend?

#

we dont want to build out any payments UX either, just link to a "pay now" page via our own invoice page and logic - the link from the Pay Now action would be the stripe part

shut orbit
#

Yep

#

So you either use Payment Links or Stripe Checkout here then

#

Depends on the amount of control you want over the actual Checkout Session

#

You likely want Stripe Checkout to be able to do more tracking of your customers since this is for invoices.

#

Payment Links is really more meant for a one to many relationship

fringe kettle
#

i see, okay - so in our code where I create an invoice line item, invoice then finalize:

  • $invoice_item = \Stripe\InvoiceItem::create([
  • $invoice = \Stripe\Invoice::create([
  • $invoice->finalizeInvoice();

Do you think it's as simple as just replacing this with API calls to create a payment / checkout page?

#

Will i still need to create a tax rate and customer for the connected account like I do with invoices? or can it just be a simple payments page for the connected account, where we don't worry about the customer (who is paying them)? that would make life a lot easier for our platform too

shut orbit
#

Would you want to use Automatic Tax instead here?

#

Or do you want to dictate the Tax Rates from your end?

fringe kettle
#

we will dictate the tax rates from our end, as they are set in our platform and invoice logic

shut orbit
#

Gotcha then yeah you would need to create tax rates on the Connected Account and pass them to the Checkout Session

fringe kettle
#

yeah cool, we already have that code sorted which is great (for the invocies implementation we have now)

#

and then we pass that to the checkout session, but don't need to create a customer for the connected account to accept the payment though do we?

#

we also currently use direct charges taking an application_fee I imagine we can continue to do that

shut orbit
#

Yep

#

You don't have to create a Customer unless you want to, correct.

fringe kettle
#

okay good to know, thanks! and in terms fo the code update required to do this, do you think itll be fairly simple to just change the api calls to checkout payment rather than an invoice, from our current flow of:

  • $invoice_item = \Stripe\InvoiceItem::create([
  • $invoice = \Stripe\Invoice::create([
  • $invoice->finalizeInvoice();
shut orbit
#

Which involves basically the same stuff from your invoice items and invoice

fringe kettle
#

okay easy, thanks for your advice

shut orbit
#

👍