#Puggle-SCA-migration
1 messages · Page 1 of 1 (latest)
HI 👋 what you need to do is going to vary depending on how you're currently integarted.
This guide should help point you in the right direction:
https://stripe.com/docs/strong-customer-authentication/migration
What will be the variations? I can see from docs there are a bunch of scanrios - if we're a SaaS company where people can pay upfront, monthly, quarterly etc and then may also pay again at start of next cycle, what scenario would we fall into so I can see what the docs say we need to implement
And is it likely to need Webhooks etc as the call to check if they have the right authentication?
Sorry, but your business scenarios don't tell me how you're integrated with Stripe. What are you using currently? From the screenshot I see a Charge object, is that what you're using to process payments?
And apologies, I don't think the doc I linked previously is a good fit here. We need to determine what your current integration is using, and then we can determine what updates need to be made to it.
From the looks of it I agree it seems we're using a Charge Obect. Apologies I was not the one who initially set up our instance. Do you know where I can specifically find the integration we use?
catching up here one min!
Do you know where I can specifically find the integration we use?
@hazy island hello! this would be in your own backend code, unless I'm misunderstanding your question?
I assume you're either using Charges (the legacy integration)
or the recommended (newer) PaymentIntents integration
Thanks for getting back to me! Where can I actually find the access to the backend code, so I can confirm this?