How to verify a broker deposit automatically before the VIP group opens

To verify a broker deposit automatically, the software has to read the deposit from the broker's own records, not from the chat. The lead gives the email or account number they registered with, the tool looks it up in the broker's IB portal over a read-only API, and only a confirmed deposit opens the paid group. Scalegram is the Telegram CRM for IBs and forex affiliates that does exactly this: the bot asks for the email mid-conversation, checks it at the broker, approves the join request when the deposit is there, and files the result on the client card.

Why screenshots stopped being evidence

The old routine was manual. A lead writes "done, I deposited", attaches a screenshot of a broker dashboard, and the IB compares it with the portal by eye, then adds the person to the VIP group by hand. It worked at twenty leads a week. It stops working at two hundred, and it never worked against someone who wanted in for free.

A screenshot proves that an image exists. It does not prove that the account is under your referral, that the deposit cleared rather than sat pending, that the amount meets the minimum, or that the money was not withdrawn an hour later. Every one of those facts lives in the broker's back office, and none of them can be read off a picture.

A typed account number is no better. It can be real and belong to a client under another IB, or to an account with no deposit at all. What the customer says is a claim. The portal is the record. The question is how to get the record into the conversation without a human opening a browser tab.

What "verify a broker deposit automatically" needs from the broker

Most brokers give IBs a portal with the referred clients, their deposits and the commission owed, and some expose it over an API. The check is a lookup by email or account number that returns a few fields: does the account exist under this referral, has a deposit completed, how much and when. Prop firms are similar: the affiliate portal or the prop firm CRM can say which plan was bought, whether a funded account is live and whether KYC passed.

Three properties matter more than the field list.

The key is scoped to the IB

An affiliate-scoped key returns only the clients under that IB's link. "Is this email under me" becomes a plain yes or no, and a client under someone else's referral does not appear.

The connection is read-only

In Scalegram every call to the broker is a GET, and there is no code path that writes into the broker's system. The key is stored encrypted and never shown again after it is saved. A broker reviewing the integration can see that it cannot move a client, alter a payout or touch an account, which is often the difference between a key being issued and refused.

The check happens live

A nightly import of the client list is a report, not a verification. A deposit made ten minutes ago has to be found ten minutes later, or the person waits until morning and the IB is back to answering "did you check yet?" by hand.

The check inside the conversation

Here is the sequence Scalegram runs once the broker key is pasted under Integrations. The flow is drawn in the builder, so an IB can move steps or add a stop, but the shape is the same for every broker.

1. The lead asks about the paid group. The bot replies in the language the message arrived in, from the product knowledge and saved replies the IB gave it, and sends the broker link.
2. When the lead says the account is open, the bot asks for the email or account number they registered with.
3. The bot looks that email up in the broker's IB portal over the read-only API and answers from what the records say: account found or not, deposit completed or not, and the amount.
4. If the deposit meets the rule the IB set, the bot approves the join request to the paid group. If the account exists but the deposit is missing, it says so and queues a follow-up.
5. The client card is updated on its own: UID, email, broker, deposit and a dated note, with the stage moved to Deposited.

The IB reads the outcome in their own Telegram. The private chat with the bot is also a console, so "who deposited today" gets answered off the real records. The how it works section shows the same flow block by block.

Where an IB wants the last word, an Ask Me block stops the flow for a single yes or no tap: a stranger claiming a funded account, a deposit just under the minimum, a discount request. Everything not marked with an Ask Me block completes without the IB.

Opening the door: how Telegram join requests work

The "open the group" step relies on a Telegram feature from late 2021. Telegram's November 2021 update introduced invite links with admin approval: people who open one "will see a button to send a join request that admins can manage from a new bar at the top of the chat", and admins "can view an applicant's public profile pictures and bio, then approve or dismiss their request".

For a bot to do the approving, the Bot API documents an approveChatJoinRequest method: "The bot must be an administrator in the chat for this to work and must have the can_invite_users administrator right." The same page notes that a join request carries a user_chat_id, and the bot "can use this identifier for 5 minutes to send messages until the join request is processed", which is the window in which a bot can ask for the email right after someone knocks.

So the paid group runs on a request-to-join link instead of an open one. Every knock reaches the bot, the bot checks the deposit, and the approval is one API call. Nobody has to be awake, and a link that leaks in a forwarded message lets nobody in without that approval.

When the check comes back empty

Most failed checks are not fraud. The person registered with a different email, or the deposit is still pending at the payment provider, or they opened the account through a search ad instead of the IB's link and sit under no referral at all. The bot says which of those it can see, and comes back later.

Scalegram queues a follow-up to whoever went quiet and cancels it the moment they reply. An AI Follow Up block turns that into up to five nudges at widening gaps, each written from where the conversation stopped, and called off by the AI after a clear no. A lead who deposits on day three is checked and let in on day three.

The bot never hands out someone else's details. Every outgoing message is filtered before it leaves: API keys, the bot's own instructions in any wording, and any email or account number the conversation cannot account for are removed. Typing a stranger's email to see what happens returns nothing that belongs to the stranger.

When the payment is the proof instead

Not every Telegram seller has a broker in the middle. If the customer pays the seller directly for a channel, the payment receipt is the verification and a membership tool fits better. InviteMember describes itself on its home page as "Payments and membership management for subscription businesses", where "Members receive access right after payment. When the subscription ends, InviteMember removes access automatically", through gateways it says cover "credit/debit cards, crypto, or even cash".

That is the right shape for a subscription and the wrong one for an IB, because the IB's customer pays the broker, and no payment gateway can see a deposit made on a broker's platform. What is a Telegram CRM separates the kinds of tool in more detail.

The deposit as an ad event

Once the deposit is a verified fact rather than a claim, it can go back to the ad platform. Meta's Conversions API page describes a connection between an advertiser's marketing data, including "offline conversions", from "an advertiser's server, website platform, mobile app, or CRM to Meta systems that optimize ad targeting, decrease cost per result and measure outcomes", with server events "processed like events sent using the Meta Pixel".

Scalegram's tracked links carry the UTM tags and read fbclid, gclid, ttclid and sccid off the click, and joins are reported server side to Meta, TikTok and Snapchat. A verified deposit tied to the click that brought the person is a different signal from a click. Meta ads Telegram conversion tracking covers that side end to end.

Setting it up

Ask the broker's partner desk for a read-only IB portal API key scoped to your affiliate account. Paste the portal address and the key under Integrations, once. Switch the paid group's invite link to request-to-join and make the bot an administrator with the invite right. Draw the flow: trigger, questions, broker link, email request, lookup, grant, follow-up, and an Ask Me block wherever a tap is wanted. Lite at $99 a month covers one bot, one account and one link; the full plan at $999 a month removes the counts. The pricing section lists both.

If you are an IB or a forex affiliate and the group opens on a deposit at a broker, stop reading screenshots. Sign in, paste the broker key, and let the check run against the records. What else an IB has to track is in the IB CRM guide, and the account-based CRM behind it in Telegram CRM for IBs.

Sources

• Join Requests and more (November 2021 update), Telegram, checked 19 September 2026
• Telegram Bot API, Telegram, checked 19 September 2026
• InviteMember home page, InviteMember, checked 19 September 2026
• Conversions API, Meta, checked 19 September 2026

A deposit is verified when the broker's records say so. Anything the customer sends you is a claim, and the tool's job is to go and check.

— The Scalegram Team

Frequently asked questions