Moment of Truth

The time has come to decide the way forward.

The past few weeks have been pretty rough - for the whole community. And even though we didn't create this reality deliberately, we take responsibility for it anyways.

You already know how we got here, so we'll skip to where we're at right now.

When we set up our Flutterwave integration, we made sure both payments and withdrawals were fully functional (so, yes, some people actually were paid via Flutterwave), at least on our end. The only issue was there was a cap - a limit on how much money we could transfer in a day. And that limit was really, really low. We also activated the option of having payments made to us stay in our Flutterwave account instead of being settled into our bank account. Just in case.

Enter the compliance review - once this began, withdrawals were completedly blocked. If the compliance review with Flutterwave went through, the limit and blocked would be removed and we wouldn't have to change a thing. So, essentially, the restriction on withdrawals was on Flutterwave's end, and no monies paid through Flutterwave ever got to us.

Unfortunately, it didn't, as we learned. And the only logical move was to have all payments made via Flutterwave refunded. We confirmed today that payments made via Bank Account, USSD, Mastercard and Visa have been refunded. Interswitch is working to make bulk refunds possible for payments made with Verve cards. And to be clear, Flutterwave is responsible for the refunds.

Why didn't we tell you immediately it happened? Partly because the Flutterwave support team beat us to it. Why they would directly communicate to you the outcome of our meeting without letting us break the ice we cannot say. Pressure from you, maybe? And partly because we were looking to find an alternative solution (of which we've made headway).

Why didn't we tell you what exactly we were going to do next? Well, we did last time, and look what happened. A house divided against itself cannot stand, and there's always the few who spoil it for the many.

It's a fact of life that no matter what you do, there's going to be someone who finds fault with it. And that's OK. Regular updates with no progress are pointless, and are usually colored by comments of buying time to make an escape. No updates means you get frantic and worried. We can't win that one.

We could have manually paid everyone due for withdrawals and temporarily closed the site for a month or two to work on the issues raised. But some of you subscribed with money from sources that won't permit that kind of delay. Why you would do that we don't know. But you did, and we've had to consider that.

What happens now?

Obviously, with each passing day, the amount we have to pay increases as more users are due for withdrawals, and the delayed response from Flutterwave just helped to exacerbate the problem. As we've received no monies from any sources whatsoever recently, our debts keep growing, while our bank balance stays the same. A recipe for disaster.

There's two ways we can remedy this, and only you can decide:

  1. Cleaning out the bank account to make refunds to as many users as we can (who paid via Paystack), then going home. (Recommended)
  2. Playing Kamikaze. Integrating with a gateway willing to give us breathing room to turn this around. Then paying everyone due for withdrawals with money in the bank, and monies from new subscriptions, until things even out. (Not recommended)

There is a poll at, and there you can vote, and make your voice heard.

This is a defining moment for all of us. And whatever you decide has to be overwhelming, and as a community. In other words, there must be a huge margin in the poll results. If the results are closely contested, and the margin small, we'll default to making refunds. Then we'll all go home.

Racksterly has always been about you - we are only custodians of a culture. It is now up to you to choose your own fate.

Whatever you decide, we will make happen.

Still Waiting

It's almost midnight, and there's been no word. This is to let you know we're waiting just as you are.

As promised, once there's feedback, you'll have it.

Moments Away

We've been in touch with the Flutterwave team throughout the week. And late last night, we had a final face-to-face with them.

We should have an official decision by the end of the day.

And please stop bombarding the Flutterwave team with emails. It's only made things more difficult for us - it's as though you're giving them a taste of things to come if they decide to work with us and something goes wrong, and this could make a big difference in whatever their decision turns out to be.

We'll let you know once we hear from them.

The situation of things

It can't be easy waiting so long, but that's where we're at. In this post, we'll be updating you on the exact situation of things.

Before that, however, let's fill you in on how we got here in the first place.

In previous posts we mentioned to you the status of our relationship with Paystack, and the conversations we were having with them. Now, we'll finish the story.

On the 25th of December, 2019, you may have noticed that most withdrawals were pending until late at night. At first (as always), we thought it was the usual bank issue. Turns out, it was because our transfers were put on hold, and when we reached out to the Paystack team about it, we were duly informed that the hold would not be taken off until we had spoken with the team, as they had given us time to work on "putting things together" before they closed our business on Paystack, and hadn't seen "much action" on our end. In truth, we wanted to keep using Paystack for payments, and had told them in an email a few days prior that we'd like to speak with them about the situation, in hopes that we could resolve whatever issues there were - an email we wrote and sent from the Paystack office in Lagos, where we'd gone to meet with them in person, and found that they were on a break and weren't available at the office.

