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

Unable To Board a Merchant

Open
#132 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
python

Research direction

Start with the merchant-boarding registration endpoint and compare the Postman request with the request that succeeds in the CyberSource portal. Review the listed Authorization, Content-Type, v-c-merchant-id, and Host headers, then follow the referenced authentication documentation or its replacement. Done means identifying the missing or incorrect authentication detail and confirming a successful registration request.

Written by the indexing model from the issue text.

Description

We are trying to board a merchant using https://apitest.cybersource.com/boarding/v1/registrations but we always get a error: UNAUTHORIZED_USER response.

It works fine when we do it from CyberSource portal but fails when we try to replicate on Postman.

{
    "response": {
        "rmsg": "{\"error\":\"UNAUTHORIZED_USER\",\"error_description\":\"UNAUTHORIZED USER\"}"
    }
}

So we are probably missing the required authentication headers but the documentation page for it leads to 404: https://developer.cybersource.com/docs/cybs/en-us/payments/developer/all/rest/payments/GenerateHeader/jwtTokenAuthentication.html.

Our current header is:

- Authorization: Bearer <Bearer> 
 - Content-Type: application/json
 - v-c-merchant-id: alpha_001
 - Host: apitest.cybersource.com

Please let us know if we are missing any authentication headers in our request.

Dominant language
Python
Stars
24
Forks
42
Avg merge
29m
Merged PRs (30d)
1

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.

More from CyberSource/cybersource-rest-client-python

All issues in CyberSource/cybersource-rest-client-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.