Let's be real: time is your most valuable asset. You're shipping code, building incredible experiences, and frankly, you don't have hours to decipher payment processing jargon. So, when you see a "72-hour hold" on your AIBC developer earnings, your first thought is probably, "What's that? And why isn't my money instant?"
I get it. In a world moving at warp speed, any delay feels like a lifetime. But this isn't some arbitrary gate. This 72-hour hold isn't about us holding onto your cash; it's about safeguarding the entire ecosystem – and ultimately, ensuring your payouts are stable, secure, and truly yours.
Why The Hold? The Unsexy Truth About Money
Think of AIBC as a vibrant marketplace for your code. You build incredible spinners, users install them via Claude Code, Cursor, or VS Code, and you get paid 60% of the revenue. It's a powerful model designed for maximum developer value. But like any marketplace dealing with real money, especially in a digital realm, there are inherent risks that can undermine trust and profitability. The biggest ones? Fraud and chargebacks.
Every transaction, every install, carries a tiny flicker of risk. Fraudsters are always looking for cracks in the system, attempting to exploit vulnerabilities for illegitimate gains. Users sometimes initiate chargebacks, claiming unauthorized purchases, technical issues, or simply buyer's remorse – a common occurrence in any digital commerce. Without a robust mechanism to vet these transactions, the entire system becomes vulnerable. If we paid out instantly on every single install, and then a wave of fraudulent transactions or chargebacks hit, the financial burden would be immense. This wouldn't just hurt AIBC; it would directly impact your legitimate earnings, potentially leading to clawbacks or a less stable payout structure overall.
This is precisely where the developer earnings hold period comes in. It's not a penalty or a tactic to delay your money. It's a necessary, calculated buffer. A brief, 72-hour window where we can proactively verify transaction legitimacy, detect suspicious activity, and mitigate the potential for costly chargebacks before funds are irrevocably released. It’s a vital layer of protection for every dollar you earn.
So, What Exactly Happens During These 72 Hours?
Simply put, the 72-hour hold is a short delay from the moment an eligible monetization event occurs (e.g., an install that generates revenue) until those earnings are officially cleared for payout to your account. It’s exactly what it sounds like: three days.
Here’s how it typically plays out:
- Monetization Event Triggered: A user installs your spinner via Claude Code, Cursor, or VS Code, and revenue is generated. Your 60% share is immediately earmarked.
- 72-Hour Clock Starts: From that moment, a 72-hour timer begins for that specific earning.
- Transaction Verification & Fraud Checks: During this period, our systems diligently work in the background. We're checking for unusual patterns, verifying transaction legitimacy, and flagging anything that looks suspicious. This isn't about doubting your users; it's about protecting all users and developers from bad actors.
- Chargeback Window Mitigation: This window also provides a crucial buffer against immediate chargebacks. While chargebacks can occur later, this initial period helps catch early issues and reduces the overall risk profile.
- Earnings Clear for Payout: Once the 72 hours have passed, and the transaction is deemed legitimate and stable, those specific earnings are officially cleared and added to your available balance, ready for your next scheduled payout.
Your Cash, Our Commitment
What does this mean for you, the developer? It means peace of mind. While your money isn't delivered the nanosecond a user installs, it is delivered securely. This small developer earnings hold period ensures that when your funds hit your account, they are solid, irreversible, and truly yours to keep. You can build with confidence, knowing the revenue you generate is protected.
We understand