Disclaimer

This document is only collection of author’s notes, experiences and point of views. It is not, in any meaning, either complete description of the topic nor official RTB documentation. It may be inaccurate, incomplete, obsolete, misleading or completely wrong. It may even cause loss of data or damage system integrity. It may not comply with company codex, values, presentation style or economic interests or may reveal company secrets.

As such, it is absolutely prohibited to distribute this document outside of RTB & Co. GmbH. Such an act may result into legal acts against both the sender and the company. But it is allowed to use this document, after review of technical and presentational correctness and accuracy, as an information source for official documentation.

Always contact documentation department for information about current presentation style and allowed formats before creating customer’s documentation.

Integration

PDM calls the sale registration vis standard mechanism of real time requests. To easily distinguish request belonging sale register, their numbers starts from 1000. Be aware that only TCP connection is supported. Server does not listen on UDP.

Requests

Register on HR tax office (1000)

Input

Following menmonics are used to get information about payment:

  • WKZ - currency is ignored. Only value BET is taken to account.

  • DTM - date and time of payment in ISO_8601 format.

  • method - See java definition file. Enumeration starts from 0.

	/** Cash payment */
	CASH,
	/** Bank card payment */
	BANK_CARD,
	/** Checque payment */
	CHECQUE,
	/** Combination of defined payments. */
	OTHER

  • TIN - ticket number

  • offline - true means: This is delayed registration of sale. The parking ticket has been issued without online code from tax office. Offline security code has been used instead.

Output

Result is JSON with JIR and ZKI. It is contained in mnemonic MRQ.

Successfully registered payment
{jir:"111848e1-daf8-439a-b58d-1bd2c10bec0a",zki:"a381434f34276c62141d418d0d361de0",REQ:1000}

If registration fails there is no jir and zki in resulting JSON. Result may also contain Error Code (ECR) Error Text (ECT) to inform about reason of failure.

Following error codes can be returned

  • 1 - Request to tax office was successful However tax office responded by error.

  • 2 - Timeout. Tax office did not answered in expected time window.

  • 3 - Request to tax office failed. There may be something wrong with configuration or application itself.

  • 99 - Error which does not belong to any of categories above.

See mnemonic ECT for more information. Maximal length of ECT mnemonic is 300 characters.

Failed registration with error code 3
{ECR:3,ECT:"Something very bad happened", REQ:1000}

Register on SI tax office

It works in the same way as Croatian one. It is also accessible also under REQ 1000. Sale register decides, according to configuration, on which tax office the request is routed.

The only difference it that result is returned in eor and zoi.

Successfully registered payment
{eor:"111848e1-daf8-439a-b58d-1bd2c10bec0a",zoi:"a381434f34276c62141d418d0d361de0",REQ:1000}