Unable to perform Card-Present and EMV Authorizations
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, node.js
Research direction
Start with the linked CyberSource Card-Present and EMV authorization examples and API reference, then compare their required EMV and point-of-sale fields with the provided sandbox payloads. Reproduce both contact and contactless requests and determine which value causes INVALID_DATA; done means documenting a corrected request that receives a successful authorization response.
Written by the indexing model from the issue text.
Description
Following the examples at here and here, I am unable get a successful response in the sandbox environment.
Card Present + EMV (Contact)
Request payload
{
clientReferenceInformation: { code: 'TC50171_3' },
processingInformation: { commerceIndicator: 'retail' },
orderInformation: { amountDetails: { totalAmount: '1', currency: 'SGD' } },
pointOfSaleInformation: {
cardPresent: 'Y',
entryMode: 'contact',
catLevel: 6,
terminalCapability: 4,
trackData: '%B4111111111111111^SMITH/BETTY^23121200123456789012**XXX******?*',
emv: {
tags: '9F3303204000950500000000009F3704518823719F100706011103A000009F26081E1756ED0E2134E29F36020015820200009C01009F1A0208409A030006219F02060000000020005F2A0208409F0306000000000000',
cardSequenceNumber: '001',
fallback: 'true'
}
}
}
Response Body
{
submitTimeUtc: '2020-04-23T11:19:21Z',
status: 'INVALID_REQUEST',
reason: 'INVALID_DATA',
message: 'Declined - One or more fields in the request contains invalid data'
}
Card Present + EMV (Contactless)
Request payload
{
clientReferenceInformation: { code: 'TC50171_3' },
processingInformation: { commerceIndicator: 'retail' },
orderInformation: { amountDetails: { totalAmount: '1', currency: 'SGD' } },
pointOfSaleInformation: {
cardPresent: 'Y',
entryMode: 'contactless',
catLevel: 6,
terminalCapability: 5,
trackData: '%B4111111111111111^SMITH/BETTY^23121200123456789012**XXX******?*',
emv: {
tags: '9F3303204000950500000000009F3704518823719F100706011103A000009F26081E1756ED0E2134E29F36020015820200009C01009F1A0208409A030006219F02060000000020005F2A0208409F0306000000000000',
cardSequenceNumber: '001',
fallback: 'true'
}
}
}
Response Body
{
submitTimeUtc: '2020-04-23T11:22:38Z',
status: 'INVALID_REQUEST',
reason: 'INVALID_DATA',
message: 'Declined - One or more fields in the request contains invalid data'
}
I have a feeling that the EMV values are incorrect, but am unsure what is wrong as the response is pretty vague. Would appreciate if someone could correct my mistake.
- Dominant language
- JavaScript
- Stars
- 50
- Forks
- 50
- Avg merge
- 19m
- 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-client-node
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative insteadOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
CyberSource/cybersource-rest-client-node#173 · 1 reaction ·
-
Difficulty 3/5 Half a day Newbie friendliness 35/100
CyberSource/cybersource-rest-client-node#148 · 2 comments ·
All issues in CyberSource/cybersource-rest-client-node
Similar issues
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#3897 ·
Maintainers usually reply within 2 days
-
agent/quality hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
Maintainers usually reply within 1 day
-
check:failed feeds:add
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
iptv-org/database#36179 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day