What this service does and does not promise about the codes it produces, the measurements it reports, and the destinations it resolves. Read alongside the terms of service, which governs where the two overlap.
The codes themselves
Every QR code and barcode this site produces is encoded from the values you enter, deterministically, in your browser. We do not check that those values are correct — a mistyped URL, a wrong Wi-Fi password or a transposed digit in a payment address encodes exactly as typed, and the resulting code is a faithful encoding of the wrong thing.
Check what a code contains before printing it, at the size you will print it. The scanner on this site decodes a code and shows you its payload, and that is the only check that tests the object rather than the intention.
Scanability reports are measurements, not certifications
The scanability checker measures properties of an image: contrast ratio, quiet zone, module size at a stated print width, and how much of the symbol a logo covers. Each is computed from the image you supply and from ISO/IEC 18004, and each is reported with the rule it was computed against.
A report that finds nothing wrong is not a promise that a code will scan. Scanning depends on the printer, the substrate, the ink, the lighting, the camera, the distance and the decoder — none of which the report can see. It tells you a code is not failing the things that can be measured, which is a smaller claim and the only honest one.
No overall score is shown. The bands that would turn these measurements into a number require a print-and-scan calibration study that has not been run, and a score presented before that study exists would be a number with nothing behind it.
Print sizes are arithmetic, not a guarantee
The print size calculator divides a printed width by the symbol's module count, including the four-module quiet zone the specification requires. That is division, and it is exact. What it does not know is whether a given camera can resolve the module size it produces.
Treat its output as a floor to design above rather than a threshold to design to, and test a printed proof at the distance your readers will actually stand.
Payment codes
We do not process, hold, transmit or settle any payment. A payment QR code encodes an address and, optionally, an amount, in the format the relevant scheme specifies. Whether a payment succeeds is between the payer, the payee and their institutions.
AI features never generate or modify an encoded payload. Where an assistant proposes values, a person confirms them and the payload is then built deterministically from what was confirmed. This is an architectural rule with a test, not a preference: a hallucinated payment address sends someone's money to a stranger.
Verify the payee name and address shown by your payment app before confirming, every time. A printed code can be covered by a sticker carrying somebody else's.
Destinations and dynamic codes
A dynamic code resolves through a short link whose destination is set by whoever made the code. We do not author, review or endorse those destinations, and a code resolving is not a statement that what it resolves to is safe, accurate or lawful.
Destinations are screened against threat intelligence and unsafe ones are refused, which is a defence rather than a warranty — screening lags, and a destination can change after it is checked. Report anything harmful through the abuse policy, which states the response times we hold ourselves to.
Availability
Static codes do not depend on this service at all. Once downloaded, a static code contains its own destination and will keep decoding whatever happens to us — which is the strongest availability statement on this page, and it is a property of the format rather than a commitment we are making.
Dynamic codes depend on the redirect service resolving. A printed code never stops resolving is an architectural rule here with a regression test per clause, and it covers downgrade, cancellation and exceeding a limit. It is not an uptime guarantee, and no uptime figure is published because none has been measured over a meaningful period.
What this site is not
Nothing here is legal, financial, tax, medical or regulatory advice. Several pages describe standards and statutes — ISO/IEC 18004, WCAG 2.2, DPDP 2023, GDPR — and those descriptions are written to be useful rather than to be relied on as compliance guidance for your own use.
- Third-party marks
- QR Code is a registered trademark of DENSO WAVE INCORPORATED. UPI, PIX, QRIS, Google Pay, PhonePe, PayPal and every other scheme or product named on this site belong to their owners. Naming a scheme we encode for is not a claim of affiliation, endorsement or certification by it.
- Standards references
- Where a figure is taken from a published standard, the standard is named beside it. Where a figure is ours, it says so, and where a figure would need a study we have not run, the page says that instead of giving one.
- Consumer rights
- Nothing on this page limits a right you have under law that cannot be limited by agreement. Where a clause here and such a right conflict, the right applies and the clause does not.
Who operates this service
- Operator
- Agochar Tech LLP, a limited liability partnership registered in India under the Limited Liability Partnership Act, 2008.
- Registered office
- 415 Decora Square, Sadhu Vasvani Road, Rajkot 360005, Gujarat, India
- Grievance officer
- Rajesh Dalsaniya, Grievance officer and CEO · [email protected] · +91 86986 76976. Complaints are acknowledged within 24 hours and resolved within 15 days.
- Governing law
- Governed by the laws of India; the courts at Rajkot, Gujarat, India have jurisdiction, subject to your rights as a consumer.
This document is in force from 1 November 2026. If we change it, the new version and its date appear here, and account holders are told before a material change takes effect.