A few hours later, we got to speak with a member of the Paystack team, where we mentioned that we were already working on our model, and needed some time. From the conversation, however, we learned they had received a lot of heat for being our payment gateway, especially during the downtime we had a few weeks back. Even before then, we had found that they were having to answer the question, "Is Racksterly a legitimate business?" incessantly - not a great position to be in (and the answer was "Yes", by the way). We were advised to make our request known on our email thread so the rest of the Paystack team could look at it, and make a decision. We did, and the hold was taken off, which explains why your withdrawals were completed late at night.

Our email went along the lines of:

"Thank you for the call.

When you mentioned in passing that your company was being called out for aiding a Ponzi scheme, everything made sense. We're really sorry about that. I know your team has worked hard for years to build Paystack into the company it now is, and we do not intend to jeopardize that in any way.

Since the incidence that led to our first phone call with your team, we've been working furiously on our model. Our current model doesn't look very good in the long term, and we want this to be sustainable. We deeply care about the people who use our service, and we want to make this work.

[Details about what we were doing behind the scenes here…]

Please give us 3 months to work this out. We know this means three more months of what you're already facing because of us. But we hope you'll give us the benefit of the doubt, and take a chance on us.

Thanks for being patient with us."

This was on the 25th. And we didn't get any replies to that email whatsoever. For days.

On the 30th, we found our transfers on hold again. Not one of our emails was replied to. When we saw that we weren't going to get a response, we proceeded to notify you by about 3am on the 31st. Not a great way to end the year, yeah?

We missed a call from the Paystack team by 11:03AM (on the 31st), and by the time we saw that, we found this email as well:

"Hi Ian,

Good morning and Happy holidays. Sincere apologies I've not responded to your previous email. I just called your number and got no response.

Regrettably, the decision to close your business still stands and this will be taking effect immediately. This is due to the current volatile nature of your business model and 3 months is a long time and in that time frame, anything can go wrong.

I've reached out to our finance team and because disputes can come from this decision we're taking, we'll be holding on to your pending settlements/balance for 2 weeks after which we'll be settling into your corporate bank account. I'll give you updates about this.

What you can do is create a new Paystack business when you do change your business model so we can review and activate accordingly.

Thank you for your understanding."

There it was. A reply, after 6 days of silence. No warning - just "this will be taking effect immediately". Sure, every business has a right to decide who they will or will not work with. That's just about the most classless way you can go about ending a working relationship. If 3 months was too long a period, they could have let us know to push ourselves harder to take a shorter period. If they were going to say "No" to our request, 6 days would have been enough time for us to set up an account with another gateway and test our implementation, so that a migration would simply come down to modifying a few files in a matter of minutes.

And what was that about holding on to monies paid to us through them (for days) for 2 weeks "because disputes can come from this decision".

Sidenote: For the uninitiated, when you go to your bank to complain about a payment you made and ask for your money back, that's a dispute.

So, not only were we left without a working gateway to receive or send money, they expected that we would fail as a result, and our users would want their money back. And their expectation gave them the right to hold on to our payments? This felt premeditated. Maybe, just maybe, we're wrong about this inference. But we're hard-pressed to see it any other way. When you do business with someone, it is important they have your best interests at heart, no matter what differences you may have along the way. And for a business we held in such high regard, we're sad to say that wasn't the case here.

We proceeded to inform you in one of our posts, and went dark while we moved to a different gateway. As you already know, we moved to Flutterwave's Ravepay. And we informed you that we were all waiting for their compliance team to complete their checks. Well, we got a notification email from their team saying they were restricting withdrawals/transfers due to flags thrown by their fraud monitoring system and inviting us for a meeting on Wednesday, 08 January 2020. What flags could have been thrown we do not know, and they didn't say. Maybe it was the large number of transactions on a first day. Your guess is as good as ours.

Every day you have to wait is torture from all the suspense, and we replied that we could have a voice or video call over the internet instead, to answer whatever questions they may have, as the date was really far away. When we didn't get a response by midnight last night, we left for their office in Lagos, but could only meet the support team as the compliance team wasn't and wouldn't be available until next week.

We knew they hadn't seen our email when we received an email a few hours ago which included the line: "Checking in to confirm you received our email". We've replied to them, and now, we continue to wait. In case you're wondering why this is taking so long, think of compliance checks as due diligence performed when you go to open a corporate account at a bank. Your bank needs to make certain everything is in order.

However this turns out, we'll let you know. We understand this is difficult for you, but rest assured, we're seeing this through to the end.

We're here for you. Always.

Half A Jiffy

Hello Fam,

We've switched to Flutterwave, and as of this moment, all implementations (payments and transfers) are complete. You probably already know this as you were able to make payments yesterday.

As it stands ,however, Flutterwave is carrying out compliance checks on our business before we can be fully operational, so, for now, payments and transfers are temporarily inactive. This means we're now waiting just as you are.

What this also means is if you made a payment and are yet to receive value, that's because we/our servers are unable to verify the transaction status or do pretty much anything else for the duration of the compliance checks, and you only need wait. Same goes for withdrawals.

We'll let you know how this pans out. Your patience is deeply appreciated.

Damage Control

We received an email from Paystack a moment ago.

We're migrating our payments integration elsewhere as we speak, so we'll need a bit of time. Please be patient.

Once we're done, we'll let you know, and give you the full gist as to what happened - you won't fucking believe this.

We've got a situation

We have a responsibility to you to let you know when stuff happens behind the scenes that could affect your experience, no matter what it is. And to be truthful about it.

Most of the withdrawals from yesterday were completed successfully. However, from about we're-not-exactly-sure-when yesterday, our transfers on Paystack were put on hold. Your emails alerted us to the situation, even though at first we thought the banks' servers had something to do with it.

Periodically, Paystack's automated systems put businesses' transfers on hold when certain transaction limits are exceeded. Then, the business's managers are required to send an email to notify Paystack of the situation so they can manually review the account and remove the hold. This happens once in a while with us, and it usually doesn't take more than a few hours for the hold to be lifted. But not this time. And we're not entirely sure our transfers are on hold this time for the usual reasons.

We've sent an email. Four, in fact. And there's been no response. Throughout yesterday up until now. So we can't even say what exactly is causing the situation. It may not be unrelated to what we mentioned to you in our last update, though.

Now, a bit of what's been happening lately.

It's obvious to anyone who cares to peer into the future that our model requires some serious tweaking if we intend to stand the test of time. The current model works, for now, but ensuring longevity is something we owe to you who have trusted us. Paystack brought this up as an issue, and we asked for time to work things out, even though we're yet to get a response. We've been on it since our last update, which is why this page has been a bit quiet on our end. There's a lot to do, and little to say. Unfortunately, some things just take time.

At this point in time, there isn't much we can do but wait for a response from Paystack. We'll let you know once we receive one. Hopefully, a positive one.

We're really sorry to those whose withdrawals are still pending. You can be sure you'll receive your money as soon as we make headway.


PS: We understand that you find these holds increasingly frustrating. It is important, however, that you understand Paystack is only trying to ensure your money is safe (even though there are certainly not-so-inconvenient ways they could have gone about it), so do not go flooding their support channels to force their hand. Let's give them time to come to a decision, so we can resolve this once and for all.


TL;DR: We're fully back. And something about the updates.

Hello Fam,

We've missed you.

It's been a rough ride these past few days. In the Racksterly way, we'll be going over recent events, where we are now, and where we're going, telling it like it is. Now strap in, it's storytime.

Let's start with a story about why we closed our site for 3 days for maintenance?

Would you be surprised if we told you we didn't? We bet you would. But, we really didn't. Now get comfortable, this one's a freight train.

We knew there was trouble in paradise when we started receiving emails from several users by the hour on the 11th, saying they weren't paid for sharing, or they made a payment and still had the transaction pending, or even worse, got the much dreaded, "This site can't be reached" message on their browsers. Some smart browsers like Chrome provided additional information like, "racksterly. co took too long to respond". Now, a trained eye can tell all of these were symptoms of an unresponsive/overloaded web server. Or were they?

We knew we were in dire straits when, by midday, even we couldn't reach our website. What could be the problem? We had already gotten the biggest, and most powerful server Namecheap had.

Starting midday, we got in touch with Namecheap. Asked for certain configuration changes. DDOS again, maybe? But we already had Cloudflare set up. Maybe it was a false positive - Cloudflare may have mistaken the traffic from our users for a DOS attack and throttled traffic. But, we figured, it wasn't like Cloudflare to make such a mistake, and even the stats looked good. No matter, we tweaked the config anyway. Then, we relaxed mod_security on the web server. We did everything we possibly could to speed up the server. Every switch and change and toggle had us believing we had found the solution to the poor server performance and everything was under control (we really should have made that post to update you earlier). Still nothing. What to do? Upgrade, now! By midnight, we were resigned to the fact that we needed a bigger server, several of them in fact. Or did we?

It wasn't supposed to take long. Provision some new servers here. Move all files and databases there. Update some DNS records somewhere. Easy peasy. Except, it wasn't easy peasy. We weren't just getting a bigger server to move to - we already had Namecheap's finest. And we'd grown tired of messaging them about our server slowing down once we reached a thousand plus users per second (it wasn't looking good too; when users begin to experience issues with a website, they tell others, who also try connecting and then tell others, ad infinitum, worsening the problem, although in our case this proved to be a blessing down the road). We were going to move somewhere we'd have full control over our servers, so we could tweak them to our heart's content, and not have to contact a remote technician whenever we had difficulty. Where? Destination Digital Ocean (for the unintiated, they provide unmanaged, bad-ass servers).

Thus, we began this migration that was totally unplanned for. By about midnight on day two (the 12th), we had packed our bags on the old servers, so to speak, and were slowly and carefully moving camp, to ensure we didn't break anything. We hoped it'd be like the last time. Set up, then point everyone there via DNS. Boy, were we wrong! Configuring new, blank servers to match the environment Racksterly ran on and getting them to sync and work as a cluster took most of the day. We seemed to underestimate how long everything would take at every step of the way. Deciding to use a cluster we could always extend, however, was the best decision we could have ever made (in hindsight, it was just common sense). That's because it forced us to use a totally seperate machine for the database (a cluster of database servers, in fact - everything had to have a backup now). And that proved pivotal.

We estimated we'd be done by the evening of the 12th. We were, sorta. When we began importing the database to the new database cluster (by about midnight, the hour of the "Red Bull" post, which was when we actually closed off access to the site), something happened that we dismissed as nothing. As the queries were executed by the much faster web servers, the database server slowed down. When we tried opening a seperate configuration web page that relied on the database to load while the migration was in progress, the page took forever to load, then ended with the message, "This site can't be reached". Ring a bell? When the import ended, everything loaded fine. We should have known.

As the Racksterly site loaded with lightning speed in the early hours of the morning on Day 3, we felt we had successfully resolved the issues. But, we held off on making any announcements so we could monitor the servers and ensure they were stable. That turned out to be the right call. As users flooded in, our website slowed down again. What the heck?! Average server load was 0.1%. Something wasn't right.

If the web servers weren't breaking a sweat, and the site was slow, something was. And there was only one other place to go. Yeah, you got that right. It was the database server. We hadn't exactly taken the biggest of them all, so we thought, "maybe its too small". We forked a new cluster, then destroyed that one (that's the reason you could sign in one moment, and couldn't sign in the next, getting the "Forking DB clusters. Please wait…" message instead).

The new cluster was massive, to put it mildly. It seemed our solution to every problem was "Get a bigger one!". As this was the largest we could get on DO, it had to work or else! Forking-Forking. Copying-Copying. Importing-Importing. Slowly and carefully. When it was ready to roll, and we pointed the web servers there and began hitting it, things looked okay. For a while. As we approached a thousand users connected per second, our site slowed down again. "This can't be happening!", we thought. Yet, there it was, unfolding right before our eyes.

Then we noticed something weird. The slow speed wasn't something we got all of the time. We had restarted the servers, and on browsing the website without signing in, it loaded incredibly fast. Once we tried signing in though, (which is what everyone was doing, and which included hitting the database), it made snails feel like Usain. We had a pattern. When we looked at the database logs, we noticed throughput averaging 14 million queries per second. We were pushing the database server, and for only about a thousand users connected at the time, something really nasty was going on.

So, we wrote a small program to log to a file whenever the database was queried. Lo-and-behold, there it was! Everytime a user tried signing in, the program that set up his session would make a blood-curdling number of queries on the database. For each user!.

With thousands of users waiting on each keystroke, and with fatigue dogging our steps, we proceeded to modify core parts of Racksterly. When you've been without sleep for long enough, your appetite goes out the door, and your mind begins to play tricks on you. Nothing keeps you going besides sheer will, and a refusal to stop until the job is done. Humans aren't designed to stay awake for so long, normally. But with thousands of users waiting with bated breath, sleep was a luxury we couldn't afford. This was the third day, and Red Bull was our crutch. Everyone had had so many cans the next one was having next to no effect. But there was too much riding on this - we simply couldn't quit or fail. We couldn't afford to let down the people who had trusted us with all their hearts. Or show them up to those they had convinced of our mettle. I guess when something is really important, you go for it with every breath in your body, no matter the odds.

By about 9pm on the 13th, we were done writing and testing. This was our last card. Our final roll of the dice. If this failed…well, better not to think about it. We re-opened login and held our breaths. 50 users, 100…300…500…as word spread that users could sign in, so did the number of simultaneous users increase. 1000…1500…2500…3000…3500. Average server load had maxed out at 0.5%. User's were still logging on by the second. And the servers were still chewing through requests like no man's business. If you were on 4G, you couldn't say your name before the site loaded (you still can't). We had dodged a bullet!

What was next? Pay everyone due for withdrawals. Except we couldn't. We had set things up in a way that made us accessible to everyone who needed access to us, so our bank had already sent officials the previous day to confirm that we weren't trying, or even planning to pull a Houdini. Obviously, the complaints had reached them. But when they saw the physical state of things around here, and went through our transaction records, it was clear as day that our hearts and souls revolved around one thing. And it wasn't "running away". By early evening on the third day, we received the news that our accounts had been unfrozen.

We still had an obstacle to surmount. Transfers on Paystack had been suspended, as we had found out the previous day. And we had received the email response we published in our previous post. There was nothing to do now but wait for the phone call from Paystack. It came in by about 7:30pm on Saturday, 14.12.2019, and lasted about 35 minutes. We could tell that this situation had caused them a real headache, with users emailing, tweeting, and probably calling, in droves. They asked many questions. We answered. They made it clear that there was a huge chance our business would be deactivated on Paystack due to the shitton of complaints they had received in the past two days or so. We dared to hope against hope. We still don't blame them. It's hard enough dealing with customer requests about one's own business. So, for just one of the businesses using their service to have given them so much of a headache couldn't have been funny. And it could have been worse if we'd actually had some funny business in our plans then or for the future.

We provided certain documents and particulars they requested after the call. But not before we were informed we'd get a response by Monday. Now, anyone who had initiated a withdrawal right before or after the server incidence knows it didn't play out that way. By 7:45pm on Sunday, transfers to thousands of users were underway. By 9pm, everyone who had made a withdrawal before then had been paid. Order had been restored. We didn't know what happened, but we were grateful it had happened.

We've spent the past few days improving and fixing any bugs that may have remained.

Now, there have been some complaints after the fact. Like complaints about the new interface. So, let's discuss that for a bit. Why some would complain that their activity balance (now Ad Credits) was being debited, even when you've never had an activity balance before now, and your main balance was being credited in usual fashion, and we told you we were still tweaking things, is beyond us. But again, there's nowt as strange as folk, eh?

Ad Credits are meant for publishing your own ads directly from your accounts. We noticed that most of us own or are involved in businesses on the side. And we thought to encourage and help you get some exposure by giving you some ad credits to start with. Alas, it was abused. We had posts of animals and bare chests and paper and legit products and mucky products and services and whatnot. Not exactly what we thought you'd do with it. The end result and experience for other users was an eyesore. So, we disabled ad publishing for a little while, and began cleaning things up.

By the time you read this, ad publishing would have been re-enabled. But before you make another post, there's something you need to know:

We're implementing a zero-tolerance policy on ads posted. There's a new "Report post" feature (tap the three dots under a post to see it). As the Stream is slowly becoming the biggest part of the Racksterly experience, everyone has a responsibility to ensure only high quality posts are allowed, for one another. So, if you see a post that shouldn't be there, report it. If a post is reported by enough people (we've set "enough people" to a small number of people), not only will your ad be removed, but its owner's Racksterly account will also be disabled. Permanently. Shitty posts will not be tolerated. If you have a legitimate business or service to advertise, you have nothing to worry about. Just take the time to prepare a nice image or video (video ad publishing from your account is now available!), and write a nice description and title, and you're good to go. Oh, and don't come looking for a refund if your account is disabled for a truly shitty post. You won't get it. Post something useful, or post nothing at all.

By the way, speaking of refunds, when we saw the number of sliding tackles that had been made on our Facebook Page, we thought we'd have to make thousands of refunds. We haven't had up to 20 requests. Weird, no?

