> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/public-finance/v2.3/exemplar/mgramseva/user-manual/tech-user-manual/bluetooth-thermal-printer-integration.md).

# Bluetooth Thermal Printer Integration

Portable Bluetooth thermal printers are used to generate the mini receipts.

### Dependencies  <a href="#dependencies" id="dependencies"></a>

`bluetooth_thermal_printer`

`js`

![](https://2287351256-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FujRjzdG1LUqcmmuo2t2T%2Fuploads%2F2V0l5OxqIiiYV2CdFTW2%2Fimage-20220210-083823.png?alt=media\&token=542fbb80-6867-4c97-a1a7-9a5832587f3f)

### Printing Receipts via Bluetooth Thermal Printer  <a href="#printing-receipts-via-bluetooth-thermal-printer" id="printing-receipts-via-bluetooth-thermal-printer"></a>

* Enable the Bluetooth in the respective mobile device.
* Switch the thermal printer.
* Tap on the Print button from the respective screen if the printer device is connected already it will print the receipt directly or else it will show a dialogue with a list of Bluetooth devices, from their user need to a selected respective thermal printer, once the device is paired successfully it will generate a receipt in the printer.

### Helper Methods <a href="#helper-methods" id="helper-methods"></a>

* `printTicket` → Used to write the bytes to the thermal printer if the device is connected otherwise it will show paired Bluetooth devices in a dialogue.

  Required Arguments → bytes, context
* `getTicket` → Used to generate the bytes from Image and also sets the paper size.\
  Required Arguments → Image
* `showMyDialog` → Used to show the Paired Bluetooth devices\
  Required Arguments → bytes, context
* `setConnect` → If the device is already connected it will generate the receipt or else it will show the paired devices to connect.

### **Files Path**

[<img src="https://github.com/fluidicon.png" alt="" data-size="line">punjab-mgramseva/common\_printer.dart at master · misdwss/punjab-mgramseva](https://github.com/misdwss/punjab-mgramseva/blob/master/frontend/mgramseva/lib/utils/common_printer.dart)

[<img src="https://github.com/fluidicon.png" alt="" data-size="line">punjab-mgramseva/index.html at master · misdwss/punjab-mgramseva](https://github.com/misdwss/punjab-mgramseva/blob/master/frontend/mgramseva/web/index.html)

> [![Creative Commons License](https://i.creativecommons.org/l/by/4.0/80x15.png)*​*](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation*](https://egov.org.in/) *is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/public-finance/v2.3/exemplar/mgramseva/user-manual/tech-user-manual/bluetooth-thermal-printer-integration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
