Using UnstructuredRemittanceIdentifier in MD5FingerPrint #7
+51
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 similar comment
This detail is not clearly described in the current EPS documentation.
bountin
force-pushed
the
bugfix_unstructuredRemittanceIdentifier
branch
from
75f511b
to
01e2b23
Compare
|
Thanks for your contribution. As my partner bank didn't provide any test system and I was using only the RemittanceIdentifier - I never had the problem. |
hakito
added a commit
that referenced
this pull request
Apr 23, 2015
…ifier Using UnstructuredRemittanceIdentifier in MD5FingerPrint
|
Yeah, the Erste cooperated pretty nicely (especially for a Bank's IT) :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The EPS API requires the use of the unstructured remittance identifier if it is specified in the XML. The Pflichtenheft is ambiguous in that point but may be fixed in the future. This fact was explained to me by their support team.
Without this patch no transactions with an UnstructuredRemittanceIdentifier can be made as it will return a fingerprint issue (and finally lock your account).