#pulley_invoice-events
fathom capeBOT
š 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/1283825924613210217
š Have more to share? Add more details, code, screenshots, videos, etc. below.
wooden pivot
@cursive dune I think there can be cases. But you really shouldn't use invoice.payment_succeeded. You should use invoice.paid which is newer and more reliable.
That one would be sent for all Invoices that get paid, even if no payment on Stripe. For example a $0 Invoice wouldn't have a payment but would be paid. Same for the "mark as paid" feature
Does that make sense?
pulley_invoice-events
cursive dune
Got ya. So whats the main difference in the two events?
Because what we have been using the payment succeeded for is to target the payment intent, in order to record transaction records on our system.
Because we are mainly using stripe for the payments gateway for our orders and subscriptions.
And storing orders on our system
Also on a side note are you able to help with a second question surrounding testing different payment methods?
wooden pivot
invoice.payment_succeeded had bugs where sometimes it wouldn't be sending for some edge-cases like the "mark as paid" so we added a brand new Event that fixed all the bugs. I recommend using the new Event, and then handling the case where there is no payment (I gave some examples).
and yes I can help with more questions but let's solve the first one first
cursive dune
Got ya, i will bring this up to the dev team.
In regards to testing. How do i set up an account that uses the different payment types.
For example Link. We have had some users use link, which we now have disabled on our system, until we can figure out how to replicate it locally to write logic surrounding it.
wooden pivot
You should be able to enable Link only in Test mode for example. Or just create a brand new/separate account to test this
cursive dune
Is there anything special that i would need to do on my user when going through the checkout to make sure that link is available to them, besides enabling that setting on our test env?
wooden pivot
I'm not sure how to answer that. I don't really get what that mean, what "my user" references, what you are trying to do that is or isn't working. It's also fundamentally dependent on the type of integration(s) you have
cursive dune
We have users on our website, that are attached to a stripe customer.
I am just making sure there are no conditions on the embeded checkout, that a customer has to match, in order for the checkbox to enable Link payments to appear.
Or does it render for every customer no matter what
wooden pivot
correct there is no dependency on the Customer object in the API
wooden pivot
sure thing!