π The Global Indian Investor
Learn how to build a globally diversified portfolio from India. 7 of 12 chapters are live, covering LRS, FX, global indexes, and Irish ETFs.
FX Retail Booking Failed in BHIM But Amount Liened
On July 31, 2026, I attempted a routine forex purchase via the Bharat Connect/Forex option on the BHIM app β the same hybrid flow I’d already used successfully three times before. The UPI mandate went through, and the amount was liened. Nothing else happened: no deal confirmation, no failure message, no funds movement.
It took 11 days to remove the lien after an enormous number of follow-ups across the board.
That failure reshaped the month’s investment plan. With the lien still unresolved on August 7, I executed the domestic legs (Nifty 50, Midcap 150) and left Nasdaq 100 blocked β full numbers in State of the 1 Portfolio β August 2026. Once the lien cleared on Day 11, I moved straight to Bank of Baroda’s manual FX Retail flow, and the Nasdaq 100 leg was bought two days later, on August 13. That fallback carried its own surprise: an additional foreign bank charge I only discovered by using it.
Due to market movements and money being locked for 11 days, I’d already lost a significant growth opportunity β one that was gone for good regardless of how the lien resolved. How much, exactly, is below.
Why This Channel Has So Many Places to Fail
| Route | Parties in the Chain | Role of Each Party |
|---|---|---|
| Direct β bank’s own card rate, not FX Retail | Bank | Bank quotes its own rate and executes the remittance. No CCIL/FX Retail platform involved at all. |
| FX Retail Web | Bank + FX Retail (CCIL) | FX Retail (CCIL) handles rate discovery and deal booking on the CCIL web platform; the bank executes the wire against the booked deal. |
| FX Retail via Bharat Connect β App | Bank + FX Retail (CCIL) + Bharat Connect + a UPI app (BHIM, CRED, etc.) | A Bharat Connect-enabled UPI app β BHIM, in my case, though CRED and others also support it β surfaces the Forex option and initiates the UPI mandate; Bharat Connect routes the booking request; FX Retail (CCIL) does deal discovery and booking; the bank settles the actual remittance. |
Every extra party in that chain is a rate improvement when the flow works β it’s what let me combine a public-bank spread with private-bank execution speed. But it’s also one more organization with a legitimate claim that a failure “isn’t (only) their problem” when something breaks. My failure happened somewhere between BHIM and ICICI β and once it did, all four parties in that bottom row had somewhere else to point.
What I Actually Lost
Everything financial about this was eventually made whole:
- The principal β released in full after 11 days under lien.
- The investment itself β completed on August 13 via the Bank of Baroda fallback, at that day’s rate and price.
- The plan β this month’s drift correction still executed, just later and in two parts instead of one.
What didn’t come back is the July 31 entry itself β and unlike the lien, that’s something I can actually put a number on, by comparing what was planned on July 31 against what actually executed on August 12β13.
| Leg | Planned (Jul 31) | Actual | Move | Basis |
|---|---|---|---|---|
| USD/INR (booked rate) | βΉ95.6075 | βΉ95.515 | -0.0925 (9 paise cheaper) | Planned rate backed out of the mandate amount less this route’s standard ~10 paise/USD buffer, both figures kept out of this post. Actual is what the Bank of Baroda remittance booked on August 12. |
| ANAU per unit | $24.4689 | $25.8999 | +$1.4310 (+5.85%) | The Nasdaq 100 UCITS ETF (USD Acc) I invest through. Actual is the real August 13 fill. Because ANAU is exchange-traded, a fill tracks the previous day’s NAV β this one landed within half a cent of August 12’s. The planned side therefore uses July 30’s NAV, which keeps both ends on identical footing. |
The chart below covers the whole window, from the day before the attempt to the day the units were finally bought. The line is the RBI reference rate; the red dots are my own two bookings.
{
"title": { "text": "USD/INR β Mid-Market, FX Retail, and a Bank Card Rate", "left": "center", "textStyle": { "color": "#2c3e50", "fontSize": 15, "fontWeight": 600 } },
"tooltip": { "trigger": "axis" },
"legend": { "bottom": 0, "data": ["RBI Reference Rate", "My FX Retail Rate", "SBI TT Sell (card rate)"] },
"color": ["#2563EB", "#DC2626", "#F97316"],
"grid": { "left": "13%", "right": "6%", "top": "18%", "bottom": "17%" },
"xAxis": { "type": "category", "data": ["Jul 30","Jul 31","Aug 3","Aug 4","Aug 5","Aug 6","Aug 7","Aug 10","Aug 11","Aug 12","Aug 13","Aug 14"] },
"yAxis": { "type": "value", "scale": true, "name": "βΉ per USD", "nameLocation": "middle", "nameGap": 50 },
"series": [
{ "name": "RBI Reference Rate", "type": "line", "smooth": true, "data": [95.7327,95.3706,95.2601,95.3487,95.1237,95.2053,95.2135,95.2560,95.4321,95.4261,95.4098,95.4263] },
{ "name": "My FX Retail Rate", "type": "scatter", "symbolSize": 12, "data": [null,{ "value": 95.6075, "label": { "show": true, "position": "top", "formatter": "Attempted", "fontSize": 11, "fontWeight": 600, "color": "#334155" } },null,null,null,null,null,null,null,{ "value": 95.5150, "label": { "show": true, "position": "top", "formatter": "Executed", "fontSize": 11, "fontWeight": 600, "color": "#334155" } },null,null] },
{ "name": "SBI TT Sell (card rate)", "type": "line", "smooth": true, "lineStyle": { "type": "dashed" }, "data": [96.05,95.85,95.75,95.81,95.60,95.57,95.75,95.60,95.80,95.86,95.86,95.85] }
]
}My FX Retail bookings sit about midway between the mid-market benchmark and a bank card rate β roughly 24 paise above one and below the other β and the rupee itself barely moved across the episode, so the currency wasn’t what this cost me.
{
"title": { "text": "ANAU β Published NAV vs. My Entry Points", "left": "center", "textStyle": { "color": "#2c3e50", "fontSize": 15, "fontWeight": 600 } },
"tooltip": { "trigger": "axis" },
"legend": { "bottom": 0, "data": ["NAV (USD Acc)", "My Entry"] },
"color": ["#10B981", "#DC2626"],
"grid": { "left": "12%", "right": "6%", "top": "18%", "bottom": "17%" },
"xAxis": { "type": "category", "data": ["Jul 30","Jul 31","Aug 3","Aug 4","Aug 5","Aug 6","Aug 7","Aug 10","Aug 11","Aug 12","Aug 13"] },
"yAxis": { "type": "value", "scale": true, "name": "USD", "nameLocation": "middle", "nameGap": 45 },
"series": [
{ "name": "NAV (USD Acc)", "type": "line", "smooth": true, "data": [24.4689,24.6163,25.0537,25.8860,25.6722,25.5725,25.8763,25.7904,25.7065,25.8957,26.1935] },
{ "name": "My Entry", "type": "scatter", "symbolSize": 12, "data": [null,{ "value": 24.4689, "label": { "show": true, "position": "bottom", "formatter": "Planned", "fontSize": 11, "fontWeight": 600, "color": "#334155" } },null,null,null,null,null,null,null,null,{ "value": 25.8999, "label": { "show": true, "position": "bottom", "formatter": "Executed", "fontSize": 11, "fontWeight": 600, "color": "#334155" } }] }
]
}This is where the cost came from. The fund climbed almost without pause through the eleven days the money was frozen. Both red dots sit just under the NAV line, and deliberately so: an ANAU fill tracks the previous day’s NAV rather than the current one. The executed dot is the real August 13 fill, which landed within half a cent of August 12’s NAV; the planned dot applies the same rule to July 31 and sits at July 30’s NAV. Like against like.
Sources. Fund NAVs from AXA IM’s ANAU page; USD/INR mid-market from the RBI reference rate archive; SBI card rates from my own captured rate history. The two booked FX Retail rates and the August 13 fill price come from my own transaction records.
The FX leg moved in my favor by less than a tenth of a rupee per dollar β noise, in context. The fund leg didn’t: buying on August 13 instead of July 31 meant paying 5.85% more per unit for the exact same fund β net of the small FX offset, that works out to about 5.7% of whatever was actually invested that day. I’m keeping the exact amount out of this post, but here’s what that 5.7% means across a realistic range for a monthly tranche β each figure in the last column links into the RealValue SIP Engine, pre-filled with that row’s numbers:
| Amount Invested | Units of ANAU “Lost” | Value Lost (at Aug 13 price) | After 20 Years @ 20% | Same, in Today’s Money After Tax |
|---|---|---|---|---|
| βΉ1,00,000 | 2.3 | βΉ5,700 | βΉ2.19 L | βΉ58,200 |
| βΉ2,00,000 | 4.6 | βΉ11,500 | βΉ4.41 L | βΉ1.17 L |
| βΉ5,00,000 | 11.6 | βΉ28,700 | βΉ11.0 L | βΉ2.93 L |
| βΉ10,00,000 | 23.2 | βΉ57,500 | βΉ22.0 L | βΉ5.87 L |
The missing units don’t just stay missing β they stop compounding. The 20% isn’t a stretch: it’s roughly what this asset delivered to a rupee investor over the past two decades β the Nasdaq 100 compounded at about 15.2% in USD across 2006β2025, and the rupee gave up another ~3.8% a year against the dollar over the same stretch. At that rate a βΉ57,500 gap becomes about βΉ22 lakh over 20 years, or βΉ5.9 lakh in today’s money once discounted for 6% inflation and 15% tax.
To be clear about what that is: not a realised cash loss, and not a claim of permanent 5.7% underperformance. It’s the same rupees buying fewer units of the same fund, and no resolution buys back July 31’s price. The estimate I gave the bank on Day 7, written before I knew how the market would move, lands in the same range.
Money under lien is a recoverable state β released, usable, invested, eventually. A missed entry window isn’t. “Invest on July 31” and “invest on August 13” are two different trades, and once July 31 passes the first one no longer exists as an option. The 11 days and the runaround between four organizations both resolved. That month’s entry price didn’t.
Actions Taken & Responses
What follows is the full contact log β every email, call, branch visit, and reply β condensed into one table. Amounts and reference numbers are omitted throughout; timestamps and the substance of each message are not.
Before the detail, the shape of it β every contact I initiated, by day and channel:
{
"title": { "text": "What It Took: My Outbound Contacts by Day", "left": "center", "textStyle": { "color": "#2c3e50", "fontSize": 15, "fontWeight": 600 } },
"tooltip": { "trigger": "axis", "axisPointer": { "type": "shadow" } },
"legend": { "bottom": 0, "data": ["Email", "Call", "X", "X Chat", "Branch"] },
"color": ["#2563EB", "#F97316", "#DC2626", "#7C3AED", "#10B981"],
"grid": { "left": "10%", "right": "6%", "top": "18%", "bottom": "17%" },
"xAxis": { "type": "category", "data": ["D1","D2","D3","D4","D5","D6","D7","D8","D9","D10","D11","D12","D13"] },
"yAxis": { "type": "value", "name": "contacts", "nameLocation": "middle", "nameGap": 35, "minInterval": 1 },
"series": [
{ "name": "Email", "type": "bar", "stack": "t", "data": [1,1,0,4,3,1,1,1,0,0,3,0,2] },
{ "name": "Call", "type": "bar", "stack": "t", "data": [0,1,0,3,1,2,3,0,0,0,0,0,0] },
{ "name": "X", "type": "bar", "stack": "t", "data": [0,0,0,1,2,3,1,2,0,0,2,0,0] },
{ "name": "X Chat", "type": "bar", "stack": "t", "data": [0,0,0,1,1,0,1,1,0,0,0,0,0] },
{ "name": "Branch", "type": "bar", "stack": "t", "data": [0,0,0,1,0,0,0,0,0,0,0,0,0] }
]
}Forty-three contacts I had to initiate across thirteen days, on top of everything arriving the other way. The three empty bars are Sunday, Saturday and Sunday. The tallest is Day 4 β ten contacts on the day I was told to get an NOC from a UPI handle, and the day I went public. Effort then tapers while nothing moves, and Day 11, the day it actually cleared, took five. SMS appears nowhere because it only ever went one way: the mandate confirmation on Day 1 was the only one I got.
{
"title": {
"text": "When the Work Happened β Hour by Day",
"left": "center",
"textStyle": {
"color": "#2c3e50",
"fontSize": 15,
"fontWeight": 600
}
},
"tooltip": {
"position": "top",
"formatter": "{b}"
},
"grid": {
"left": "12%",
"right": "6%",
"top": "16%",
"bottom": "18%"
},
"xAxis": {
"type": "category",
"data": [
"D1",
"D2",
"D3",
"D4",
"D5",
"D6",
"D7",
"D8",
"D9",
"D10",
"D11",
"D12",
"D13"
],
"splitArea": {
"show": true
},
"axisTick": {
"show": false
}
},
"yAxis": {
"type": "category",
"inverse": true,
"data": [
"07:00",
"08:00",
"09:00",
"10:00",
"11:00",
"12:00",
"13:00",
"14:00",
"15:00",
"16:00",
"17:00",
"18:00",
"19:00",
"20:00",
"21:00"
],
"splitArea": {
"show": true
},
"axisTick": {
"show": false
}
},
"visualMap": {
"min": 1,
"max": 4,
"calculable": false,
"orient": "horizontal",
"left": "center",
"bottom": 0,
"text": [
"4 contacts",
"1"
],
"inRange": {
"color": [
"#dbeafe",
"#93c5fd",
"#3b82f6",
"#1d4ed8"
]
}
},
"series": [
{
"name": "Contacts",
"type": "heatmap",
"data": [
{
"value": [
0,
4,
1
],
"name": "Day 1, 11:00 β Email"
},
{
"value": [
1,
8,
2
],
"name": "Day 2, 15:00 β Call, Email"
},
{
"value": [
3,
4,
1
],
"name": "Day 4, 11:00 β Call"
},
{
"value": [
3,
5,
1
],
"name": "Day 4, 12:00 β Branch"
},
{
"value": [
3,
9,
4
],
"name": "Day 4, 16:00 β EmailΓ2, CallΓ2"
},
{
"value": [
3,
12,
3
],
"name": "Day 4, 19:00 β Email, X, X Chat"
},
{
"value": [
3,
14,
1
],
"name": "Day 4, 21:00 β Email"
},
{
"value": [
4,
1,
2
],
"name": "Day 5, 08:00 β Email, X"
},
{
"value": [
4,
5,
1
],
"name": "Day 5, 12:00 β X Chat"
},
{
"value": [
4,
9,
1
],
"name": "Day 5, 16:00 β Email"
},
{
"value": [
4,
10,
2
],
"name": "Day 5, 17:00 β X, Call"
},
{
"value": [
4,
11,
1
],
"name": "Day 5, 18:00 β Email"
},
{
"value": [
5,
4,
1
],
"name": "Day 6, 11:00 β Email"
},
{
"value": [
5,
5,
1
],
"name": "Day 6, 12:00 β X"
},
{
"value": [
5,
6,
2
],
"name": "Day 6, 13:00 β XΓ2"
},
{
"value": [
5,
10,
1
],
"name": "Day 6, 17:00 β Call"
},
{
"value": [
5,
11,
1
],
"name": "Day 6, 18:00 β Call"
},
{
"value": [
6,
3,
1
],
"name": "Day 7, 10:00 β X"
},
{
"value": [
6,
5,
1
],
"name": "Day 7, 12:00 β Call"
},
{
"value": [
6,
7,
1
],
"name": "Day 7, 14:00 β Call"
},
{
"value": [
6,
8,
2
],
"name": "Day 7, 15:00 β Email, X Chat"
},
{
"value": [
6,
10,
1
],
"name": "Day 7, 17:00 β Call"
},
{
"value": [
7,
0,
3
],
"name": "Day 8, 07:00 β X, X Chat, Email"
},
{
"value": [
7,
10,
1
],
"name": "Day 8, 17:00 β X"
},
{
"value": [
10,
3,
1
],
"name": "Day 11, 10:00 β Email"
},
{
"value": [
10,
4,
3
],
"name": "Day 11, 11:00 β Email, XΓ2"
},
{
"value": [
10,
9,
1
],
"name": "Day 11, 16:00 β Email"
},
{
"value": [
12,
6,
2
],
"name": "Day 13, 13:00 β EmailΓ2"
}
],
"label": {
"show": true,
"formatter": "{@[2]}",
"fontSize": 10,
"color": "#0f172a"
},
"itemStyle": {
"borderColor": "#fff",
"borderWidth": 2
},
"emphasis": {
"itemStyle": {
"shadowBlur": 6,
"shadowColor": "rgba(0,0,0,0.3)"
}
}
}
]
}Each square is an hour in which I had to do something. Empty means nothing from me β the three blank columns are weekends. The work clusters into two bands: late mornings and the 16:00β19:00 stretch after a working day, which is when most of this actually got done.
| Date/Time | Channel | From | To | Message |
|---|---|---|---|---|
Jul 31, FriDay 1 | ||||
| 11:23 | SMS | ICICI Bank | Me | "Your AutoPay mandate with ONETIME is successfully created towards Axis Bank from 31-Jul-26 to 31-Aug-26 for Rs. <redacted>, RRN <redacted> β ICICI Bank." β the same amount that would show up as the lien minutes later. |
| 11:36 | Me | BHIM Support / FX Retail (CCIL) | Reported it the same hour: "When I pressed Book, the UPI mandate went through and it liened the amount. But nothing happened further." And the part that mattered most β "Since the amount is liened I am not able to try again." | |
| 17:08 | BHIM Support | Me | "We request you to kindly contact your respective bank⦠Your bank will be able to check the details and provide the necessary support." The first handoff, on day one. | |
Aug 1, SatDay 2 | ||||
| 15:05 | Call | Me | ICICI (Customer Care) | Called ICICI, discussed multiple items; raised the lien issue and was asked to contact a nearby branch. |
| 15:51 | Me | ICICI (NRI / Customer Care) | Forwarded the BHIM thread with the lien screenshot and two questions: when the amount would be accessible again, and what caused the booking to fail so it could be avoided next time. Sending it to two ICICI desks opened two separate service requests on the same incident, which then ran in parallel and never converged. | |
Aug 2, SunDay 3 | ||||
| β | β | β | β | No response from any party; lien still in place. |
Aug 3, MonDay 4 | ||||
| 11:45 | Call | Me | Home branch DM | No answer. I'd waited two days hoping the lien would clear on its own; with the entire investment corpus blocked, I stopped waiting. |
| ~12:30 | Branch | Me | Nearby ICICI branch | Went in person instead. Said only that I was there about a lien, and waited for my turn. |
| 12:44 | Call | Home branch DM | Me | Called back while I was still waiting at the branch. He could see the lien but could not determine the reason for it, and said he'd escalate to the backend team. I left without taking it up with the branch, expecting it to be investigated. |
| 16:30 | ICICI (Wealth Management) | Me | Said the lien traced to "a notice from 296bbf4d299b4206b5a17b64029bf593@upi" β an anonymous, machine-generated UPI handle; asked me to obtain a clearance letter or NOC from that "authority" and submit it at the nearest branch with original photo ID. No process exists to obtain an NOC from a UPI handle. | |
| 16:42 | Me | BHIM / FX Retail / ICICI | Put all three on one thread and named the loop: "BHIM is asking me to reach the bank, and the bank is asking me to reach out to BHIM. How long will it take to remove the lien?" Noted three prior transactions through the same flow with no issues, and asked plainly: "Who is this 296bbf4d299b4206b5a17b64029bf593@upi?" | |
| 16:44 | ICICI (auto-reply) | Me | "We will assure you to respond within 1 business day." | |
| 16:44 | Call | Me | FX Retail (CCIL) | Called after the NOC email. They had no record of my Day 1 email at all. |
| 16:50 | Me | FX Retail (CCIL) | Resent the entire thread from the top, per that call. | |
| 16:54 | Call | Me | BHIM Support | Tried a couple of numbers found online. Couldn't reach anyone β BHIM has no phone line I could get through to. |
| 18:51 | ICICI (Customer Care) | Me | Said additional information was required; asked me to visit the nearest branch. "We have checked the details and require additional information to process your request." | |
| 19:12 | Me | ICICI (Customer Care) | Wrote back with everything I now knew and didn't know: the home branch DM couldn't explain the lien either, and "I have absolutely no clue who this authority is." Asked to be routed to the NRI/Money2World team that actually built the FX Retail Bharat Connect integration β "I don't think anyone else understands the issue here" β and noted the amount had been locked for no apparent reason. | |
| 19:27 | X | Me | @ICICIBank @ICICICare @NPCI_BHIM @NPCI_NPCI, cc @dilipasbe @RBI | Went public. Opened with "Need helpβ¦ Multiple lakhs of my funds have been under lien for several days after a transaction failed," then laid out the whole sequence over an eight-post thread: the same flow had worked multiple times before, the mandate succeeded but the booking never completed, and the reason given was a UPI handle nobody could identify. Thread β |
| 19:39 | X Chat | Me | BHIM Support | Sent the full case summary by DM β the flow, the successful mandate, the failed booking, and every desk contacted so far. |
| 19:52 | X Chat | BHIM Support | Me | "Please allow us some time as we are currently reviewing this." |
| 21:33 | Me | BHIM / FX Retail / ICICI | Did the investigation myself and sent the evidence: the AutoPay mandate SMS from Day 1, matching the lien in net banking to the paisa. "This AutoPay mandate was never executed due to a failure, yet the lien continues to remain on my account." Asked four specific questions β which entity holds the lien, the reason code behind it, the RRN's current status, and why it survived a failed execution. | |
| 21:35 | ICICI (auto-reply) | Me | Second automated reply of the day, this one noting "you have reached out to us multiple times" and promising "our expert team is reviewing them⦠You will hear from us shortly." The next substantive reply from ICICI came seven days later. | |
| 22:45 | ICICI (Wealth Management) | Me | Replied to the "who is this UPI handle" question by asking for four things about my branch visit: date, branch name, IFSC code, and the name of the employee I'd spoken with. Nothing about the lien. | |
Aug 4, TueDay 5 | ||||
| 08:46 | Me | ICICI (Wealth Management) | Wrote the whole sequence out end to end β the failed booking, the customer care call, the branch visit, the NOC email β and named what I thought the actual problem was: "there appears to be an integration gap between BHIM/FX Retail and ICICI Bank for this Bharat Connect/Forex transaction." Asked to be escalated to the team that owns Bharat Connect/UPI AutoPay and Forex, with a concrete timeline. | |
| 08:49 | ICICI (auto-reply) | Me | Three minutes later, the machine: "you have reached out to us multiple times⦠our expert team is reviewing them." | |
| 08:56 | X | Me | @UPI_NPCI, @ICICIBank_Care | Kept the thread alive: "In a multi party transaction when things goes wrong everyone asking to reach out to other." |
| 09:09 | BHIM Support | Me | "Please allow us some time as we are currently reviewing your details with our internal team. We will update you as soon as we have more information." | |
| 12:14 | X Chat | Me | Bharat Connect | Opened a second DM thread β sent the mandate SMS and a link to the public thread. |
| 15:13 | X Chat | Bharat Connect | Me | "We kindly request you to connect with the BHIM Support Team." |
| 16:30 | X Chat | BHIM Support | Me | "We kindly request you to contact your respective bank." |
| 16:31 | Me | BHIM Support | Replied to the morning's "allow us some time" with the only thing I wanted: "If i can get an update on when i will get further details/timeline for resolution that would be great." | |
| 17:38 | X | Me | Public post | Posted the loop as it actually was: Bharat Connect says contact BHIM, BHIM says contact ICICI, ICICI says get an NOC from the "Authority." "No one is really taking ownership to help the customer." |
| 17:56 | Call | Me | FX Retail (CCIL) | Second call. They forwarded the issue to the ICICI official who owns the system and said ICICI would reach out. |
| 18:19 | Me | FX Retail (CCIL) / BHIM / ICICI | Sent SMS and lien screenshots after the call above; shared account/customer IDs; asked for help. | |
| 18:24 | ICICI (auto-reply) | Me | Same template, second time today. | |
| 18:38 | FX Retail (CCIL) | Me | "We have forwarded your query to the concerned officials at ICICI Bank⦠The team will get in touch with you shortly." No one did. | |
| 19:19 | ICICI (Head Service Quality) | Me | A separate grievance ticket opened at the Head Service Quality office: "We shall update you with the status by August 10, 2026." Six days, for money that was already frozen. | |
Aug 5, WedDay 6 | ||||
| 11:49 | Me | FX Retail (CCIL) | Still nothing from the bank, money still liened. Said I'd check back the same evening if I hadn't heard from them. | |
| 12:15 | X | Me | @ICICIBank_Care | FX Retail had passed the case to the ICICI official who owns the system, and said ICICI would call. Nobody did. "Radio silence from customer care and wealth management email ids as well." |
| 13:11 | X | Me | @ICICIBank_Care | First time I put a rupee figure on it publicly β what not investing on 31 July had already cost me β and asked whether the bank would bear it, or at minimum give a timeline. |
| 13:23 | X | Me | @ICICIBank_Care | "Any timeline on when you will be able to give me a timeline to resolve this?" |
| 17:42, 18:24 | Call | Me | FX Retail (CCIL) | Third and fourth calls, and the first time the owner moved: FX Retail said the issue had to be resolved by the BHIM/NPCI team, and that NPCI officials had already passed it to BHIM. Day 4 it was ICICI's; Day 6 it was BHIM's. |
| 18:31 | Call | FX Retail (CCIL) | Me | Someone on the FX Retail team called me back on a direct line β the first time anyone in this whole chain rang me without being chased. |
Aug 6, ThuDay 7 | ||||
| 10:17 | X | Me | @ICICIBank_Care @NPCI_BHIM | FX Retail had now confirmed the issue "needs to be resolved by @NPCI_BHIM" β the third party to name a different owner. Asked them to expedite. |
| 12:08, 14:02 | Call | Me | FX Retail (CCIL) β direct line | Tried the direct line twice. The person assisting me was unavailable both times. |
| 15:38 | Me | BHIM / FX Retail / ICICI | New thread, subject line "Urgent Escalation: Day 7 β BHIM/FX Retail/Bharat Connect-Forex Lien Still Not Resolved." Relayed what FX Retail had said on the phone the day before, put the same rupee estimate of the lost investment opportunity in writing, and asked for a status and an expected timeline. | |
| 15:40 | BHIM Support (automated) | Me | Two minutes later, a brand new ticket β not the one opened on Day 1 β asking for my registered mobile number, transaction ID, and a screenshot of the error. All of it had already been sent, more than once. "Our team will review your request and get back to you within 24 hours." | |
| 15:41 | X Chat | Me | BHIM Support | Sent them the original ticket ID from Day 1 by DM, plus a link to the day's post, to stop the case fragmenting further. |
| 15:43 | ICICI (auto-reply) | Me | And the ICICI template, to close out five minutes in which one escalation produced a new ticket, a request for details already supplied, and two automated non-answers. | |
| 17:01 | Call | Me | FX Retail (CCIL) | Fifth call to the one desk that kept picking up. |
Aug 7, FriDay 8 | ||||
| 07:01 | X | Me | @ICICIBank @ICICICare @NPCI_BHIM @NPCI_NPCI @dilipasbe | A six-post thread reframing the whole thing: "This is no longer just a failed transaction. It is now a service deficiency arising from an end-to-end process failure, where the customer is left without ownership, communication, or a resolution timeline." Asked for two things only β current status, and a date. Thread β |
| 07:06 | X Chat | Me | BHIM Support | Forwarded that thread into the DM thread as well. |
| 07:37 | Me | BHIM / FX Retail / ICICI β seven desks, incl. Head of Service Quality and the Principal Nodal Officer | Went up the ladder. Subject: "Urgent Escalation β Day 8: Failed FX Retail/Bharat Connect Transaction Still Unresolved." Asked ICICI to assign one case owner to coordinate with BHIM/NPCI and FX Retail, since "as a customer, I should not be required to coordinate between multiple organizations to resolve a failed transaction." Requested three things β current status, expected release timeline, and the case owner's details β and said I'd otherwise take it to grievance redressal and regulatory channels. | |
| 07:41, 07:45 | ICICI (auto-reply) | Me | Writing to the Principal Nodal Officer unlocked a different template: "We acknowledge receipt of your email addressed to the higher authorityβ¦ your concern has been escalated to the appropriate teamβ¦ We request your patience while we examine the details." It arrived twice, four minutes apart, on two separate threads β one escalation, two parallel cases. Still automated, still no owner, still no date. | |
| 09:31 | Call | FX Retail (CCIL) | Me | They rang me, verified that the issue was still unresolved since 31 July, and looped in the ICICI team. |
| 09:40 | FX Retail (CCIL) | ICICI escalation team (cc: Me) | "Looping ICICI team for support. Please look into the below customer issue on priority." The platform operator escalating on my behalf, to a named ICICI contact. | |
| 17:17 | X | Me | @ICICIBank_Care | "Day 8 is also over. I have to keep posting this again over X, Email and calls on Day 11. π" |
Aug 8, SatDay 9 | ||||
| β | β | β | β | No response from any party; lien still in place. |
Aug 9, SunDay 10 | ||||
| β | β | β | β | No response from any party; lien still in place. |
Aug 10, MonDay 11 | ||||
| 10:19 | Me | ICICI (Wealth Management) | Resent the Day 7 escalation verbatim to the desk that had gone quiet since Day 4. | |
| 11:25 | Me | FX Retail / ICICI escalation desk (+ the same seven desks) | Same subject line, now reading "Day 11." Dropped the formal register: "I have been running behind so many emails/calls/branches/x." Narrowed everything down to two asks β remove the lien immediately, and confirm whether the BHIM/Bharat Connect Forex route is safe to try again β with a fallback: "At least do 1 today." | |
| 11:31, 11:35 | ICICI (auto-reply) | Me | The "higher authority" template, twice again, four minutes apart β the same doubling as Day 8. "We request your patience while we examine the details." | |
| 11:31 | X | Me | @ICICIBank_Care @NPCI_BHIM | "Day 11, issue is neither resolved nor a timeline provided for resolution." Said I'd be sending documentation of the loss. |
| 11:35 | X | Me | @ICICIBank_Care @bhim | Narrowed the ask to two lines: remove the lien, and confirm whether the BHIM/Bharat Connect Forex route is safe to try again. "At least do 1 today." |
| 11:36 | ICICI (escalation desk) | Me + BHIM + NPCI + internal ICICI | Eleven days in, the first straight answer from ICICI: "The lien has been marked by the BHIM team. We have raised this concern with the team." Sent to a wide list including an NPCI address, and tagging a named colleague for priority resolution. Note what this isn't β the NOC-from-a-UPI-handle instruction of Day 4 quietly stopped being the bank's position. | |
| 11:41 | ICICI (escalation desk) | Me + all | Five minutes later: "β¦would like to recall the message." The recall notice went to the same wide list, NPCI included. Outlook recalls don't work on external mailboxes, so the original stayed sitting in my inbox β all the recall achieved was telling all fourteen recipients β BHIM and NPCI among them β that ICICI wanted that sentence taken back. | |
| 13:15 | ICICI (auto-reply) | Me | The "you have reached out to us multiple times⦠You will hear from us shortly" template again, an hour and a half after the recall. | |
| 15:54 | Call | Home branch manager | Me | Explained the issue to him and passed on the email address of the backend team working on it. He asked me to call back if it wasn't resolved. |
| 16:12 | Me | ICICI (escalation desk) | Asked the only question the recall left me with: "Should I pursue further with the BHIM team or ICICI team is addressing/resolving this issue?" Then spelled out the relationship β a customer since 2009, across wealth, mutual funds, credit cards and securities, with the yearly domestic and international investments all routed through this account. | |
| 16:36 | ICICI (escalation desk) | Me | "The lien is being marked by the BHIM team. We are following up with BHIM team to get this resolved on priority. Kindly allow us sometime." Still no timeline, and no answer on whether I should keep chasing BHIM myself. | |
| 17:38 | ICICI (Head Service Quality) | Me | The grievance ticket came back on its promised date β closed, on the strength of that call. The branch manager "had spoken to you and we confirm that all your concerns related to account lien have been clarified." He had ended the call by telling me to ring back if it wasn't resolved. It wasn't: the lien was still on the account as I read the email. | |
| 18:12 | Call | ICICI (NRI team) | Me | Briefed me that they were actively working with the BHIM team, and that a further update would follow. It never did β no confirmation ever came from the bank that the lien was gone. |
| ~21:00 | App | Me | β | Lien released. Found it myself, checking the balance in Samsung Wallet, because nobody was going to tell me. |
Aug 11, TueDay 12 | ||||
| 14:01 | Call | FX Retail (CCIL) β direct line | Me | Rang to ask whether the issue had been resolved. I confirmed the lien was gone. The only party in the entire chain that followed up on its own to close the loop β and it was the platform operator, not the bank holding the money. |
| 18:11 | X Chat | Bharat Connect | Me | "The lien removal needs to be processed from the bank's end⦠We kindly request you to check with your bank." Arrived a full day after the lien had already been released. |
Aug 12, WedDay 13 | ||||
| 09:43 | ICICI (Wealth Management) | Me | Answered the Day 7 escalation, five days late and one account off: "As per our record, there is no lien mark in your account xxxx<redacted>." True, but that wasn't the account the lien had ever been on. | |
| 13:00 | BHIM Support | Me | Word for word the same message as Day 5, eight days later: "Please allow us some time as we are currently reviewing your details with our internal team." Different agent, same template, two days after the lien was gone. | |
| 13:01 | Me | BHIM Support | "Issue was resolved on 10 August 2026. Thank you." The customer closing the loop for the support team. | |
| 13:03 | Me | ICICI (Wealth Management) | Corrected the account and closed it out myself: "Issue has been resolved on 10 Aug 2026 on the account ending with <redacted>. You can close all related tickets auto created on various email/x." | |
| 13:05 | BHIM Support | Me | Closed the ticket, glad to hear "the lien amount against the forex purchased has been released" β describing a forex purchase that never happened. Thirteen days, and the closing message still had the transaction wrong. | |
| 13:09 | ICICI (auto-reply) | Me | The sixth firing of that same template in nine days β this time in response to me telling them the issue was already closed. "You will hear from us shortly." | |
| 13:57 | ICICI (Wealth Management) | Me | "Thank you for your confirmation. In case of future, if you face any problem we request you write back to us for serving you happier." The last message in thirteen days of correspondence, thanking me for confirming a resolution I had found myself. | |
Reflections
- An additional relationship bank is what let me stop waiting for an answer I was never given. It didn’t lift the lien any faster; it meant that when the money came back I could route around the flow that had just swallowed it. I asked repeatedly whether the BHIM/Bharat Connect route was safe to retry, and never got a reply.
- I picked the wrong door first. Two days after it cleared, I wrote: “I should have pursued FX Retail helpline rather than connecting with customer cares of ICICI/BHIM.” The generic customer-care desks at either end couldn’t see the transaction at all; the platform operator in the middle was the only party that could reach the people who could.
- Nobody could name an owner partly because, in their systems, there wasn’t one case to own. Every escalation spawned a new ticket rather than joining an existing one β two ICICI service requests, a second BHIM ticket asking again for details already supplied five times, and the nodal-officer address opening two parallel cases from one email, twice. Each desk was looking at a fragment, which is why the last thing I had to write was a request to “close all related tickets auto created on various email/x.”
Related Reading
- State of the 1 Portfolio β August 2026
- Bank of Baroda FX Retail for IBKR: From a βΉ0.10 Per USD Markup to an Additional Foreign Bank Charge
- FX Retail via Bharat Connect: Private Bank Speed at Public Bank Rates β A Live Transaction Walkthrough
- Chapter 4: FX Retail β A Deep Dive
Disclaimer
For educational purpose only
This post reflects my personal experience and is not investment or financial advice. Amounts and identifiers are redacted. The FX rates are the ones that applied to my own planned and executed transactions; the fund NAVs are published figures. I don’t have a confirmed root cause from BHIM, ICICI, or FX Retail, and your experience with this flow may differ from mine.