mandate initiation request iso mandate initiation additional merchant related data authentication data CustomerBIC for Routing Information mandate initiation response status reference for use in MandateServiceStatusRequest initiation acceptance data the status of the process request for retrieving the status for a specific mandate process the reference got from MandateServiceInitiationResponse top identify a single process authentication data the status for a specific mandate process the report when mandate was accepted the status of the process signature from debtorbank or scheme operator the status of the process mandate process as defined in initiation has been completed process ended without processing the mandate as given in the initiation process status is not clear: the process may still be in progress or there was a technical error so that the status is undetermined error description for status NOK xml invalid: broken or syntactically wrong xml inconsistent: corresponding data within the xml does not match authorisation wrong: hash/status reference wrong or even CreditorId (registered) is wrong type of process not supported unspecified error: external error with no specific handling by the scheme operator: might be when debtorbank sends inconsistent data which should never be internal error: an internal error at the scheme operator process timeout: expiration time exceeded connection timeout/error: debtor bank may be not reachable additional concrete information in form of describing text data needed by the creditor to continue mandate process the url to redirect the debtor to for choosing his bank language for the banking-gui used by bank merchant related data the url to redirect the debtor to after process has been completed on banking side the url to receive the mandate acceptance report set by the scheme operator language for the banking-gui asked by merchant the time after which the process will never ever end in a status OK RFC 1766 labgauge specification authetication data the creditors's 'user id from the registration process at the scheme operator the fingerprint calculated concatenating pin the signature when authenticating via xml dsig instead of fingerprint the creditor's user id from the registration process sha256 fingerprint the base structure for every mandate messsage the message header which contains the same data for each message in a specific process the unique process id, set by creditor creation time of the intitiation message the reference provided by SO for use in MandateServiceStatusRequest string restricted to base64-characters string restricted to hex-characters length limited http(s) uri