iChek Developer Guide
One account and one set of API keys for every iChek product.
Address API
Make sure every customer gives you a delivery address that actually works. iChek fills in city and state from the PIN code, catches wrong or incomplete addresses while the customer is still typing, and returns a clean, standardized address you can ship to.
Create a free accountTry the live demoQuick start
- Create an account. The free plan includes 1,000 checks a month.
- Open Install & settings in your dashboard. You get two keys:
pk_…is the publishable key. It's safe to put in web pages and is used by the widget.sk_…is the secret key. It's for your server only. Never put it in a web page or app.
- Pick how you connect:
You have… Use Coding needed Any website checkout (custom, Magento, OpenCart…) Checkout widget: one script tag Paste one line WooCommerce WordPress plugin None Your own backend or mobile app REST API A few lines A spreadsheet of existing addresses Bulk upload in the dashboard None - Before going live, add your website domain under Allowed website domains so your publishable key only works on your site.
Checkout widget
Paste this on your checkout or address page, just before </body>. Use your own publishable key:
<script src="https://api.ichek.info/widget.js" data-key="pk_YOUR_KEY" async></script>
That's all. The widget finds the address fields on the page by itself, including forms that appear later, like WooCommerce's. Then it:
- fills city and state as soon as a valid PIN code is typed (it works with text boxes and state drop-downs)
- checks the address when the customer leaves a field, and shows hints right under the address box
- offers a "Use this address" button with the cleaned-up version
- adds hidden fields to your form so your server receives the result:
ichek_status,ichek_score,ichek_check_id
Options
| Attribute | What it does |
|---|---|
data-block-invalid="true" | If the address is INVALID, the customer must fix it or click "Continue anyway" before the form submits. |
data-lang="hi" | Shows the widget's own labels in Hindi. |
data-auto="false" | Turns off auto-detection. Tell the widget your fields yourself (below). |
Point it at your fields (optional)
<script src="https://api.ichek.info/widget.js" data-key="pk_YOUR_KEY" data-auto="false"></script>
<script>
iChek.attach({
pincode: '#zip', city: '#city', state: '#state',
line1: '#address1', line2: '#address2', landmark: '#landmark', phone: '#phone',
onResult: function (r) { console.log(r.status, r.score, r.standardized.full); }
});
</script>
Every check also fires an ichek:result event on the form, with the result in event.detail.
WooCommerce plugin
- Download ichek-woocommerce.zip.
- In WordPress, go to Plugins → Add New → Upload Plugin, choose the zip, then Install and Activate.
- Go to WooCommerce → iChek and paste your publishable key. The iChek URL is already filled in. Click Save.
The widget now runs on your checkout and cart pages. Each order stores the address check result, which shows in the order screen under the shipping address.
REST API
| Base URL | https://api.ichek.info/api/v1 |
|---|---|
| Authentication | Header X-API-Key: sk_YOUR_SECRET_KEY |
| Format | JSON in, JSON out (UTF-8) |
| Interactive reference | https://api.ichek.info/docs (try calls in the browser) |
POST/address/verify
Checks one address and returns a score, the problems found, hints to show the customer and a standardized address.
| Field | Required | Description |
|---|---|---|
line1 | yes | House / flat number, building, street |
line2 | Area / locality | |
landmark | Nearby landmark | |
city | City / town (filled from the PIN if empty) | |
state | State name or code (KA, Karnataka…). Filled from the PIN if empty. | |
pincode | yes (India) | 6-digit PIN code |
phone | Mobile number. +91 and spaces are fine. | |
country | ISO code. Defaults to IN. Other countries get basic checks only. |
curl -X POST https://api.ichek.info/api/v1/address/verify \
-H "X-API-Key: sk_YOUR_SECRET_KEY" \
-H "Content-Type: application/json" \
-d '{"line1":"flat 204 lotus towers, 5th cross","line2":"indiranagar",
"city":"Bangalore","state":"KA","pincode":"560038","phone":"+91 98200 13457"}'
<?php
$ch = curl_init('https://api.ichek.info/api/v1/address/verify');
curl_setopt_array($ch, [
CURLOPT_POST => true,
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => ['X-API-Key: sk_YOUR_SECRET_KEY', 'Content-Type: application/json'],
CURLOPT_POSTFIELDS => json_encode([
'line1' => 'flat 204 lotus towers, 5th cross', 'line2' => 'indiranagar',
'city' => 'Bangalore', 'state' => 'KA', 'pincode' => '560038', 'phone' => '+91 98200 13457',
]),
]);
$r = json_decode(curl_exec($ch), true);
if ($r['status'] === 'INVALID') {
// ask the customer to fix: implode("\n", $r['suggestions'])
}
echo $r['standardized']['full'];
import requests
r = requests.post(
"https://api.ichek.info/api/v1/address/verify",
headers={"X-API-Key": "sk_YOUR_SECRET_KEY"},
json={"line1": "flat 204 lotus towers, 5th cross", "line2": "indiranagar",
"city": "Bangalore", "state": "KA", "pincode": "560038", "phone": "+91 98200 13457"},
timeout=10,
).json()
print(r["status"], r["score"], r["standardized"]["full"])
for hint in r["suggestions"]:
print("-", hint)
// Node 18+ (server side; never expose sk_ keys in the browser)
const res = await fetch("https://api.ichek.info/api/v1/address/verify", {
method: "POST",
headers: { "X-API-Key": "sk_YOUR_SECRET_KEY", "Content-Type": "application/json" },
body: JSON.stringify({ line1: "flat 204 lotus towers, 5th cross", line2: "indiranagar",
city: "Bangalore", state: "KA", pincode: "560038", phone: "+91 98200 13457" }),
});
const r = await res.json();
console.log(r.status, r.score, r.standardized.full);
Response: a good address
{
"score": 95,
"status": "VERIFIED",
"standardized": {
"line1": "Flat 204 Lotus Towers, 5th Cross",
"line2": "Indiranagar",
"landmark": "",
"city": "Bangalore",
"state": "Karnataka",
"pincode": "560038",
"country": "IN",
"full": "Flat 204 Lotus Towers, 5th Cross, Indiranagar, Bangalore, Karnataka 560038"
},
"issues": [
{ "code": "NO_LANDMARK", "severity": "info", "message": "No landmark given", "penalty": 5 }
],
"suggestions": [ "Add a nearby landmark (helps the courier)" ],
"pincode_info": { "pin": "560038", "found": true, "state": "Karnataka",
"districts": ["Bengaluru"], "offices": ["HAL II Stage", "Indiranagar"] },
"location": null,
"phone": "9820013457",
"phone_valid": true,
"country": "IN"
}
Response: an address that needs fixing ("line1": "near temple", "state": "Bihar", "pincode": "560038")
{
"score": 40,
"status": "INVALID",
"issues": [
{ "code": "STATE_PIN_MISMATCH", "severity": "error", "message": "PIN 560038 belongs to Karnataka, not Bihar", "penalty": 25 },
{ "code": "LINE_SHORT", "severity": "warn", "message": "Address is very short", "penalty": 20 },
{ "code": "NO_HOUSE_NO", "severity": "warn", "message": "No house / flat / plot number", "penalty": 15 }
],
"suggestions": [
"PIN and state don't match — is the PIN or the state wrong? (Karnataka)",
"Add building, street and area",
"Add house or flat number"
],
...
}
GET/pincode/{pin}
Looks up a PIN code and returns its state, districts and post offices. Useful for building your own auto-fill.
curl https://api.ichek.info/api/v1/pincode/560038 -H "X-API-Key: sk_YOUR_SECRET_KEY"
{ "pin": "560038", "valid_format": true, "found": true, "state": "Karnataka",
"districts": ["Bengaluru"], "offices": ["HAL II Stage", "Indiranagar"], "source": "api" }
found is false when the PIN doesn't exist. It is null when only the PIN's range could be checked, because the lookup service was unreachable.
Response fields
| Field | Meaning |
|---|---|
score | 0–100. Starts at 100, and each problem subtracts its penalty. |
status | VERIFIED (80+): ship it · NEEDS_REVIEW (50–79): show the hints · INVALID (<50): ask the customer to fix it |
standardized | The cleaned address: proper capitalization, abbreviations expanded (opp → Opposite, rd → Road), canonical state name, city/state filled from the PIN, and full as one line. |
issues[] | Each problem: code, severity (error / warn / info), message, penalty |
suggestions[] | Short, customer-friendly hints, ready to show on screen. |
pincode_info | What we know about the PIN code (state, districts, post offices). |
location | {lat, lon, precision} when available, otherwise null. |
phone, phone_valid | The normalized 10-digit mobile number, and whether it's a valid Indian mobile. |
Issue codes
| Code | Severity | Meaning |
|---|---|---|
PIN_MISSING / PIN_FORMAT | error | No PIN, or not 6 digits |
PIN_NOT_FOUND | error | The PIN doesn't exist in India Post records |
STATE_PIN_MISMATCH | error | The state doesn't match the PIN code |
JUNK_TEXT | error | Test or placeholder text ("test", "asdf", "xyz"…) |
LINE_MISSING | error | No street address |
CITY_PIN_MISMATCH | warn | The city isn't in the PIN code's area |
LINE_SHORT / LINE_FEW_WORDS | warn | The address is too short to find |
NO_HOUSE_NO | warn | No house / flat / plot number |
STATE_UNKNOWN, CITY_MISSING, PHONE_INVALID | warn | Unrecognized state, empty city, or invalid mobile |
NO_LANDMARK, STATE_FILLED, CITY_FILLED, PIN_UNVERIFIED | info | Hints and auto-fills |
GST at checkout: step by step
Ask shoppers for their GST number while they type their address, and check it on the spot. About 10 minutes, no coding on most stores.
- Create your account at the iChek Address API and log in. You get a publishable key (
pk_...) and a secret key (sk_...). - Open Install & settings. Under "Step 1 · Add the widget to your checkout" you will see one line of code.
- Tick the options you want under that line: "Check the GST number at checkout" and, if your checkout has no GST field, "Add a GST number box if my checkout has none". The line updates by itself.
- Press Copy and paste the line on your checkout / address page, just before
</body>. WooCommerce, Magento, OpenCart and custom sites: put it in the checkout template. Shopify does not allow scripts on its own checkout, so the widget works there only on cart pages and custom forms. - Add your website domain under "Allowed website domains" and press Save, so nobody else can use your key.
- Test it. Open your checkout. An optional "GST number" box appears with the address fields. Type a wrong number (for example
27AABCI0493D1ZV) and you get a hint. Type a real, active GSTIN and you get a tick and the registered company name, with a "Use this company name" button. - Go live. Watch "Usage this month" in the dashboard: it shows how many live GST look-ups you have used.
The box never blocks an order. If the GST service is busy or your monthly look-up limit is used up, the shopper still gets the format check and can place the order. To check a GSTIN from your own server instead, see below.
GST verification
Check a customer's GSTIN. The format and check-digit test is free and instant. When live look-up is switched on for the service, the same call also confirms that the GSTIN exists, whether it is active, and who it is registered to. Each live look-up counts against your plan's monthly GST limit (shown in your dashboard). Results are reused for 24 hours.
POST/gst/verify
curl -X POST https://api.ichek.info/api/v1/gst/verify \
-H "X-API-Key: sk_..." -H "Content-Type: application/json" \
-d '{"gstin":"27AABCI0493D1ZU","name":"iSec Services Pvt Ltd","pincode":"400102"}'
| Field | Meaning |
|---|---|
valid_format | false means a typing mistake (wrong length, state code or check character). reason says which. Nothing is charged. |
state, pan, taxpayer_type_from_pan | Read from the number itself. |
live_check | done, or not_enabled when only the format check is available. |
live | found, status (ACTIVE, CANCELLED, SUSPENDED), legal_name, trade_name, address, registration_date, taxpayer_type, constitution. |
match | Only if you send name and/or pincode: name.verdict MATCH / PARTIAL / MISMATCH and pincode.verdict. |
valid | true when the GSTIN is registered and ACTIVE. |
A 402 means this month's GST limit is used up. A 502 means the look-up service is unavailable; nothing is charged, so try again.
GST number at checkout (widget)
For B2B or GST-invoice checkouts, the widget can check the GSTIN while the shopper types it. Add data-gst="true" to the script tag and it uses your existing GST field (it finds fields named gst, gstin or "GST number"). If your checkout has none, add data-gst-add="true" and the widget adds an optional "GST number" box under the company field. The shopper sees a tick for a valid number, a hint for a typing mistake and, when live look-up is on, the registered company name with a "Use this company name" button. It never blocks the order. The widget calls POST /api/v1/public/gst/verify?pk=pk_..., limited to 40 look-ups an hour per visitor and to your allowed domains. Only live look-ups count against your GST limit.
<script src="https://api.ichek.info/widget.js" data-key="pk_..." data-gst="true" data-gst-add="true" async></script>
GST on orders (Pro)
When an order has a buyer's GST number, iChek compares it with the GST record and adds what it finds to the order's risk score and reasons. Send two optional fields with POST /api/v1/order/score:
{ "order_id": "A-1001", "phone": "9820013457", "line1": "...", "pincode": "560001", "state": "Karnataka",
"payment_method": "COD", "order_value": 12500,
"gstin": "27AABCI0493D1ZU", "company_name": "ISEC Services Pvt Ltd" }
Shopify and WooCommerce orders are read automatically: a GST number in the order notes, custom fields or billing company is picked up, and the billing / shipping company is used as company_name.
| What we find | Points | Holds the order in Hold mode |
|---|---|---|
| GST number is not valid (typing mistake) | +25 | No |
| Right format but not found in the GST records | +30 | Yes |
| Registration cancelled, suspended or inactive | +40 | Yes |
| Company name does not match the registered name | +25 (partly matches: +8) | Yes (partly: no) |
| Delivery state differs from the GST state | +12 | Only together with a PIN mismatch |
| Delivery PIN differs from the registered address | +5 | Only together with a state mismatch |
| Active registration and the name matches | −10 | No |
Choose how strict to be under Risk rules → GST number on orders, or with PUT /api/v1/gst/order-settings and {"mode": "off" | "flag" | "hold"}. Flag (default) lists the findings and adds points, but never sends an order to review because of GST alone. Hold sends it to the review queue, and the usual order.flagged alert goes to your webhook. Nothing is ever cancelled automatically. The order response and GET /api/v1/order/{id} include gstin and the reasons.
Each new GST number uses one live look-up (your allowance, then your prepaid pack). The same number again within 24 hours is free. If look-ups are not available, the state check still runs.
GST & OTP pricing
The format and check-digit test is always free and unlimited. Only a live look-up (is this GSTIN registered and active, and in whose name) is counted. The same GSTIN checked again within 24 hours is free.
| Plan | Live GST look-ups included each month | OTP messages included each month |
|---|---|---|
| Free | 5 | 25 |
| Pro | 200 | 1,000 |
| Business | 1,000 | 5,000 |
Need more? Buy a prepaid pack in Plan & billing at ₹3 per look-up plus GST: 100 for ₹300, 500 for ₹1,500 or 1,000 for ₹3,000. You pay with Razorpay (UPI, cards, net banking) and get a GST invoice by email. Packs do not expire. Each live look-up beyond your monthly allowance uses one look-up from your pack. If you have none left, the checkout box still checks the format and the shopper can still order. OTP SMS pricing beyond the included amount will be announced when the SMS service goes live.
Saved addresses with OTP
Let returning shoppers fill in their address by confirming an OTP sent to their mobile. Each store sees only the addresses it saved. Nothing is shown without the OTP. Switch it on in Install & settings, where you also confirm that your checkout tells shoppers their address will be saved.
- Save addresses. Either tick "save addresses from orders I score", or call the API after an order is placed (only with the shopper's agreement):
curl -X POST https://api.ichek.info/api/v1/saved-addresses \ -H "X-API-Key: sk_..." -H "Content-Type: application/json" \ -d '{"phone":"9820013457","name":"Priya Sharma","line1":"Flat 204, Lotus Towers", "line2":"Indiranagar","city":"Bengaluru","state":"Karnataka","pincode":"560038","consent":true}'A store keeps up to 5 addresses per mobile number.consentmust betrue. - Add the widget option.
<script src=".../widget.js" data-key="pk_..." data-otp="true" async></script>shows "Ordered here before? Fetch my saved address (OTP)" under the mobile field. The SMS goes out only when the shopper clicks it and only if the number has saved addresses. The reply looks the same either way, so nobody can find out whether a number is saved. - Forget a customer.
DELETE /api/v1/saved-addresses?phone=9820013457removes everything saved for that number.
An OTP is valid for 5 minutes with 5 tries. Sending is limited per number, per visitor and per day, and your plan includes a monthly number of OTP messages. Mobile numbers are stored only as a one-way hash.
Bulk CSV / Excel
In the dashboard, go to Bulk upload → Addresses and upload a .csv or .xlsx file of up to 5,000 rows. Column names are matched flexibly ("Pin Code", "Mobile", "Address 1", Shopify/WooCommerce exports…). You get a score, status, standardized address and hints for every row, and can download the results as CSV.
From code: POST /api/v1/bulk/verify with multipart fields file and mode=addresses.
Errors & limits
| HTTP | Meaning | What to do |
|---|---|---|
| 401 | Missing or wrong key | Check X-API-Key (server) or data-key (widget) |
| 402 | Monthly quota used up | Upgrade your plan, or wait for next month |
| 403 | Domain not allowed, or Pro feature | Add your domain in Settings, or upgrade to Pro |
| 429 | Too many requests from one IP (widget: 60 per minute) | Slow down and retry |
| 400 / 422 | Bad input | The response body says which field |
Identity verification (KYC)
Confirm that a customer is who they say they are, using a photo of their Aadhaar, PAN card, passport, driving licence or voter ID and a live selfie. iChek reads the card, checks the number rules, matches the selfie against the photo on the card and gives you a decision with the reasons. Every check records the customer's consent (time, IP address, device and, if allowed, location).
See what your customer sees: try the KYC demo with your own ID. Nothing is saved.
| Check | What it does |
|---|---|
| Document number | Aadhaar check digit (Verhoeff), PAN structure and holder type, passport MRZ check digits and expiry, driving licence and EPIC format |
| Aadhaar Secure QR | Reads the QR code on the card: name, date of birth and photo, signed by UIDAI. Only the last 4 digits of an Aadhaar number are stored. |
| Face match | Compares the live selfie with the photo on the card and returns a similarity score |
| Name & date of birth | Compares what's printed on the card with the name and DOB you send |
| Photo quality | Blur, glare and darkness. Customers are asked to retake bad photos before they submit. |
| Re-used documents | Warns if the same document was already used in another of your verifications |
Decisions: VERIFIED (all checks passed), REVIEW (a person should look: open it in the dashboard and Approve or Reject), FAILED (a critical check failed). After a review the status becomes APPROVED or REJECTED. Links that are never used become EXPIRED.
POST/kyc/sessions
The easiest way. Create a link, then send it to the customer by SMS, WhatsApp or email (the dashboard has buttons for this). The customer opens it on their phone, gives consent, photographs their ID with the camera and takes a selfie. No app to install.
| Field | Required | Description |
|---|---|---|
reference | Your customer or application ID | |
full_name | Name to match against the card | |
dob | Date of birth to match, YYYY-MM-DD | |
id_types | Documents the customer may use: aadhaar, pan, passport, dl, voter. Default: all. | |
purpose | Shown in the consent text, e.g. "opening your account" | |
phone, email | For your records | |
callback_url | Webhook for the result (otherwise the one in Settings is used) | |
redirect_url | Where the customer is sent when they finish | |
video | true adds a recorded video call with an agent after the photos (video KYC) |
curl -X POST https://api.ichek.info/api/v1/kyc/sessions \
-H "X-API-Key: sk_YOUR_SECRET_KEY" -H "Content-Type: application/json" \
-d '{"reference":"CUST-1042","full_name":"Asha Mehta","dob":"1990-04-12",
"id_types":["aadhaar","pan"],"purpose":"opening your account"}'
{"id":"kyc_3f9c…","status":"CREATED","url":"https://api.ichek.info/verify/Xb7…","expires_at":"…"}
Links work for 72 hours and can be used once. The customer gets 3 tries at the photos.
POST/kyc/verify
If your own app already captures the photos, send them directly as multipart/form-data. You must have collected the customer's consent and send consent=true.
| Field | Required | Description |
|---|---|---|
id_type | yes | aadhaar, pan, passport, dl or voter |
front | yes | Photo of the ID (JPG/PNG, up to 8 MB) |
back | Back of the card (Aadhaar QR is usually here) | |
selfie | Live photo of the customer, for face match | |
full_name, dob, id_number, reference | Details to match against the card | |
consent | yes | true |
curl -X POST https://api.ichek.info/api/v1/kyc/verify -H "X-API-Key: sk_YOUR_SECRET_KEY" \
-F id_type=pan -F consent=true -F full_name="Asha Mehta" \
-F front=@pan.jpg -F selfie=@selfie.jpg
Results & webhook
| Endpoint | Use |
|---|---|
GET/kyc/sessions/{id} | Full result: status, checks[] (code, label, pass/warn/fail, detail), extracted (details read from the card, such as number, name and DOB), face.similarity, consent record and history |
GET/kyc/sessions | List, with ?status=REVIEW or ?q= name / reference |
POST/kyc/sessions/{id}/review | {"decision":"APPROVED | REJECTED","note":"…"} |
GET/kyc/sessions/{id}/report.pdf | Verification report with photos, checks and consent, for your files |
GET/kyc/sessions/{id}/files/{front|back|selfie} | The photos (until they are deleted) |
DELETE/kyc/sessions/{id}/data | Delete the photos now, e.g. when a customer asks. The result and audit trail are kept. |
| Webhook | When a customer finishes, iChek POSTs {"event":"kyc.completed","data":{…}} to your callback URL, signed with X-iChek-Signature (HMAC-SHA256 of the body using your secret key). Always confirm with GET /kyc/sessions/{id} before acting. |
Video KYC with an agent
Create the link with "video": true. After the ID photo and selfie, the customer's status becomes VIDEO and the same link takes them to a video call: they join the queue when an agent is online during your working hours, or book a time (we email the booking and a reminder when you send their email). Calls are taken by your own team in the dashboard's agent console, or by the iChek team if that is switched on for your account.
On the call the agent sees the submitted photos, the automatic checks and the customer's live location; asks random questions (with the answers to check against), gives liveness instructions that appear on the customer's screen, and captures the face (compared with the selfie and ID photo) and the original ID / PAN held up to the camera (read and compared with the submitted number). Approval is only possible once the required checklist items, questions, captures and recording are in place. The whole call is recorded with a burnt-in time stamp, stored encrypted, and fingerprinted (SHA-256).
| Where | What you get |
|---|---|
GET /kyc/sessions/{id} | video_calls[]: status, decision (APPROVED / REJECTED / RESCHEDULE / DISCONNECTED), agent, times and duration, location and whether it is in India, questions with the agent's marks, liveness prompts, checklist, capture results and recording (size, SHA-256) |
GET/vkyc/calls/{call_id}/recording | The recording (WebM), with your key or dashboard login |
GET/vkyc/calls/{call_id}/captures/{face|doc|pan} | Frames the agent captured |
| Webhook | kyc.completed is sent after the call, with video_calls (decision, agent, duration, recording SHA-256) |
| Second check | If you switch on "second check" in Video KYC settings, a video approval goes to REVIEW until another person approves it with {"decision":"APPROVED","reviewer":"Name"} |
Free accounts include 10 identity checks and 2 video calls a month; paid plans include more. A check is counted when photos are submitted. Over the limit, the API returns 402.
RTO risk scoring PRO
For COD-heavy stores. Every order gets a risk level (LOW / REVIEW / HIGH) with reasons. The score uses address quality, COD vs prepaid, order value, the customer's past RTOs and failed deliveries, one phone used with many addresses (or one address with many phones), the PIN code's RTO rate and bursts of orders. Your team works a review queue (call, then Verify or Reject) before dispatch. Courier outcomes flow back, so the rules can be tuned from real results.
| Endpoint | Use |
|---|---|
POST/order/score | Address fields plus order_id, customer_name, payment_method (COD/PREPAID) and order_value. Returns risk_level, risk_score and risk_reasons. |
POST/order/outcome | {"order_id":"1001","outcome":"delivered | ndr | rto | cancelled"} |
POST/order/verify | {"order_id":"1001","action":"verified | rejected","note":"called customer"} |
GET/orders/risk | Orders waiting for a decision, highest risk first |
| Shopify / WooCommerce | No code: paste the webhook URL from your dashboard into your store's webhook settings, and every new order is scored automatically. |
| Alerts | Set a callback URL. REVIEW/HIGH orders are POSTed to it and signed with X-iChek-Signature (HMAC-SHA256 of the body using your secret key). |
Downloads
- WooCommerce plugin (zip)
- OpenAPI specification (import into Postman, Insomnia, or code generators)
- Sample addresses CSV for trying bulk upload
- widget.js (source, no dependencies)
PIN code data: India Post. Questions? Contact us through ichek.info.