The transfer desk

Transfer partners, both directions

The whole graph, two ways in: pick your bank to see every program its points reach — or pick the program you want and see every Indian card that can feed it, best ratio first. 154 routes, every ratio in our-points : partner-miles.

Routes carry their own verification date — 151 of 154 (98%) name the document their ratio was last read out of, and when. The rest are on the T&C watchdog, which re-checks the issuer documents on rotation; an undated route says so rather than borrowing someone else's date.

Want ₹-value verdicts instead of raw ratios? The optimizer prices every route → Or see the whole network at once: the transfer map → — including every program-to-program direct door →

By bank — where can my points go?

By program — which card feeds it?

The long way round — no Indian card reaches these directly

25 programs have no direct card route from India at all. You get there by transferring through an intermediary — the aggregated end-to-end ratio, and whether it is worth it, is on each page.

How we time transfers

"I transferred three days ago and nothing has landed" is the sharpest question this desk gets, and the one place the rest of the field goes quiet: the only automated transfer-time collector in existence reads its users' linked loyalty accounts, which are overwhelmingly American and European, so it lists Indian routes and prints Unknown on every single one. We would rather say what we know and show our working.

Who says so — all 359 routes and hops

229 issuer-published The card issuer states this window in its own document.
23 programme-published The receiving programme states this window in its own document.
6 SLA + observed The issuer's published SLA, printed with the shorter time transfers actually take.
83 community-reported No issuer or programme publishes a window; a community grid is the only witness.
18 nobody publishes one We read the document. It states no credit window.

Every one of those links the document it came out of, dated to the day we read it — and that date is deliberately separate from the ratio's, because the two get re-read on different days and one date covering both would backdate one of them. Where nobody publishes a window, the row says so rather than borrowing a neighbour's number. Four rows lost an invented "7 working days" on 29 Aug 2026 for exactly that reason.

The desk's own stopwatch

An issuer publishes a ceiling, and a ceiling is not an answer: "up to 21 days" does not tell you whether to transfer on Sunday for a Tuesday booking. So we run the transfers ourselves and publish both timestamps. We have none yet, and that is the honest state of it — an observation is a claim that we watched a clock, and it cannot be derived from a document or reconstructed from a forum post. 12 routes are queued below.

What we will and will not print

Below 3 reports, no summary. The raw records render, dated, and nothing is averaged. Three is where a median starts meaning anything: at one report the "median" is the report, at two it is the mean of two and one bad reading drags it half way, and at three no single outlier can be the answer.
Above it, the estimate is pulled toward the published window. estimate = (n/(n+3))·observed + (3/(n+3))·published — so 3 completed transfers weigh exactly as much as the bank's own sentence. Fewer, and the bank's word still leads; more, and reality does. The raw median and the issuer's own words print beside it, never behind it.
Reports and contributors are always both printed — "7 reports · 4 contributors". At this scale the realistic failure is one enthusiast filing ten, and that sentence is what makes it visible instead of impressive.
A transfer that missed the published ceiling suppresses the shrinkage entirely. Pulling the estimate back under a promise the issuer has already been caught breaking would hide the one thing worth surfacing.
No fuzzing, no secret constants. Both numbers above are the real ones. Silence is printed as silence — a route with no data says so, and never looks like "instant".

The wanted list — 12 transfers we are queuing

Where a stopwatch would buy the most. A route earns a slot when our answer today is weak — a community grid, a ceiling wide enough to be useless, or nothing at all — and the route is one a lot of readers actually hold.

axis-edge-miles → Singapore Airlines KrisFlyer The richest route Atlas has and, per Axis's own per-partner table, among the slowest — "up to 10 working days", which is a fortnight in wall-clock time. Nothing tells a reader whether that ceiling is the real number or a lawyer's. The single most valuable stopwatch on the board.
hdfc-reward-points → Singapore Airlines KrisFlyer HDFC publishes no transfer window anywhere a reader can reach — every one of the 22 HDFC rows rests on a community grid. This is the most-held premium card in the country transferring into the most-wanted programme, and our answer is somebody else's table.
hdfc-reward-points → Air Canada Aeroplan Same blackout, and the community figure here is "24 hours" — the exact shape of claim that is either true and worth saying loudly or false and costing readers a booking.
sbi-travel-credits → Air Canada Aeroplan SBI's T&C §2(m) says "up to 21 days" and that clause covers all 26 SBI routes identically. A ceiling that wide is honest and nearly useless; one real transfer converts it into a number.
hsbc-reward-points → Singapore Airlines KrisFlyer HSBC is the only Indian issuer whose own page says "instantly or within 1 working day". If that holds, it is the fastest route in the country and should be famous; if it does not, we are repeating a marketing sentence.
amex-membership-rewards → Singapore Airlines KrisFlyer The only `mixed` block on the board — Amex's FAQ publishes a 3–5-working-day SLA while every community report says 1–3 days. Both are in the string because we cannot choose between them. A stopwatch chooses.
amex-membership-rewards → Marriott Bonvoy The 1:1 hotel route, and the one Amex row whose community figure ("24–48 hours") is materially faster than the airline rows. Worth confirming that the hotel side really is the quick one.
icici-reward-points → Air India Maharaja Club Air India's own page publishes 5 working days, but this is the only airline exit ICICI has and it is open to just two cards — a slow surprise here has nowhere else to go.
kotak-solitaire-air-miles → Etihad Guest Kotak publishes no window on any route — checked across all three ratio PDFs and the card page. A single observation here would be the only number that exists anywhere for this issuer.
rbl-nova-points → Singapore Airlines KrisFlyer Retracted to "not published" on 2026-08-29 when the desk's own extrapolation was caught. The honest blank is better than the invented seven days, and a stopwatch is the only thing that fills it.
aurum-reward-points → The British Airways Club (Avios) AURUM's transfer terms live behind a login on an Angular portal that serves an empty shell to every fetcher. The document is unreadable; the transfer is not.
marriott-bonvoy → Air Canada Aeroplan The busiest hop on the multi-hop router and the on-ramp for a dozen chains. "~5 days" is an aggregator's word, and every chain that runs through it inherits that uncertainty end to end.

Run one of these yourself? File it → — reader reports are published separately from this table, in their own tier, only in aggregate, and never as a source.