Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue in ARQC Generation for CVN18/22 #103

Closed
ManojhM-1530 opened this issue Sep 10, 2024 · 5 comments · May be fixed by #106
Closed

Issue in ARQC Generation for CVN18/22 #103

ManojhM-1530 opened this issue Sep 10, 2024 · 5 comments · May be fixed by #106
Labels
enhancement New feature or request stale

Comments

@ManojhM-1530
Copy link

Hi @tilln,

While generating ARQC using the ISO8583 Crypto PreProcessor (ISO-8583 Version 1.3), I am able to generate an ARQC value, but we are getting declined error message due to ARQC. However, when I generate the ARQC using online tool, the value is correct, and I receive a successful response. I have attached the reference screenshots for your review. please note that we need to generate ARQC with CVN18/22.

Could you please assist me in resolving this issue? Is there any configuration that needs to be adjusted on my side?

*Note: Card number and key values have been masked.

Generated using online tool:

image

Generated Using ISO-8583 pre processor:

image

image

@tilln tilln added the bug Something isn't working label Sep 11, 2024
@tilln
Copy link
Owner

tilln commented Sep 11, 2024

Hi @ManojhM-1530

Thanks for reporting this issue.

I suspect it is caused by incorrect padding of the ARQC input data.

Could you please enter the value 80 in the "Padding (hex)" field and try again?

@ManojhM-1530
Copy link
Author

Hi @tilln,

Thank you for the advice. I added 80 in the "Padding (hex)" and generated the ARQC value and it worked for me.

Once again Thank you for the quick response.

@tilln
Copy link
Owner

tilln commented Sep 11, 2024

The user should not have to provide the padding or even know what padding method to apply.

Ideally, the CryptogramDataBuilder or CryptogramSpec should take care of that.

In fact, a padding option has been introduced but will only be released with jPOS v.2.1.10.
However, it does not consistently define the method to use for all cryptogram versions (only CPA).

A PR has been submitted at jPOS and will be included in the next release.

@tilln tilln added enhancement New feature or request and removed bug Something isn't working labels Sep 11, 2024
@github-actions github-actions bot added the stale label Oct 12, 2024
@tilln tilln removed the stale label Oct 12, 2024
Repository owner deleted a comment from github-actions bot Oct 12, 2024
Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Nov 12, 2024
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants