IPIP and IPID scams sell a simple lie in technical clothing. A "sender" somewhere already has a very large amount of money. A "receiver" is needed to accept it, often by "IP to IP," "IPID," or "server to server." Screenshots and receipts are produced to show that the transfer is already in motion. Then you are told to pay a large upfront fee so the funds can be downloaded, cleared or completed. There are no funds. The fee is the point.
People who work in capital raising recognise this immediately. People who do not are asked to trust a vocabulary they have never seen on a real term sheet. That gap is the product.
Last reviewed: 13 November 2026.
What IPIP and IPID are claimed to be
In these pitches, IPIP is usually spoken as "IP to IP" or "IP/IP." IPID is used the same way, sometimes as "IP to ID," sometimes as a supposed protocol, sometimes as a sender code. You will also hear "S2S" or "server to server," "ledger to ledger," "bank server download," and "manual release." The labels change. The structure does not.
None of this is a standard, public payment rail with a rulebook you can read at your bank. Real banks do use IP networks, encrypted links, APIs and host-to-host connections. Those tools carry instructions and data. They do not create a secret corridor in which billions sit unseen until a private operator invoices you. For a longer demolition of the invented claims, see false claims about IPIP transfers. This article is about the fraud that uses those claims to collect a fee.
How the fake sender and receiver setup works
The pitch is staged like a closing. There is a sender, often described as a fund, a family office, a "top bank," or a private investor who already approved the amount. There is a receiver, which may be your company account, a special purpose vehicle, or an account the operator wants you to rent, open, or "assign." There may be a procedure list: pre-advice, readiness confirmation, server handshake, download window, then disbursement.
Documents are exchanged to make the theatre feel complete: a letter of intent, a readiness letter, a bank officer email, a receiver form, sometimes a drafted MT103 or a "conditional" transfer. You are told the money cannot move until the receiver is in place, or until a fee is paid to keep the sender "on the screen." If you ask to speak to the sending bank on a number you found yourself, the answers become vague. The officer is in a restricted room. The bank will not take inbound calls. The SWIFT copy should be enough.
That is not how a real payment is set up. A genuine sender is an institution you can identify, licensed in a known jurisdiction, acting for a disclosed principal, with a commercial reason to pay you. Your bank can, in a real transaction, look for an incoming payment or an authenticated message. It does not need a rented "IPIP receiver" costume to credit funds that have actually been sent.
A longer group-site briefing on these labels, including IPID, S2S and related claims, is here: IPIP, IPID, S2S and DTC transfer claims explained. The rest of this page stays on the sender-receiver fee mechanic.
Server-to-server claims, and why they sound convincing
Server-to-server language works because it is half familiar. Information technology really does move from server to server. Bank systems really do talk to each other. The scam takes that fact and pretends it is the settlement itself. "The funds are already on the server" is the key sentence. If you accept it, every later delay can be blamed on a technical step that only the operator can clear, for a price.
Settlement is not a file landing on a machine you cannot see. Settlement is a credit on the books of a financial institution that is responsible to you. Until your bank confirms that credit, or confirms that it has received an authenticated payment instruction it is prepared to act on, you have a story, not money.
Operators often staple an MT103 or MT760 copy onto an IPIP narrative, as if a message type could prove that a private server transfer is under way. We have already described the narrower document fraud on how the MT103 fund transfer scam works. The IPIP version is broader. It pretends to be a private bank-to-bank path that your relationship manager is not senior enough to see.
SWIFT is a provider of secure financial messaging services for its users. The FBI Internet Crime Complaint Center has warned that fraud actors use counterfeit SWIFT messages or documents, such as MT 799 or MT 760, to give scams an authentic look and to exploit gaps in technical knowledge. A forwarded copy, a screenshot, or a "server print" sent by the supposed sender is not that network. It is an attachment.
Fake receipts and the pressure that follows
The receipt is there to close your scepticism. It may show a time stamp, a reference, a BIC, a value date and an amount with more zeros than your last term sheet. It may be a photograph of a screen in a dark office. It may be a PDF with a bank logo. Logos are easy to copy. Credits are not.
The ICC Financial Investigation Bureau has documented fake guarantees and standbys that named institutions which did not exist or were unregulated, used names similar to real ones, and contained inconsistencies, invented terms and poor drafting. In one case, a purported one billion euro standby included release instructions and language that would not appear in a genuine instrument. Treat an IPIP receipt with the same suspicion. If the named bank is real, call the bank on a number from its official website. If the bank is not real, you already have your answer.
Then comes urgency. The download window is short. The sender will divert the funds. A compliance hold can be lifted only today. You may be told not to inform your own bank, or to sign a non-disclosure agreement first. The FBI has listed unnecessary secrecy, NDAs, and intricate excuses for missing funds among the common features of these schemes, together with the request for an advanced fee before funding.
The upfront fee, and the fact that there are no funds
The invoice is the business model. It may be called a download fee, a server fee, a pre-advice charge, a SWIFT cost, a tax, an insurance, a receiver activation, or a "one-time compliance clearance." It is paid to the operator or to an account the operator controls. It is not paid because your bank has asked for it in order to credit a genuine incoming payment.
The FBI's definition of an advance fee scheme is the right test. You are asked to pay money in anticipation of receiving something of greater value, such as a loan or investment, and you receive little or nothing in return. FinCEN has described the same family of fraud, including forged official papers that invent a fee as a condition of moving funds. RBI has cautioned that fictitious fund-transfer and remittance offers are used to extract processing or transfer charges, and that some operators falsely claim to be registered as NBFCs or other regulated firms.
If the funds were real and already launched, your bank would be the place to confirm them. Paying a third party does not cause a non-existent payment to settle. It only reduces the amount of money you still have.
This is also why a paid advisory retainer is a different discussion. A retainer, where it is used, pays for work on a real file: underwriting support, packaging, and a lender process, with no promise that funding is guaranteed. That distinction is set out on our page covering advance fee loan fraud versus retainer mandates. A download fee for an IPIP sender is not a retainer. It is a payment for a disbursement that will not happen.
Red flags in an IPIP or IPID pitch
| Signal | Why it matters |
|---|---|
| A sender you cannot independently identify is ready to send a very large amount, with little or no underwriting | Real funders do not skip credit work because a procedure list says "IPIP" |
| You must use a special receiver, rented account, or "IPIP-ready" structure before anything can be confirmed | The setup is being used to justify process and fees, not to complete a standard payment |
| Server-to-server, IP/IP, or hidden-terminal language is offered instead of a bank confirmation | Messaging and screenshots are being substituted for settlement |
| Fake or unverifiable receipts, MT copies or screenshots are treated as proof | Only your bank can confirm an authenticated message or a credit |
| A large upfront fee is required to download, activate, clear or complete the transfer | This is the advance-fee step. There are no funds to release |
| You are told not to call your own bank, or to sign an NDA and decide immediately | Independent checks would end the pitch |
If real lenders already declined the deal
The sender in these stories often appears after a string of rejections. That timing is not a compliment. If banks and investors have already refused the file, it is not an IPIP "sender" who has discovered that you deserve hundreds of millions without underwriting. Credit committees do not work that way. The companion article on what real investors and lenders actually do explains the process you should expect instead.
The related KTT version of the same fraud, usually built around telex language, NBFC providers and MT "downloads," is here: the KTT scam: fake downloads and upfront fees. Private placement and "platform" stories that travel with similar documents are covered in bullet trade, ping trade and SBLC private placement programs.
What to do instead
Do not pay the fee. Do not send further KYC packs to an unverified operator. Ask your own bank whether any payment or authenticated message has arrived. If you have already paid or handed over documents, contact the bank, keep the full file, report the matter to local law enforcement, and file a complaint with the FBI Internet Crime Complaint Center at www.ic3.gov.
If there is a real trade, project or acquisition, repair the file and take it through a genuine process. Financely is an advisor and arranger only, never a lender. We do not operate a secret IPIP rail, and we do not collect a fee to download funds that do not exist. To have a real transaction reviewed, request a free estimate or start your engagement.
Frequently asked questions
What are IPIP and IPID scams?
They are advance-fee frauds that pretend a large payment will move by "IP to IP," "IPIP," "IPID," or "server to server" between a designated sender and a designated receiver. The operator shows fake receipts or screenshots, then demands a fee to download or complete a transfer that does not exist.
What is the fake sender and receiver setup?
You are told that a specific "sender" already has billions, or access to them, and that a matching "receiver" account, sometimes at your bank and sometimes at a rented or offshore account, must be in place before the funds can move. The sender is not a verified institution making a real payment. The setup exists to make the paperwork look complete and to justify the fee.
Does server-to-server transfer mean the money is already in the bank?
No. Banks do use secure networks and host-to-host connections to send payment instructions. That is messaging and connectivity, not a hidden pile of money. A "server acknowledgement" or a screenshot of a terminal is not a credit to your account. Only your bank can confirm settlement.
Why do they ask for an upfront fee?
Because the fee is the scam. It may be described as a download charge, a SWIFT cost, a compliance clearance, a tax or a receiver activation. The promised funds are the bait. The FBI treats this as an advance-fee scheme: you pay in the hope of receiving something of much greater value, and you receive little or nothing.
How is this different from a real cross-border payment?
A real payment is sent by a known institution, on a standard rail, to an account in your name, and is confirmable by your own bank without a special fee paid to an intermediary. It follows KYC, sanctions checks and, if it is a loan or investment, underwriting. An IPIP "sender" who appears after every real lender has declined the file is not a substitute for that process.
