-
Your code doesn't indicate you have to setup NLog anywhere.
When it's not setup the entire nuget fails to load anything. It seems you have to not only setup NLog now, you also have to add a magic u…
-
We use CyberSource in our software as a payment processor. Our assemblies are all signed. Our solution is unable to make the API calls to CyberSource to the newly provided dlls because they are not si…
-
Next.js tries to load the import as AMD, due to relative path resolution in Webpack to get this library to work you need to add the following to next.config.mjs.
```
const nextConfig = {
webpac…
-
So it seems that in Cybersource, there is an authorization and if successful, a charge. CiviCRM is recording both of these as payments and I think this has led CiviCRM to send two receipts, one for th…
-
Under Readme section "Using the Sample Code" - https://github.com/CyberSource/cybersource-rest-samples-php#using-the-sample-code - it states "The samples are all completely independent and self-contai…
-
According to this you should be able to log all the traffic to the API by setting "enableLog", and "logDirectory", "LogFileName". However it doesn't work:
https://github.com/CyberSource/cybersource-…
-
https://www.nuget.org/packages/CyberSource.Authentication/
v0.0.0.9 has a package dependency on NUnit 3.10.1
This package is not required. Application code should not have a dependency on a tes…
-
We were using this samples project while integrating the API into Drupal Commerce, but we realized that the version it uses of the REST client is outdated. Certain code changes in the client made it h…
-
## Issue
Passing a `DateTime` object as the `$reportDate` parameter into `CyberSource\Api\ReportDownloadsApi::downloadReport($reportDate, $reportName, $organizationId = null)` produces an error, desp…
-
CyberSource `XML parse error.` errors should probably be handled as `CANCELED` transactions.