Enum ScraperResultCode
public enum ScraperResultCodeFields
AccountNotSupported = 101ChallengeResponseNeeded = 1This very special result code may be returned from Login(JsonObject), ContinueLogin(JsonObject), InitiatePayment(SepaDocument), or ContinuePayment(JsonObject) when a challenge response value (usually a TAN) is needed to continue. In response to this result code the client shall obtain the challenge response value (i.e. the TAN) from the user and include it with the other credentials in a followup call to ContinueLogin(JsonObject) or ContinuePayment(JsonObject).
Exception = 999An exception occured during processing of the current call. Exception details are available in DisplayText and DiagnosticTrace.
Failure = 299A programmatic failure occured. Maybe missing JSON data or an invalid state for a method call. These should only occur when there is a bug in the calling code.
InvalidCsvData = 200LoginFailure = 202This code must only be returned by Login(JsonObject), whenever the login failed for some other reason than WrongCredentials.
NotSupported = 100QueryResponseNeeded = 2The user has to provide more information for Login(JsonObject).
Together with this result code, the the QueryHeading and QueryPrompt holds a prompting message text that shall be presented to the user. In addition a list of choices may be included in QueryChoices. If no choices are included, then the user must be able to enter arbitrary text. The user response text or Value must be stored in the JSON field QueryFieldName in the credentials supplied to another Login(JsonObject) call.
ScraperFailure = 201The scraper implementation encountered some unexpected JSON or HTML content which prevents further processing of the request. Usually this means that the implementation must be fixed.
Success = 0Operation was successful. With this Code, the properties DisplayText and DiagnosticTrace should be
null.WrongChallengeResponse = 204The given ChallengeResponse value was wrong.
WrongCredentials = 203The given security credentials have been proven wrong. Often this may be the result of a Login(JsonObject) with wrong PIN or password.