Payment with flex token example gives INVALID_DATA error
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
Research direction
Start by running Samples/Payments/Payments/payment-with-flex-token.js and payment-with-flex-token-create-permanent-tms-token.js as described in the issue, then inspect how each example builds the Flex token payment request. Trace the tokenInformation.jti handling and verify the examples no longer return INVALID_DATA for that field.
Written by the indexing model from the issue text.
Description
When I run the flex token payment example i.e.
node Samples/Payments/Payments/payment-with-flex-token.js
I get the following error in the response:
\"Declined - One or more fields in the request contains invalid data\",\"details\":[{\"field\":\"tokenInformation.jti\",\"reason\":\"INVALID_DATA\"
As these examples are supposed to be self-contained I expected this to work. Does anyone know what the issue is? I did try adding the jti value which you can obtain from the decoded JWT token but this didn't fix the issue.
Also note that the exact same problem applies to the payment-with-flex-token-create-permanent-tms-token.js example.
- 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
- 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.
More from CyberSource/cybersource-rest-samples-node
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
CyberSource/cybersource-rest-samples-node#72 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
CyberSource/cybersource-rest-samples-node#58 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
All issues in CyberSource/cybersource-rest-samples-node
Similar issues
-
idnits3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ietf-tools/idnits#363 ·
Maintainers usually reply within 1 day
-
prototype(verifier_token): map disallowed warning to contraindicated before composite precedence checkPossibly taken @drk-ram claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentrust-io/trace-spec#582 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 72/100
TheOdinProject/curriculum#31479 ·
Maintainers usually reply within 1 day
-
chore
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
SignalK/n2k-signalk#368 ·
Maintainers usually reply within 1 day