Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Received 401 Unauthorised response

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
api, payments

Research direction

No files, tests, or entry points are identified. Start by reproducing the process payment call and comparing its credentials, headers, and signature with the void, capture, refund, and retrieve transaction APIs. Done means identifying the cause of the 401 responses and confirming the affected calls succeed or documenting the required correction.

Written by the indexing model from the issue text.

Description

I am able to call process payment api. However, i received '401 Unauthorised ' response when calling void payment, capture payment, refund payment, retrieve transaction API. All using the same credentials and header signature method.

Anyone encounter similar issues?

Dominant language
JavaScript
Stars
43
Forks
66
Avg merge
1d 8h
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from CyberSource/cybersource-rest-samples-node

All issues in CyberSource/cybersource-rest-samples-node

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.