#ninja-legacycheckout-react

1 messages · Page 1 of 1 (latest)

modern pewterBOT
short abyss
#

ninja-legacycheckout-react

#

@trail needle yes extremely outdated. It's for our Legacy Checkout product we deprecated 4+ years ago when we released our newer Checkout integration. Also this was maintained by an external developer, not Stripe

trail needle
#

AHHH thats why this codebase is freaking failing payments, but some goes thorught, check this payment ID out to confirm for me that its this library that cause the errors, its in production, real money... card_1NGHJxBt7kb9IN0zbgQZHJWU

context: some guy have implemented stripe checkout in this web app and they used that library.

short abyss
#

that's not a "payment" that's just a Card id but yes that used Legacy Checkout which we deprecated over 4 years ago

trail needle
#

what do you need to check it?

short abyss
#

I already checked it and confirmed what you needed. I just explained at the same time that this id is a Card id not a Charge or PaymentIntent id which would represent a payment, that's all

trail needle
#

ahh okay, well thats quite funny that a senior developer implemented this 7 months ago lmao..

anyway, i see a sucesfull payment in the dashboard too, is it possible some payments would work anyway? po_1MsdrCBt7kb9IN0zspepvt4I

short abyss
#

That is the id of a Payout which represents money moving from your Stripe account's balance to your own external bank account.

trail needle
#

card_1MryUwBt7kb9IN0zPO88cKG0

short abyss
#

lol

trail needle
#

ch_3MryV1Bt7kb9IN0z3SdC7STU

#

there aha

short abyss
#

yes that is a Charge id for one specific payment. If you look at it in the Dashboard you can see if it worked or not.

#

Sorry I'm not sure what all those ids are for? I already explained what you're doing

trail needle
#

haha yeah.. well basically, this library using something that is depricated, most payments fails, but i see some suceeds, so thats what the ids is for, to see how its possible for some payments to suceed anyway

#

but anyway, this needs to be migrated.

#

so i think i'll use the react stripe payment components

#

as it needs to have its own UI

#

but yeah now i know for sure at least why payments does not work - the library is totally outdated.

short abyss
#

Legacy Checkout only accepts card payments and doesn't support 3DS. You're in Europe where 3DS is required most of the time, hence why it likely fails most of the time

trail needle
#

Perfect thanks! ---- how long time do you say it would take to migrate from the current lib to making my own checkout with stripes react PaymentElement? just give a rought estimate

short abyss
#

Impossible to say, depends really on how experienced you are with coding yourself and all that. Some people it'd take a couple hours, others 3 weeks

trail needle
#

im a senior typescript dev, but have not touched these stripe paymentelement before

#

so lets say ish 13 hours just to leave some room

#

and for testing

short abyss
#

or you use our Checkout product and it's drastically easier :p

#

but yeah if you are an experienced web developer I'd say a couple hours to have an MVP and then a couple of days to wire it all up

#

depends if you do card payments only or also local payment methods at the same time

trail needle
#

mmm alright, yeah they just want a popup with the credit card info and thats it. So it really does not seems that this will be hard of the payment elements does the validation etc..

only thing im concerned with is that i need to pass in a custom tax rate for different customers as the customers are at different places in europe

#
  • any easy way to do that as in the Checkout product? as the tax values comes from the user object in the DB so i have access to it when they do a payment
short abyss
trail needle
#

i mean with the paymentelements

modern pewterBOT
short abyss
#

like days of work extra

trail needle
#

haha fuck, so what shall i say to this client guy then, as ofc he want the stripe to work quick, and he want the same UI as he has now with the popup.

short abyss
#

go with Checkout 🙂

trail needle
#

but why would it be day extras if:
you just know this X user is from norway, caluclate the tax for the user, pass it into the payment element stuff

spring mist
#

Sure, that's the trade off here -- Checkout offers a complete solution where most of this is automatic but there is limited UI customization

#

You can certainly build that custom flow with the Tax API, it's just more work

trail needle
#

with more work, i need to know how much more work? what is required to pass in custom tax rate using the PaymentElements?

spring mist
trail needle
spring mist
#

I think you could get a working version faster than that, but making it work the way you need and handling all the edge cases (eg, handling customer addresses etc) is going to take much longer.

trail needle
#

yeah i need a production ready version that collects payments from multiple of countires in EU

spring mist
#

My recommendation would be: build the Checkout version first to get something that works ASAP. Then, while that's working to serve customers, you can build out the custom flow if the checkout version is not meeting all your needs.