CyberSource / CyberSource/cybersource-rest-client-java

Get status transaction Payment

Open
#130 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
29
Forks
50
Avg merge
28m
Merged PRs (30d)
1

Description

Hello, I am trying to retrieve the status of a payment transaction through the sdk "" using the "refreshPaymentStatus" method of the "PaymentsApi" class but I get an error

--- [ntContainer#0-1] Invokers.ApiClient : {"submitTimeUtc":"2023-08-28T22:47:13Z","status":"404","errorInformation":{"reason":"NOT_FOUND ","message":"The requested resource does not exist."}}
--- [ntContainer#0-1] Invokers.ApiClient : ApiException : 404 Not Found

I am passing the Id retrieved from the PtsV2PaymentsPost201Response when I create the payment and I am also sending the code and ReconciliationId... how can I check the status of a transaction to know if it was paid or declined

I use sdk version: cybersource-rest-client-java:0.0.55

Note: I am also using the "Api reference" in the "Check a Payment Status" method and I get the same error.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the PaymentsApi.refreshPaymentStatus entry point and the SDK version 0.0.55, then compare its parameters with the API reference's "Check a Payment Status" method. Reproduce the 404 using the payment ID, code, and ReconciliationId described in the issue; done means the call returns the transaction status so paid and declined payments can be distinguished.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, payments
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.