Skip to content

Updated field descriptions - #71

Open
deboragracio wants to merge 4 commits into
mainfrom
possystemapi-fields-update
Open

Updated field descriptions#71
deboragracio wants to merge 4 commits into
mainfrom
possystemapi-fields-update

Conversation

@deboragracio

Copy link
Copy Markdown
Collaborator
  • You've read the Contributor Guide and Code of Conduct.
  • You've included unit or integration tests for your change, where applicable.
  • You've included inline docs for your change, where applicable.
  • There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Description

More details on https://github.com/fiskaltrust/market-de/issues/413

@deboragracio
deboragracio requested a review from a team as a code owner July 28, 2026 14:16
| `ftPayItemCase` | `integer($uint64)` | 0 | false | Optional. Defines the type of payment related to **fiskaltrust** reference. For more information, see [ftPayItemCase](../../general/reference-tables/reference-tables.md#type-of-payment-ftpayitemcase). This field is relevant for **fiskaltrust.middleware** processing and represents a country-specific mapping. If not specified, the cash payment at the point of sale is used as a fallback. |
| `ftPayItemCaseData` | | | false | Optional. Provides additional details for defined type of payment related to **fiskaltrust** reference. |
| `Moment` | `string($date-time)` | null | true | Optional. The moment at which the payment was executed. It must be provided in UTC. The accumulated line items obtain the minimum (first) moment. If not provided, the `cbReceiptMoment` is used as fallback. Example: 2020-06-29T17:45:40.505Z. |
| `Position` | | | | Optional. Used to sort line items for receipt visualization. Line items are ordered in ascending order based on this value, with lower values appearing first.When multiple line items are accumulated into a single line item, the resulting line item inherits the lowest (first) Position value from the accumulated items. The `Position` field is interpreted as a flat ordering index. Although decimal values (e.g. `1.1`) may be accepted, they do not create grouping or hierarchical relationships between line items. Grouping behavior via decimal positions is not applied in the current digital receipt implementation. It uses `DecimalPrecisionMultiplier` as a discriminator between int64 and double values with a specific instruction/flag in `ftReceiptCase`. |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am still not sure what this accumulation of line items means exactly and whether our business logic supports this. Maybe @Tjark-fiskaltrust could say more about this?

@dima-pantelus dima-pantelus Aug 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have have discussed this issue with Tjark and he also couldn't find anything grouping- or accumulation-related in the code base. We suppose that this was just an idea in the past to introduce a grouping logic, however, most likely it didn't make it into a feature. Therefore, I would remove this sentence beginning with "When multiple line items are accumulated...".

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dima-pantelus thanks for checking! I just removed the sentence. Also, would you know the Position Data Type (either string or integer), default value (null or leave it in blank), and Nullable (either True or False)? cc @Tjark-fiskaltrust

Clarified the description of the 'Position' field in the data structures documentation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants