Just found it hard to believe that your best argument to the situation is that you were intoxicated. Spiked my skepticism.
Either way, nothing personal, I have good intent and that remains true regardless of the situation. I do want to genuinely wrap up the deal.
The confusion was that it wasn't actually generating. I understand that you would rather not get into technicalities and would rather an out of the box solution. But this specifically won't work here, because of the nature of some of these providers pricing models, I took it upon myself to do the following;
I have implemented into the tool all possible SMS providers, that I know of, that allow Telegram registrations. But it comes at a price, the numbers can be quite expensive.
I've already made a good deal at 400$, I wasn't looking to spend investments on numbers that I won't really use. That's mainly the reason I added a mock provider. It does the same thing flow wise, all except the part where it actually calls for a REAL 2FA code.
Flow remains; Per each providers documents: Buy number (API) > Telegram Request (1) > Check for code from Provider (API) > Code Received (API) > Telegram Request (2)
Way I built it, you get to try different providers (Knowing each implementation is following the providers documentation). What provider can't offer you, you pick a different one & move on. That way, you have control over your expanses and request to process completion margins.
But I simply cannot invest funds into numbers knowing the pricing models of these providers, that's why I offer to present the codebase as evidence.
If you still want a copy of the contract, I can share it.
@
life
![[Image: ShACnTx.jpeg]](https://i.imgur.com/ShACnTx.jpeg)