DE ♦ EN (Theano GmbH)  » Web Service  » Without SOAP

Forgot password?


New customer? Register


External uptime monitor:

Validating IBANs, Converting to IBANs, getting additional information

  • validate_iban: performs multiple checks, returns additional information such as SWIFT BIC, bank name, etc.
  • calculate_iban: converts BBAN to IBAN, performs multiple checks, returns additional information such as SWIFT BIC, bank name, etc.
  • find_bank: search the international bank code directory by bank name, bank code, country, and/or BIC.
  • qrcode: creates a QR code containing all information needed for a SEPA transfer. This QR code can be scanned by banking apps for easily entering a transfer. It is useful for printing on invoices.

Other REST endpoints

Documentation for the other REST endpoints will appear here soon. There will be REST equivalents for all SOAP functions.

Using the Web Interface without SOAP or REST

In case you don't like the idea of using SOAP or run into technical problems with it, but you still would like to use the web service, you can call exactly the same functions using an http or https interface. You send the values for SOAP parameters, along with the name of the desired function, to the following form, using GET or POST: (or without SSL:

The server will forward this request to the SOAP interface and respond with an XML file whose structure reflects that of the corresponding SOAP response. If you would like to have your request forwarded to a specific version of the SOAP interface, for instance the version, please specify the version (here: "12-2") by using the additional parameter "version", for instance by adding "&version=12-2" to your URL.

To use this http-based interface instead of the SOAP interface, please

  • refer to the documentation of the SOAP interface for the names of functions and their parameters, as well as the return values:
  • send requests to this URL, passing the parameters with GET or POST to fields whose names are the same as the parameter names in the calls to SOAP functions.
    For example, to calculate an IBAN, you could call:
  • Authentication: instead of sending your password in clear text as part of a URL, you can also send the MD5 value of the concatenation of the function name, your user name, the account number (value of the parameter "account" or "iban"), and your password. In the example above, assuming your password is "secret", the value for password would be md5("calculate_iban"."someusername"."648479930"."secret").
  • In addition to the parameters to SOAP functions, you also need to specify the function name using the parameter "function" (see the example above).
  • You can omit parameters whose values should be empty. In the example above, we omitted the parameters bic and legacy_mode since both are irrelevant for the country DE.

The following SOAP functions are currently supported by this wrapper:


  • calculate_iban. For authentication, send md5("calculate_iban".<username>.<domestic account number>.<secret>)
  • validate_iban. For authentication, send md5("validate_iban".<username>.<IBAN>.<secret>)
  • qrcode. For authentication, send md5("qrcode".<username>.<$recipient>.<iban>.<bic>.<amount>.<memo>.<label>.<secret>)
  • get_balance. For authentication, send md5("get_balance".<username>.<secret>)
  • find_bank. For authentication, send md5("find_bank".<username>.<search terms>.<secret>)
  • supported_countries. For authentication, send md5("supported_countries".<username>.<supported_condition>.<language>.<secret>)
  • validate_creditor_identifier. For authentication, send md5("validate_creditor_identifier".<username>.<creditor_identifier>.<secret>)
  • get_form. For authentication, send md5("get_form".<username>.<params>.<secret>); params should contain the complex data type in urlencoded JSON. For instance, if params contains the two parameters country and language, it could have the value {"country":"DE","language":1}, which would be urlencoded as %7B%22country%22%3A%22DE%22%2C%22language%22%3A1%7D. Overall, a call to this function could look like this:


Please also refer to the SOAP documentation.