Everyone's ad credits have been reset to zero. When you want to publish a post, you can simply top up your ad credits (now you know what the top-up feature is for). Then, you can create a post from the ad credits in your ad credits balance.

There are some posts that aren't allowed on Racksterly. Let's address those:

Sexually explicit/violent content is not allowed. In fact, pretty much anything you wouldn't let your kid catch you looking at is not welcome.

Political ads are cash-cows for platforms that thrive on providing publicity. However, we won't be accepting political ads on our platform, for what should be obvious reasons. And if those reasons aren't obvious to you, then you've probably been asleep the past few years. Here's some cold water.

Spammy, scammy, or misleading content are all not allowed. Neither is news. Please do not advertise news articles.

Products, businesses and services that pass the above tests are fine, pending when we update the list (we'll let you know when we do).

We promised to compensate you for the days you lost while you couldn't use our service, and we have. It wasn't the most comfortable of decisions, but a promise is a promise. If you still haven't been compensated, kindly get in touch with us and we'll take care of it.

We're sorry for ever putting your integrity in doubt before those you introduced into our family. Even though we pulled through, you should never have been in that situation. We're really sorry.

Thank you for trusting and believing.

We love you. For always.

PS: We still don't have a Twitter handle.

Nightmare before Christmas

Over the past week or so, you may have had your account compromised or "hacked", and your earnings transferred to a different bank account than yours.

Now, why you would give your email address and password, or even more astonishingly, your ATM card details and (oh, the horror!) a transaction OTP to a total stranger over the internet we can't exactly understand. But as they say, there's nowt as strange as folk.

We have a responsibility to protect our community, and you can be sure we're taking this very seriously:

You can no longer change the bank account information on your profile. If you absolutely need to change it (say, because your withdrawals to your linked bank account are failing), send us an email and we'll do it for you. You must make sure, however, that the name on the new bank account you provide matches the name on your Racksterly profile. And don't worry about missing your withdrawal day. You'll be able to access your account until you've withdrawn your money.

You can no longer change the email address on your profile. That's pretty much self-explanatory.

Sometimes, we get requests from users to provide a bank account they can make a payment to when they are experiencing issues making payments with Paystack. It's not that we can't. We just don't, and the reason is accountability and speed. When you make a payment with Paystack, and something goes wrong, your bank has only one place to go and one person to talk to for answers, and you can be sure you were actually making a payment to us, and someone knows what happened to your money. You can also be certain you'll get your money back, and fairly quickly too. You don't get that with bank transfers, where the recipient might as well be your neighbour next door, and recovering it could take a lifetime. We'll never ask you to transfer any money to any bank account. So, please don't do it.

Did we mention we don't have an android app yet? That's right, we don't. So, if you're using a "Racksterly app" you downloaded on the play store, we have no control over what happens to your data as you enter it on the app, and you're practically begging to be screwed. Kindly uninstall it. We've contacted the app publishers to take the apps down, and they've acceded. So as of this moment, you shouldn't be seeing any Racksterly apps on the Play Store.

If your account has been hacked (assuming we can call fleecing a person of money they worked for by collecting and then changing their login details "hacking" - what a joke), kindly get in touch. We understand that the experience can be disorienting, and we're here to help you get your account back.

Send us an email with subject "Account compromised". In this email, include as much information as you can about your account: your phone number, your subscription transaction reference, your full name, and the Facebook name on the profile, etc, and we'll help you get right back in.

We know that some persons had their earnings stolen/transferred to a different bank on their withdrawal day by those who took over their accounts. As much as we both know this is really your fault, you're still our own, and we always take care of our own.

Kindly send us as much information as possible explaining what happened. Screenshots with subscription payment evidence and your phone number (and even screenshots of the withdrawal confirmation email you received) will help expedite the process. We want to be able to verify that what you say happened actually happened without having to request additional evidence. Once that's done, we'll make a full payment of your earnings to your bank account (include your bank account in your email) on our account.

We'll be disabling withdrawals until 4:00 PM, 03.12.2019 GMT+1. That's tomorrow. This is to give people with "hacked" accounts enough time to get their accounts back. Sorry if this ruins anything for you, but this is necessary to keep anyone losing the money they've worked hard for within the next few hours.

We're here for you.

Everything Is Scary

We're not sure what is it about today's occurrence that was scary, but it appears we managed to scare a few souls. Guess we didn't think that one through.

For the next few weeks, we'll avoid doing anything that disrupts your experience. If you haven't shared today, please sign in and do so.