# Russia FNS Receipt QR

> Source: https://docs.barcoder.ai/docs/standards/russia-fns-receipt-qr
> research date 2026-10-30 · extracted at 2026-10-30
> Publisher: Barcoder — encyclopedia of QR, barcode and payment-code standards

Specifications:
- [Federal Law 54-FZ, Article 4.7: requirements for the cash receipt and strict-reporting form](https://www.consultant.ru/document/cons_doc_LAW_42359/7a607e9ee7058b0c3bcb22e564e88190964aee72/)
- [FNS Order ED-7-20/662@, Annex 2, paragraphs 14 and 15: QR string](https://www.consultant.ru/document/cons_doc_LAW_362322/be0c5f9845adc7d099a6538edd7604b2561f36dd/)
- [FNS Order ED-7-20/662@ of 14.09.2020 on the FNS site (original text and annexes)](https://www.nalog.gov.ru/rn77/about_fts/docs/10020801/)
- [FNS Order ED-7-20/236@ of 26.03.2025 (print and display requirements)](https://www.nalog.gov.ru/rn89/about_fts/docs/16421640/)

## Overview

The **FNS receipt QR code** is the two-dimensional code printed on Russian cash receipts and strict-reporting forms (БСО). Federal Law No. 54-FZ lists "QR-код" among the mandatory details of a receipt <sup>[1][1]</sup>, and an order of the Federal Tax Service (FNS, ФНС) sets the content <sup>[4][4]</sup>.

The payload is not a URL. It is a query-style text string of six fields, `t`, `s`, `fn`, `i`, `fp` and `n`, which together let the FNS checking software look up one fiscal document <sup>[4][4]</sup>. The fields carry the date and time, the amount, the fiscal drive's serial number, the fiscal document number, the fiscal sign and the type of settlement <sup>[4][4]</sup>.

## History

- **22 May 2003.** Federal Law No. 54-FZ, on the use of cash register equipment (ККТ) in settlements, is adopted. Its current edition was last amended by Law No. 158-FZ of 24 June 2025 <sup>[34][34]</sup> <sup>[1][1]</sup>.
- **3 July 2016.** Federal Law No. 290-FZ sets out the new cash register procedure <sup>[18][18]</sup>. Under it, registers send electronic copies of receipts to the tax authority online from 1 July 2017, and taxpayers on the ENVD and patent regimes follow from 1 July 2018 <sup>[17][17]</sup>.
- **21 March 2017.** FNS Order ММВ-7-20/229@ approves additional fiscal document details and formats <sup>[13][13]</sup>. An FNS page from October 2017 already says the register prints a QR code on the receipt <sup>[17][17]</sup>. The order's last edition, of 29 August 2019, carries the six-field string, the CP866 rule and the ban on URLs <sup>[13][13]</sup>.
- **3 July 2018.** Federal Law No. 192-FZ adds the QR code to the mandatory details of receipts and strict-reporting forms, as reported at the time by the accounting press <sup>[22][22]</sup>. ConsultantPlus gives 3 July as the day the law took effect <sup>[23][23]</sup>.
- **6 June 2019.** Federal Law No. 129-FZ adds receipts obtained by scanning a QR code shown on a screen, and gives them the same standing as paper or electronic receipts <sup>[24][24]</sup>.
- **1 February 2020.** The duty to show the code on vending machine displays applies, according to Garant's news summary of Article 1.2(5.1) as amended by Law 192-FZ <sup>[25][25]</sup>.
- **14 September 2020.** FNS Order ЕД-7-20/662@ cancels Order 229@ and its three amending orders, and introduces format version 1.2 (ФФД 1.2) <sup>[10][10]</sup> <sup>[14][14]</sup>. It was registered by the Ministry of Justice on 9 December 2020 under No. 61361 <sup>[10][10]</sup>.
- **26 March 2025.** FNS Order ЕД-7-20/236@ adds minimum print and display requirements for the code, in force from 1 September 2025 <sup>[11][11]</sup> <sup>[12][12]</sup>.

## Technical specification

### Symbol

The order defines the symbol as QR Code **Model 2**, at least **20 × 20 mm**, with error correction **L or higher** <sup>[5][5]</sup>. In the document model it is detail **tag 1196**, a text value that is printed but not stored as a TLV structure in the electronic document <sup>[6][6]</sup>. It must appear in its own separated area of the receipt <sup>[8][8]</sup>.

Order 236@ added these limits <sup>[12][12]</sup>:

| Medium | Size | Contrast | Other |
|---|---|---|---|
| Paper | at least 20 × 20 mm | at least 40 % | Must stay legible for at least 6 months from issue (Law 54-FZ, Article 4.7(8)) <sup>[1][1]</sup> |
| Display | at least 20 × 20 mm | 250:1 | Backlit screens at least 250 cd/m²; shown until the next settlement or for at least 40 seconds |

### Payload

Paragraph 15 of Annex 2 requires a text string of Latin letters, digits and the separators `=` and `&`, encoded in **CP866** <sup>[4][4]</sup>. CP866 is the DOS Cyrillic code page; its printable range 0x20–0x7E matches ASCII, so a conforming string has the same bytes in either encoding <sup>[32][32]</sup>.

| Field | Meaning | Format | Source tag |
|---|---|---|---|
| `t` | Date and time of settlement | `YYYYMMDDTHHMM`, no seconds | 1012 |
| `s` | Settlement amount | Roubles and kopecks, separated by a dot | 1020 |
| `fn` | Fiscal drive serial number | Tag value is 16 digits | 1041 |
| `i` | Fiscal document number | Decimal, not zero-padded; tag value is a UInt32 | 1040 |
| `fp` | Fiscal sign of the document | Decimal, not zero-padded | 1077 |
| `n` | Settlement type | 1, 2, 3 or 4 | 1054 |

The field list and formats are from paragraph 15 <sup>[4][4]</sup>; the tag properties are from the order's table of detail values <sup>[6][6]</sup>. The tag numbers beside the fields are this article's mapping by name, since paragraph 15 does not cite them.

- **`n` values:** 1 приход (receipt of funds), 2 возврат прихода (refund of a receipt), 3 расход (expenditure), 4 возврат расхода (refund of an expenditure) <sup>[7][7]</sup>.
- **`fp`:** tag 1077 is a 6-byte array. Only bytes 2–5 are printed, read as a big-endian UInt32 and shown in a 10-digit format <sup>[6][6]</sup> <sup>[9][9]</sup>. Law 54-FZ defines the fiscal sign as a value formed with the fiscal drive to check that fiscal data is reliable, and the drive as a sealed cryptographic device <sup>[2][2]</sup>. Annex 2 gives the byte layout but no derivation algorithm.
- **Literal `T`:** the format template in paragraph 15 is written in Russian (`ГГГГММДДТЧЧММ`, with a Cyrillic Т), but paragraph 15 allows only Latin letters and its sample uses a Latin `T` <sup>[9][9]</sup>.

The authority's own sample <sup>[4][4]</sup>:

```
t=20150720T1638&s=9999999.00&fn=000110000105&i=12345678&fp=123456&n=2
```

### No URL

Paragraph 14 of Annex 2 says the code on a **printed** receipt must not contain address data in URL format. It must instead allow the FNS receipt-checking software to verify the six details <sup>[4][4]</sup>. The string therefore points nowhere by itself; it needs software that knows the format.

### Size

The sample is 69 characters. Lowercase letters rule out alphanumeric mode, so it encodes in byte mode [[qr-ref]]. Computed with segno 1.6.6, with no error-level boost:

| Level | Version | Modules |
|---|---|---|
| L | 4 | 33 × 33 |
| M | 5 | 37 × 37 |
| Q | 6 | 41 × 41 |
| H | 8 | 49 × 49 |

At the minimum 20 mm, version 4 gives a module of about 0.6 mm (arithmetic from the figures above).

### When the code may be absent or moved

- **Correction receipts:** the code may be left off a correction receipt <sup>[9][9]</sup>.
- **Electronic receipts:** in the format versions 1.1 and 1.2 tables, tag 1196 is included when the receipt goes to the buyer's email, and may be included when it goes to a phone number <sup>[9][9]</sup>. This reading is from the order's original 2020 text on the FNS site.
- **Screen instead of paper:** Article 1.2(3.1) of the law lets a user meet the duty by showing the code on a device's display or printing it on a form. The buyer then scans it and collects the electronic receipt through the FNS service or app, free of charge <sup>[3][3]</sup>.
- **Other cases in the law:** Article 1.2 also refers to the code on automatic payment devices (5.1), for sales away from the place of settlement (5.7), and in paragraph 5.8 <sup>[3][3]</sup>.

## Verification

The buyer has two routes:

1. **Mobile app.** Scan the code, or enter the details by hand, to see whether the receipt reached the FNS <sup>[26][26]</sup> <sup>[27][27]</sup>. The app compares the data with the FNS revenue accounting system <sup>[18][18]</sup>. A receipt that passes shows "Чек корректен" <sup>[15][15]</sup>.
2. **Website.** The FNS service at kkt-online.nalog.ru takes the ФН, ФД and ФП values, the total and the date, and all fields must be filled in <sup>[19][19]</sup>.

Verification is a look-up against FNS records, not an offline signature check by the reader. The data reaches the FNS from the register through the fiscal drive and a fiscal data operator (ОФД) <sup>[17][17]</sup>. If a receipt is missing from the system, the buyer can file a complaint through the app with a photo of the paper receipt <sup>[21][21]</sup>.

## Use cases

- **Consumer checks.** Buyers confirm that a receipt was registered, and can report the seller when it was not <sup>[15][15]</sup> <sup>[21][21]</sup>.
- **Receipts without paper.** Under Article 1.2(3.1), a code on a screen or form replaces handing over a receipt, and the scan delivers the electronic one <sup>[3][3]</sup>.
- **Household records and tax deductions.** An FNS regional office describes the app as a place to store receipts, keep a family budget and use electronic receipts for tax deductions <sup>[20][20]</sup>.
- **Enforcement.** Issuing a document without the code, such as a card terminal slip in place of a receipt, or an incorrect receipt, is a violation under Part 2 of Article 14.5 of the Code of Administrative Offences, according to a 2019 FNS article <sup>[15][15]</sup>. A receipt missing any mandatory detail is treated as non-compliant <sup>[16][16]</sup>.
- **Software integrations.** Open-source clients parse the string to request receipt data from the FNS <sup>[28][28]</sup> <sup>[29][29]</sup>.

## Implementations

No reference implementation from the FNS was found, and the open-source parsers found are small and no longer active. Star counts and dates below were read from the repository pages.

| Repository | Language | Stars | Last commit | Notes |
|---|---|---|---|---|
| [kosov/fns-check](https://github.com/kosov/fns-check) | PHP | 29 | July 2020 | `FnsCheckHelper::fromQRCode` converts the string into request data. Archived on 31 July 2023 <sup>[29][29]</sup> |
| [spiritofsim/fns](https://github.com/spiritofsim/fns) | Go | 6 | January 2020 | `ParseQrStr` parses the string. MIT licence. Below the usual 10-star bar, kept because little else exists <sup>[28][28]</sup> |
| [sergelevin/pyofd](https://github.com/sergelevin/pyofd) | Python | 23 | December 2018 | Queries receipts from fiscal data operators by field values; its README does not cover QR parsing <sup>[30][30]</sup> |
| [zxing/zxing](https://github.com/zxing/zxing) | Java | 34,185 | October 2026 | General QR encoder and decoder; it has no knowledge of the format <sup>[31][31]</sup> [[url-ref]] |

No dedicated encoder library turned up. The string is short, so any QR library can carry it, set to Model 2 and error correction L or higher <sup>[5][5]</sup>.

## Comparison

| | FNS receipt QR | [Spain VeriFactu QR](https://docs.barcoder.ai/docs/standards/spain-verifactu-qr) | [SBP Universal QR](https://docs.barcoder.ai/docs/standards/sbp-universal-qr) | [Chestny ZNAK](https://docs.barcoder.ai/docs/standards/chestny-znak) |
|---|---|---|---|---|
| Purpose | Check one fiscal document | Validate one invoice with the tax agency | Pay | Mark one product |
| Payload | Six-field text string, not a URL | HTTPS URL on the agency's host | Payment QR on the SBP rail | Marking code |
| Seller ID in the code | No | Yes (`nif`) | Not compared | Not compared |
| Issuer | FNS | Spanish tax agency (AEAT) | NSPK under the Bank of Russia | CRPT |

The closest relative is VERI*FACTU, whose code is a URL with four parameters, `nif`, `numserie`, `fecha` and `importe` <sup>[33][33]</sup>. A URL can open in an ordinary browser, while the Russian code needs software that knows the format <sup>[4][4]</sup>. The Russian string identifies the document by fiscal drive and document number, and has no field for the seller's tax number <sup>[4][4]</sup>.

The other two Russian codes do different jobs. The SBP Universal QR starts a payment [[sbp-ref]], and a receipt code proves one afterwards. Chestny ZNAK codes identify individual goods [[cz-ref]], and format 1.2 was introduced in part to pass their data through the fiscal data operator and to require sellers to verify them with the register <sup>[14][14]</sup>. A choice between these formats does not arise, since each is required for its own purpose.

## Fun facts

- The authority's sample is dated **20 July 2015** and still appears unchanged in the 2025 edition of the order <sup>[4][4]</sup>. Its `fn` has 12 digits, although tag 1041 is fixed at 16 <sup>[6][6]</sup>, so the sample would not match a real drive number.
- The mandated character set dates from Russian MS-DOS 4.01 (1990) <sup>[32][32]</sup>, for a string that uses none of its Cyrillic characters <sup>[4][4]</sup>.

## Status

Active and mandatory. Article 4.7(1) of Law 54-FZ lists the QR code in the edition of 24 June 2025, in force from 2 September 2025 <sup>[1][1]</sup>. An organisation or sole proprietor must give the buyer a receipt or strict-reporting form that meets the article <sup>[16][16]</sup>.

Order ЕД-7-20/662@ applies in its edition of 8 December 2025 and is valid until **1 September 2031** <sup>[10][10]</sup>. Its amending orders are No. ЕД-7-20/239@ (12 April 2023), No. ЕД-7-20/1038@ (15 November 2024), No. ЕД-7-20/236@ (26 March 2025) and No. ЕД-7-20/1050@ (8 December 2025) <sup>[10][10]</sup>. Paragraphs 14 and 15 read the same in that edition as in the 2020 text <sup>[4][4]</sup> <sup>[9][9]</sup>. The order keeps format versions 1.05, 1.1 and 1.2 side by side <sup>[10][10]</sup>.

The FNS app is maintained by АО ГНИВЦ and was last updated on 6 October 2026 <sup>[26][26]</sup>. Its name varies between FNS pages: "Проверка чеков", "Проверка кассового чека" and "Проверка чеков ФНС России" <sup>[18][18]</sup> <sup>[20][20]</sup> <sup>[26][26]</sup>.

## Sources

[1]: https://www.consultant.ru/document/cons_doc_LAW_42359/7a607e9ee7058b0c3bcb22e564e88190964aee72/
[2]: https://www.consultant.ru/document/cons_doc_LAW_42359/a1b0f1c99aa2a3ab98dfb729163d3194973bdaee/
[3]: https://www.consultant.ru/document/cons_doc_LAW_42359/d2fc933bc5ec367e9a8713330510af5d9e1a3fe4/
[4]: https://www.consultant.ru/document/cons_doc_LAW_362322/be0c5f9845adc7d099a6538edd7604b2561f36dd/
[5]: https://www.consultant.ru/document/cons_doc_LAW_362322/0ca1f4a1abc08962fede832bd65a2c3f5b0141ca/
[6]: https://www.consultant.ru/document/cons_doc_LAW_362322/65751246d9560082321a07aa1003815e17375dec/
[7]: https://www.consultant.ru/document/cons_doc_LAW_362322/c3f6615226cb89c3d7f325ed9d064a64f45a481d/
[8]: https://www.consultant.ru/document/cons_doc_LAW_362322/a8ba391367e9d45ecb42df504a434417cb9aeb8d/
[9]: https://www.nalog.gov.ru/rn77/about_fts/docs/10020801/
[10]: https://www.consultant.ru/document/cons_doc_LAW_362322/2ff7a8c72de3994f30496a0ccbb1ddafdaddf518/
[11]: https://www.nalog.gov.ru/rn89/about_fts/docs/16421640/
[12]: https://www.nalog.gov.ru/html/sites/www.new.nalog.ru/files/about_fts/docs/16421640.docx
[13]: https://www.consultant.ru/document/cons_doc_LAW_214339/6111d2e938c6fe4df089424ce2fe9ef428678b1d/
[14]: https://www.nalog.gov.ru/rn77/news/activities_fts/10020885/
[15]: https://www.nalog.gov.ru/rn68/news/smi/9441211/
[16]: https://www.nalog.gov.ru/rn93/news/activities_fts/15188128/
[17]: https://www.nalog.gov.ru/rn13/news/tax_doc_news/7401690/
[18]: https://www.nalog.gov.ru/rn53/news/activities_fts/6954236/
[19]: https://www.nalog.gov.ru/rn16/news/activities_fts/13794780/
[20]: https://www.nalog.gov.ru/rn05/news/activities_fts/16545278/
[21]: https://www.nalog.gov.ru/rn61/news/activities_fts/16562612/
[22]: https://buh.ru/news/uchet_nalogi/70642/
[23]: https://www.consultant.ru/law/hotdocs/54184.html
[24]: https://buh.ru/news/uchet_nalogi/89871/
[25]: https://www.garant.ru/news/1324958/
[26]: https://www.rustore.ru/catalog/app/ru.fns.billchecker.mobile.android
[27]: https://apps.apple.com/ru/app/%D0%BF%D1%80%D0%BE%D0%B2%D0%B5%D1%80%D0%BA%D0%B0-%D1%87%D0%B5%D0%BA%D0%BE%D0%B2-%D1%84%D0%BD%D1%81-%D1%80%D0%BE%D1%81%D1%81%D0%B8%D0%B8/id1169353005?l=uk
[28]: https://github.com/spiritofsim/fns
[29]: https://github.com/kosov/fns-check
[30]: https://github.com/sergelevin/pyofd
[31]: https://github.com/zxing/zxing
[32]: https://en.wikipedia.org/wiki/Code_page_866
[33]: https://www.agenciatributaria.es/static_files/AEAT_Desarrolladores/EEDD/IVA/VERI-FACTU/DetalleEspecificacTecnCodigoQRfactura.pdf
[34]: https://www.consultant.ru/document/cons_doc_LAW_42359/
[qr-ref]: https://docs.barcoder.ai/source/standards/qr-code
[url-ref]: https://docs.barcoder.ai/source/standards/url-qr
[sbp-ref]: https://docs.barcoder.ai/source/standards/sbp-universal-qr
[cz-ref]: https://docs.barcoder.ai/source/standards/chestny-znak

[1] [Federal Law 54-FZ, Article 4.7: requirements for the cash receipt and strict-reporting form](https://www.consultant.ru/document/cons_doc_LAW_42359/7a607e9ee7058b0c3bcb22e564e88190964aee72/) — ConsultantPlus, edition of 24.06.2025, accessed 2026
[2] [Federal Law 54-FZ, Article 1.1: basic concepts](https://www.consultant.ru/document/cons_doc_LAW_42359/a1b0f1c99aa2a3ab98dfb729163d3194973bdaee/) — ConsultantPlus, edition of 24.06.2025, accessed 2026
[3] [Federal Law 54-FZ, Article 1.2: scope and rules for using cash register equipment](https://www.consultant.ru/document/cons_doc_LAW_42359/d2fc933bc5ec367e9a8713330510af5d9e1a3fe4/) — ConsultantPlus, edition of 24.06.2025, accessed 2026
[4] [FNS Order ЕД-7-20/662@, Annex 2, paragraphs 14 and 15 (page of Table 10)](https://www.consultant.ru/document/cons_doc_LAW_362322/be0c5f9845adc7d099a6538edd7604b2561f36dd/) — ConsultantPlus, edition of 08.12.2025, accessed 2026
[5] [FNS Order ЕД-7-20/662@, Annex 2, I. General provisions](https://www.consultant.ru/document/cons_doc_LAW_362322/0ca1f4a1abc08962fede832bd65a2c3f5b0141ca/) — ConsultantPlus, edition of 08.12.2025, accessed 2026
[6] [FNS Order ЕД-7-20/662@, Annex 2, Table 5: general values of fiscal document details](https://www.consultant.ru/document/cons_doc_LAW_362322/65751246d9560082321a07aa1003815e17375dec/) — ConsultantPlus, edition of 08.12.2025, accessed 2026
[7] [FNS Order ЕД-7-20/662@, Annex 2, Table 9: settlement type values (tag 1054)](https://www.consultant.ru/document/cons_doc_LAW_362322/c3f6615226cb89c3d7f325ed9d064a64f45a481d/) — ConsultantPlus, edition of 08.12.2025, accessed 2026
[8] [FNS Order ЕД-7-20/662@, Annex 2, Table 96: cash receipt in format 1.2](https://www.consultant.ru/document/cons_doc_LAW_362322/a8ba391367e9d45ecb42df504a434417cb9aeb8d/) — ConsultantPlus, edition of 08.12.2025, accessed 2026
[9] [Order of 14.09.2020 No. ЕД-7-20/662@, with Annex 2 as a DOCX download](https://www.nalog.gov.ru/rn77/about_fts/docs/10020801/) — Federal Tax Service of Russia, published 2020, accessed 2026
[10] [FNS Order ЕД-7-20/662@, operative text](https://www.consultant.ru/document/cons_doc_LAW_362322/2ff7a8c72de3994f30496a0ccbb1ddafdaddf518/) — ConsultantPlus, edition of 08.12.2025, accessed 2026
[11] [Order of the FNS of Russia of 26.03.2025 No. ЕД-7-20/236@](https://www.nalog.gov.ru/rn89/about_fts/docs/16421640/) — Federal Tax Service of Russia, published 27.06.2025, accessed 2026
[12] [Annex to Order ЕД-7-20/236@ (DOCX)](https://www.nalog.gov.ru/html/sites/www.new.nalog.ru/files/about_fts/docs/16421640.docx) — Federal Tax Service of Russia, 2025, accessed 2026
[13] [FNS Order ММВ-7-20/229@, Table 49 and its notes 61 and 62 (repealed)](https://www.consultant.ru/document/cons_doc_LAW_214339/6111d2e938c6fe4df089424ce2fe9ef428678b1d/) — ConsultantPlus, edition of 29.08.2019, accessed 2026
[14] [Additional details and new fiscal document formats approved](https://www.nalog.gov.ru/rn77/news/activities_fts/10020885/) — Federal Tax Service of Russia, 15.09.2020, accessed 2026
[15] [QR code: a mandatory detail of the cash receipt](https://www.nalog.gov.ru/rn68/news/smi/9441211/) — FNS regional office, reprint from Tambovskaya Zhizn, 24.12.2019, accessed 2026
[16] [What requirements apply to a cash receipt](https://www.nalog.gov.ru/rn93/news/activities_fts/15188128/) — FNS regional office, 02.09.2024 (archived page), accessed 2026
[17] [Online cash registers: how it all works](https://www.nalog.gov.ru/rn13/news/tax_doc_news/7401690/) — FNS regional office, 16.10.2017 (archived page), accessed 2026
[18] [Cash receipts can be checked on the FNS site](https://www.nalog.gov.ru/rn53/news/activities_fts/6954236/) — FNS regional office, 04.08.2017 (archived page), accessed 2026
[19] [An FNS service will help check a receipt](https://www.nalog.gov.ru/rn16/news/activities_fts/13794780/) — FNS regional office, 08.08.2023 (archived page), accessed 2026
[20] [The authenticity of a cash receipt can be checked online](https://www.nalog.gov.ru/rn05/news/activities_fts/16545278/) — FNS regional office, 12.09.2025 (archived page), accessed 2026
[21] [A cash receipt can be checked with a mobile app](https://www.nalog.gov.ru/rn61/news/activities_fts/16562612/) — FNS regional office, 27.10.2025 (archived page), accessed 2026
[22] [The list of mandatory cash receipt details has been extended](https://buh.ru/news/uchet_nalogi/70642/) — BUH.RU (third party), 11.07.2018, accessed 2026
[23] [The law clarifying the duty to use cash registers took effect on 3 July](https://www.consultant.ru/law/hotdocs/54184.html) — ConsultantPlus, 04.07.2018, accessed 2026
[24] [Buyers may support expenses with receipts obtained by QR code](https://buh.ru/news/uchet_nalogi/89871/) — BUH.RU (third party), 10.06.2019, accessed 2026
[25] [From 1 February the QR code must appear on a vending machine's display](https://www.garant.ru/news/1324958/) — Garant (third party), 03.02.2020, accessed 2026
[26] [Проверка чеков ФНС России](https://www.rustore.ru/catalog/app/ru.fns.billchecker.mobile.android) — RuStore listing, updated 06.10.2026, accessed 2026
[27] [Проверка чеков ФНС России](https://apps.apple.com/ru/app/%D0%BF%D1%80%D0%BE%D0%B2%D0%B5%D1%80%D0%BA%D0%B0-%D1%87%D0%B5%D0%BA%D0%BE%D0%B2-%D1%84%D0%BD%D1%81-%D1%80%D0%BE%D1%81%D1%81%D0%B8%D0%B8/id1169353005?l=uk) — App Store listing, accessed 2026
[28] [spiritofsim/fns](https://github.com/spiritofsim/fns) — GitHub, accessed 2026
[29] [kosov/fns-check](https://github.com/kosov/fns-check) — GitHub, accessed 2026
[30] [sergelevin/pyofd](https://github.com/sergelevin/pyofd) — GitHub, accessed 2026
[31] [zxing/zxing](https://github.com/zxing/zxing) — GitHub, accessed 2026
[32] [Code page 866](https://en.wikipedia.org/wiki/Code_page_866) — Wikipedia, accessed 2026
[33] [Detalle de las especificaciones técnicas del código QR de la factura](https://www.agenciatributaria.es/static_files/AEAT_Desarrolladores/EEDD/IVA/VERI-FACTU/DetalleEspecificacTecnCodigoQRfactura.pdf) — Agencia Tributaria, accessed 2026
[34] [Federal Law of 22.05.2003 No. 54-FZ](https://www.consultant.ru/document/cons_doc_LAW_42359/) — ConsultantPlus, accessed 2026

## Deployments

_No country reports mention this standard by name._