Social Media Platforms
Facebook Credits
Facebook Credits was Facebook's own virtual currency, piloted in 2009 and pushed into general use through 2011, that the company tried to make the mandatory payment method for every game and app on its platform, taking a 30 percent cut of every transaction. Developers led by Zynga resented the forced conversion from real money to Credits to in-game currency and the fee it locked in. Facebook backed away from the mandate in June 2012 and let developers price directly in local currency again, then wound the currency down entirely.
- Company
- Started
- 2009
- Ended
- 2012
- Facebook's platform-wide cut of every Credits transaction
- 30%
- Collapse speed
- Rapid
- Preventability
- High
- Lesson transfer
- Industry-wide
- Last reviewed
- 2026-08-06
Narrative
The story
The ambition
Facebook Credits began as a modest idea, a single virtual currency that users could buy once and spend across any game or app on the Facebook Platform, instead of juggling a different payment flow for every developer. Facebook piloted the system in 2009 and moved it through beta through 2010 and into 2011, priced at ten Credits to the US dollar and supported in fifteen currencies. The ambition went beyond convenience. If Facebook owned the pipe that real money had to pass through to reach a game, it could take a cut of every transaction on its platform and make Credits synonymous with spending money online, the way Apple had done with the iTunes balance.
The rise
By early 2011 Credits had real traction. More than 150 developers across over 650 games and apps had integrated it, and Facebook said it accounted for more than 70 percent of the virtual goods bought on the platform. Zynga, the maker of FarmVille and by far the largest developer on Facebook, was already routing payments through Credits, along with PopCap and Playdom. Facebook had quietly locked in agreements with these major developers before announcing, in January 2011, that Credits would become mandatory for all Canvas games starting July 1, 2011. Developers could keep their own in-game currencies, but any real-money purchase had to convert through Credits first, and Facebook took an industry-standard 30 percent cut of every purchase.
The cracks
The mandate had been rumored for a year and had already stirred what one contemporary account called plenty of angst in the developer community before it was confirmed. The economics were the core complaint: a 30 percent platform tax, layered on top of whatever fees developers already absorbed, on money that had to pass through an extra currency conversion before it reached a game. The advocacy group Consumer Watchdog went further, asking the Federal Trade Commission to investigate Facebook Credits as an antitrust violation, arguing that Facebook used its dominant share of the social-gaming market to force developers into exclusive use of Credits, bar them from offering lower prices off-platform, and impose fees that fell hardest on smaller developers who could least absorb them. Most developers had already built their own in-game currencies, and a platform-wide currency standing between the user's wallet and the developer's economy was friction they had not asked for and could not tune themselves.
The collapse
Facebook never let Credits fail loudly; it walked the mandate back instead. On June 19, 2012, not quite a year after Credits became compulsory, Facebook announced developers could once again price items directly in local currencies, mirroring the model Apple and Google used in their own app stores, and added subscription billing as a new option. Facebook's own justification was blunt: most games had already built proprietary virtual currencies, so a platform-wide one added a redundant step rather than removing one. Existing Credits balances were converted into local-currency equivalents, and the 30/70 revenue split stayed unchanged; only the mechanism developers were forced to route payments through went away. A separate account of the reversal from the same week added that Facebook saw payments as too important a future revenue line to keep tied to an unproven proprietary currency, and wanted to avoid the regulatory exposure that came with acting like a currency issuer.
The aftermath
Zynga, still Credits' largest single source of volume, said the change might affect its accounting but described its economic relationship with Facebook as otherwise unchanged and committed to working through the phase-out. Facebook kept building on the local-currency model it had reverted to, framing the move as a step toward broader payments ambitions such as a "Pay with Facebook" button and eventual expansion beyond gaming. The Credits brand itself lasted a little longer in name only before Facebook finished retiring it, closing out an experiment that had gone from mandatory platform infrastructure to a footnote in about three years.
The lessons
Facebook Credits failed because Facebook tried to insert itself as a mandatory intermediary in a transaction that developers and users could already complete more directly, and it charged a steep toll for the privilege. A platform-wide currency only earns its keep if it removes friction; here it added a conversion step, a 30 percent fee on top of costs developers already bore, and a loss of pricing control, while delivering no matching benefit to the people forced to use it. A dominant platform mandating its own currency also invites the regulatory scrutiny it is trying to avoid: Consumer Watchdog's antitrust complaint to the FTC shows how quickly a forced-payment mandate can be read as an abuse of market power rather than a convenience. Facebook's reversal, quiet and unapologetic, is itself a lesson: a platform owner can retreat from a bad mandate without a public reckoning, so long as it moves before the resentment curdles into regulatory action or developer exodus.
Causal timeline
Failure Anatomy
- 2011
Credits piloted and built out
Facebook piloted Credits in 2009 and expanded it through 2010 and early 2011, priced at ten Credits per US dollar and supported in fifteen currencies, reaching more than 150 developers across 650-plus games and apps. [1]
- 2011-07-01
- 2011-2012
Developer resentment and antitrust scrutiny build
Developers who had already built their own in-game currencies chafed at the added conversion step and the fee, and Consumer Watchdog asked the FTC to investigate Facebook Credits as an antitrust violation. [4]
Poor executionRegulatory pressure - 2012-06-19
- 2012
Credits wound down
Existing Credits balances were converted into local-currency equivalents and the currency was phased out, ending an experiment that had briefly been mandatory platform infrastructure. [8]
Failure to adapt
Structured analysis
What Went Wrong
Root causes
A 30 percent toll on every transaction. Facebook required all Canvas game payments to route through Credits starting July 1, 2011 and took a 30 percent cut of every purchase, on top of costs developers already carried. [2] [3]
Added friction instead of removing it. Because most games had already built their own virtual currencies, forcing real money through Credits first added a conversion step rather than simplifying payment, and Facebook itself cited this redundancy when it reversed course. [6]
Contributing factors
Antitrust scrutiny of the Credits mandate. Consumer Watchdog asked the Federal Trade Commission to investigate Facebook Credits as an antitrust violation, arguing Facebook used its market dominance to force exclusive use of Credits, block off-platform discounting, and impose fees that hit smaller developers hardest. [4]
Developers had no alternative but compliance. Because Facebook controlled distribution to its user base, developers who objected to the mandate and the fee still had to adopt Credits to keep selling on the platform. [2]
Immediate trigger
Facebook reverses the mandate. On June 19, 2012, Facebook announced developers could price directly in local currencies again and added subscription billing, ending Credits' run as the required payment intermediary less than a year after the mandate took effect. [5]
Visible symptoms
Developer anger over the mandate's rollout. The mandatory-Credits policy had stirred what contemporary reporting called plenty of angst in the developer community even before it was confirmed, and Consumer Watchdog's FTC complaint made the antitrust concern public. [2] [4]
Warning signs
Facebook framed payments as too important to risk on Credits. In explaining its own retreat, Facebook signaled that it now saw payments as a core future revenue line too important to tie to an unproven proprietary currency, an implicit admission that the Credits bet had not paid off as hoped. [7]
Affected groups
Keep reading
Related failures
Evidence
Claims & sources
Every numbered marker in the analysis links to the claim it rests on, and each claim to its sources.
- [1]
Facebook piloted Credits in 2009, expanded it through beta in 2010 and early 2011, priced it at ten Credits per US dollar, and supported fifteen currencies, reaching more than 150 developers across over 650 games and apps by early 2011.
- [2]
Facebook confirmed in January 2011 that all Canvas games would be required to process real-money payments through Facebook Credits starting July 1, 2011, and had already secured agreements with major developers including Zynga, Playdom, and Playfish before announcing the mandate publicly.
- [3]
Facebook took an industry-standard 30 percent cut of every purchase made through Credits, a rate that remained unchanged even after the 2012 reversal away from mandatory Credits.
- [4]
The advocacy group Consumer Watchdog asked the Federal Trade Commission to investigate Facebook Credits as an antitrust violation, alleging Facebook forced developers into exclusive use of Credits, barred them from offering lower prices off-platform, and imposed a 30 percent fee that fell hardest on smaller developers.
- [5]
On June 19, 2012, Facebook announced that developers could once again price items directly in local currencies rather than exclusively through Credits, and introduced subscription billing as a new payment option.
- [6]
Facebook explained the reversal by noting that most games on Facebook had already implemented their own virtual currencies, making a platform-wide currency an added, redundant step rather than a simplification.
Moderate Reported explanation Facebook Adds Subscription Billing For App Developers, Backs Away From Credits As Primary Currency - [7]
A contemporaneous analysis reported that Facebook saw payments as too important a future revenue source to keep tied to an unproven, unregulated proprietary currency, and wanted to avoid the regulatory scrutiny of acting like a currency issuer.
- [8]
Existing Facebook Credits balances were converted into local-currency equivalents as part of the phase-out, and Facebook subsequently retired the Credits system.
Sources
Facebook Credits
Wikipedia
Facebook To Make 'Facebook Credits' Mandatory For Game Developers (Confirmed)
TechCrunch · 2011-01-24
Why Facebook Is Folding On Credits And Doubling Down On Payments
TechCrunch · 2012-06-23