cybersource / cybersource-plugins-commercetools Goto Github PK

can @brianmc @carlosalaniz @krishnaprasadsn25 @jbransvisa anyone please help me to integrate the cybersource with commercetools because I read all the steps but I am not able to understand what to do in commercetools and what to do other things as am I new learner.

I'm submitting a question about how to use this project

Summary

@mattsmi86
would like to ask how we could determine if account is Sale is enabled so we could set the field custom.fields.isv_saleEnabled.

just wanna clarify if this is an account level setup, or this is just a flag here in this plugin if we're gonna charge customers that we can turn off for some specific scenarios (e.g. testing purposes)??

Hoping for your response here. Thanks

• I'm submitting a question about the decisions made in the repository

• Summary

we're currently working on a project and planning to use this for our commercetools integration with cybersource.
just wanna ask some questions about the 3DS setup.

seems like the PAYMENT_GATEWAY_3DS_RETURN_URL is defined via ENV VAR. just checking if this is correct since we might be defining this dynamically for each request that requires authentication check.

• I'm submitting a ...
  [x] bug report
  [ ] feature request
  [ ] question about the decisions made in the repository
  [x] question about how to use this project

• Summary

ESLint has over 1000 errors.

Is there any reason to have ESLint there, is this expected? The Circle CI/CD workflow runs the linting as well, which results in over 1000 errors and hundreds of warnings? Is this intended, or is ESlint being simply abandoned? (if so, should it not be excluded on CI/CD, etc.)