#karlos-checkout-webhook

1 messages · Page 1 of 1 (latest)

rose moon
#

Correct you have to do that

#

we don't render it on the Event we send to your webhook

sour echo
#

seems like someone wasn't thinking this 'expand' thing fully. everything I do I have to make another call and expand it, so who's saving what data? LOL

#

I have a maintenance parse that used to include sub data in the customer objects, now I call the list and expand each one LOL

#

I have to listen to subscription webhooks for the Cx Portal stuff anyways so I guess I can just provision on subscription.updated, but then will have to build this for the payments. Oi 🤦‍♂️

#

and I say updated because one subscription checkout generated freakin 10 webhooks or so 😂 and created was inactive in every case

#

I also didn't anticipate checkout leaving customers in a pending state for 24 hrs if something fails. One of my testers used a live card in test mode and my bot provisioned them via maintenance for a day then removed it

#

"low code" lolol

#

sorry if this has become more venting, but damn it almost seems like the current API is half-done and half-anti-developer

#

Anywho you answered my Q and I thank you very much 😂 😄

rose moon
#

In theory you would only listen to checkout.session.completed though

#

but glad you're unblocked

sour echo
#

well to use the management portal effectively I'd need subscription events, I'm letting y'all handle that shit 😄

#

I pass CX, they do what I allow in dashboard, process webhooks, win. That part seems low-code at least

#

Time for some eats! thank you again! Though frustrating, it's really only an extra function between what I was gonna do and will do.

#

much like the parse lol