CyberSource / CyberSource/cybersource-rest-client-php
No API for Chargeback Reports or Summaries
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 41
- Forks
- 77
- Avg merge
- 26m
- Merged PRs (30d)
- 1
Description
In lib/Api/, there are no APIs provided for the following:
- Chargeback Details Report: https://{urlPrefix}/reporting/v3/chargebackdetails?
startTime={startTime}&endTime={endTime} - Chargeback Summaries Report: https://api.cybersource.com/reporting/v3/retrievalsummaries?
startTime={startTime}&endTime={endTime}
Where {urlPrefix} is "api.cybersource.com" or "apitest.cybersource.com", and {startTime}/{endTime} are ISO 8601 timestamps like "2017-10-01T10:10:10+05:00"
Since these two endpoints have different parameters and URIs than the regular report downloads (/reporting/v3/report-downloads) in lib/Api/ReportDownloadsApi.php, that one cannot be used.
I kept trying to use ReportDownloadsApi.php mistakenly and kept getting a resource not found error. The Servlet to REST API Migration Guide says the Chargeback reports are retired.
However, I eventually tracked down a PDF called Reporting_API_WellsFargoPaymentGateway.pdf that reveals they are not in fact retired, and gives the required URI and parameters.
I think it would be very helpful to include API classes for Chargeback Details and Summaries reports.
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 by reading lib/Api/ReportDownloadsApi.php and compare its conventions with the Chargeback Details and Chargeback Summaries URIs and parameters in the issue. Use the linked migration guide and the Reporting_API_WellsFargoPaymentGateway.pdf reference to verify the endpoints. Done means API classes exist for both chargeback reports and expose their documented parameters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100