Flexible Publisher Payment System (FPPS) by Tealium

Choose how to pay for viewing publisher content (ads, social, money - it's your choice)

Comment

Inspiration

People generally don't like online advertising but don't necessarily want to pay for a paywall. We wanted to give users the flexibility to choose how they "pay" for access to publisher content.

What it does

This is a javascript library (connected to our back-end) which a publisher can put on their site which will handle giving the ability for users to choose to pay into a common payment system either by:

  • Viewing ads
  • Tweeting content (paid in the form of credits, the more followers you have the more credits you get)
  • Paying cash (paid in the form of credits)

Credits can be spent on any participating publisher and article prices are set per publisher.

Additionally, we price the articles based on the price that advertisers have bid for the ads on the current page.

How I built it

  • Back-end written in PHP which stores visitor profiles and handles how many credits you have
  • Javascript API communicated with back-end to update profiles/request profiles
  • Twitter API communicated to in PHP to check credits from tweets
  • Bootstrap used to handle UI on top of publishers site

Challenges I ran into

  • Defining payment logic
  • Defining user journeys
  • Time!
  • Ensuring credits are not assigned for the same tweet twice!

Accomplishments that I'm proud of

The prototype works!

What I learned

Build your front-end first! The twitter API :) How to do a SCRUM(-ish)!

What's next for Flexible Publisher Payment System

Build into deployable package for any publisher and convert into full package

Built With

Share this project:

Updates