1. The State Bank of Pakistan Raast QR Standard
Under the National Payment Systems Strategy, the State Bank of Pakistan (SBP) launched Raast as Pakistan's instant payment system. Raast QR codes comply with the international
EMVCo Merchant-Presented QR Code Specification using Tag-Length-Value (TLV) payload encoding.
A compliant static Raast QR payload contains structured data objects:
* Tag `00` (Payload Format Indicator): `01`
* Tag `01` (Point of Initiation Method): `11` for static or `12` for dynamic
* Tag `26` to `51` (Merchant Account Information): Contains the IBAN / Raast Alias, Member Bank Identifier, and sub-tags
* Tag `52` (Merchant Category Code): Standard 4-digit ISO 18245 code
* Tag `53` (Transaction Currency): `586` (PKR ISO code)
* Tag `58` (Country Code): `PK`
* Tag `63` (CRC-16/CCITT): Mandatory 4-character checksum calculated over all preceding characters
2. JazzCash & Easypaisa Merchant Integration
For informal micro-merchants and freelance service providers operating outside full Raast corporate acquiring:
*
JazzCash Till Format: Generates merchant payment strings routing directly to the 8-digit or 11-digit mobile account till identifier.
*
Easypaisa Format: Encodes merchant wallet numbers with transaction reference parameters for instantaneous P2M settlement.
All payment QR codes generated on QR Code Tools execute client-side with zero intermediary financial storage, ensuring full confidentiality for both merchant and consumer.
Putting this into practice
Start with the smallest real test you can run. Generate the code, print it at the exact size you plan to use, and scan it with two different phones in the lighting where it will live. Check that the destination page loads quickly on a mobile connection and that the call to action next to the code tells people what they will get. If anything feels slow or unclear, fix it before you print a full batch, because reprints cost more than a short test. Keep a note of the size, material, and placement that worked so the next batch starts from a proven setup.
Common mistakes to avoid
The most common mistakes are easy to avoid once you know them. Long payloads make modules tiny, low contrast makes edges hard to read, and text placed too close to the border eats the quiet zone the scanner needs. Covering a corner finder pattern with a logo or a sticker breaks detection entirely, and a code placed behind glare or on a curved surface fails even when the print is perfect. Review each of these points on a proof copy, and treat any failure as a reason to adjust the design rather than a reason to blame the scanner.
Quick checklist
- Keep the payload as short as practical so modules stay large.
- Keep dark modules on a light background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Test the printed code at the real viewing distance and lighting.
- Confirm the destination page loads fast on a phone.
- Recheck the code after any change to the link, design, or placement.
Related tools and guides
- For local payments, the [Pakistan payment QR](/pakistan-payment-qr) page explains the regional flow and what customers see.
- The [regional payment QR](/regional-payment-qr) guide covers payment codes used across different markets.
- The [UPI QR code generator](/upi-qr-code-generator) builds payment codes for UPI-based transfers.
- The [bulk generator](/bulk-generator) builds many codes from a table when one-off generation would take too long.
- Test every code with the [QR scanner](/qr-scanner) on more than one phone before you publish or print it.
- The [UTM builder](/utm-builder) adds campaign parameters so scans show up separately in your analytics.
