CyberSource / CyberSource/cybersource-rest-samples-java

[network token] Profile not found

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

Nobody has claimed this yet.

Dominant language
Java
Stars
35
Forks
84
Avg merge
37m
Merged PRs (30d)
1

Description

I have created a test merchant account and replaced the key in the project with my own to conduct testing on the REST API.
The similar AuthorizationWithCustomerTokenCreation/CapturePayment API can be used as usual. Additionally, the management background is able to view debit records (no records are available in token management).

Subsequently, I created a profile and activated Payment Tokenization for it. The status of this profile is active.
I will provide with the replacement account ID for Tmsv2customersEmbeddedDefaultPaymentInstrumentEmbeddedInstrumentIdentifier.
However, when making a request, an error occurs stating:
{"errors": [{"type": "notFound", "message": "Profile not found"}]}

Why am I still receiving an error message indicating that an active profile cannot be found even though I have already created one? Thank you.

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

No source file or test is identified. Start by reproducing the REST API request described for Tmsv2customersEmbeddedDefaultPaymentInstrumentEmbeddedInstrumentIdentifier, then compare the active profile and merchant account configuration with the request context. Done means identifying the cause of the “Profile not found” response and adding a documented or tested correction if the repository contains a relevant sample.

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
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.