#Jechris Olaya-sca
1 messages · Page 1 of 1 (latest)
If you were not already SCA compliant, it's unlikely that just upgrading your API version would make you automatically compliant. What is your integration currently doing?
I have a client website that has a payment issue. Its now declining the payment. So they seek for help regarding making it compliant.. Its a wordpress website... However the issue is the only change that I can make in the site is the API Key and secret. Would need your guidance in making it SCA compliant, Is there any settings in stripe platform that I can set up for this to happen?
Are you using a wordpress plugin? Or have you written the code to integrate with stripe yourself?
the plugin is already created. actually its in a theme...
the plugin is just using api keys
is there an option that I could setup in stripe dashboard so I can make it SCA compliant?
It really depends on what the plugin is doing - like for example, if the plugin is using Charges, that API is not SCA compliant and the code would have to be changed to use Payment Intents instead (this is not as simple as just changing your API keys or your API version)
I see, so we have to make a way for the plugin to use payment intents?
That's correct
i see thank you
is there any other way of doing it without editing the theme/plugin?
No, if your plugin is using charges there is no way to be SCA compliant