Micropayments for publishers
This environment is simulated; any transactions made within it are not real.
How the system works
You know what's frustrating? Watching potential readers bounce off your paywall because they're not ready to commit to a full subscription. Here's how we address that challenge.
- 1. The moment of truth: When your reader hits a paywall, they see the usual subscription option – but now there's something new. A simple "pay as you go" button that lets them buy access to just that one article they're dying to read.
- 2. Streamlined payment process: Here's where it gets interesting. They get a QR code and an SMS link. One text message later – boom, article unlocked. And honestly? That SMS won't cost them a penny, thanks to most mobile operators offering free messaging.
- 3. Behind the scenes: We register that SMS operation and immediately unlock the article for your reader. No waiting, no friction, no second-guessing.
- 4. Settlement and revenue transfer: At the end of each billing period (weekly or monthly – your choice), we bundle everything together. Usage reports, billing summaries, payment collection – then we transfer those funds straight to you.
Want to see this in action? Check out our demo below and watch how seamlessly your readers can access premium content.
The questions everyone asks
What are the real transaction costs?
Here's our billing model: Instead of charging you for each transaction (which gets expensive fast), we focus on "settling" transactions.
The transactions themselves? Completely free. No percentage cuts, no fixed fees per transaction. Instead, we charge a small flat fee for "active account and settlement" within the system. This fee gets distributed proportionally among all publishers based on their revenue share.
What about payment security and fraud prevention?
Our model is built on payment declarations, which naturally raises questions about collection rates. We're transparent about this: some users may not settle payments initially.
However, we've developed comprehensive fraud prevention measures including unreliable number tracking and payment recovery protocols. During our meeting, we'll share specific data on collection rates and discuss risk mitigation strategies tailored to your content type and audience.
The trade-off? Access to revenue from users who would never subscribe but will pay for individual articles – a market segment traditional paywalls can't monetize.
How complex is the integration process?
We understand you're working with existing CMS systems or custom solutions. That's why we provide dedicated implementations tailored to your specific setup.
Integration support includes:
- Technical consulting at every step
- Ready-to-use integration codes
- EventSource-based architecture (known for reliable implementation)
- Typical timeline: 2-4 weeks depending on your current setup
We'll assess your technical environment during our meeting and provide a realistic timeline and resource estimate.
What about duplicate transactions? What if someone buys the same article twice?
Smart question. Each article gets a unique content_id. Even if a user somehow manages to unlock the same article twice, our system catches duplicates during settlement and treats it as a single access within that billing period. No double-charging, no confusion.
How do we determine article pricing?
Article prices are defined on your end – through HTTP headers or a dedicated service that returns prices for specific articles. We also support fallback pricing and custom mechanisms.
Pricing strategy is crucial for maximizing revenue, so we'll discuss optimal pricing models and provide benchmarks from similar publishers during our meeting.
Settlement Reports & Payment Process
Curious about what your users actually see? [Click here for a sample report]. After settlement processing, users get the full report via SMS. Payment is completed by scanning the QR code in their banking app.
Next steps
Ready to explore how this could work for your publication? Let's schedule a meeting to discuss implementation details, revenue projections, and address any technical questions specific to your setup.