CyberSource / CyberSource/cybersource-rest-samples-csharp
CyberSource.Rest.Client.NetStandard is deprecated but GenerateCaptureContextAcceptCheck doesn't work in CyberSource.Rest.Client
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 28
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
CyberSource.Rest.Client.NetStandard has been marked as deprecated and a notification to migrate to CyberSource.Rest.Client.
MicroformIntegrationApi.GenerateCaptureContextRequest isn't working locally for me, so I updated the cybersource-rest-samples-csharp project to provide the most recent examples.
However, I discovered it's still pointing at CyberSource.Rest.Client.NetStandard!
So I updated it to use CyberSource.Rest.Client, whereup I've found that MicroformIntegrationApi.GenerateCaptureContextRequest in GenerateCaptureContextAcceptCheck also doesn't work, so presumably the SDK is broken in someway.
This is a configuration issue I think, or just a general API error, but it's not being caught by the new SDK:
Exception on calling Payment Gateway API: - Invalid JSON response received from CyberSource API. This typically indicates an API configuration error or the CyberSource service returned an unexpected error response.","@l":"Error","@x":"System.Text.Json.JsonReaderException: 'e' is an invalid start of a value
As such, can you please answer:
- when CyberSource.Rest.Client
- when the samples project will be updated to use CyberSource.Rest.Client and provide examples of how to migrate
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the cybersource-rest-samples-csharp project with MicroformIntegrationApi.GenerateCaptureContextAcceptCheck and GenerateCaptureContextRequest, then reproduce the invalid JSON response using CyberSource.Rest.Client rather than CyberSource.Rest.Client.NetStandard. Check the API configuration and migration behavior. Done means the current client works and the samples provide updated usage and migration guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100