Rovas makes it easy for volunteers to ask for payments, in a fair and community-building way. The key reason is that payments can be made in volunteer time in addition to national currency. The proof of volunteer work is ownership of the Rovas currency Chron.

Rovas provides several monetization options:

1. The Payment button. Similar to PayPal Donate button, an HTML element like a button or a hyperlink can be placed into your application, pointing to its Rovas project page.
   Clicking the "Reward" button there brings the Purchase details page, where the user can choose to pay with Chrons, or their national currency. Credit card is available as a payment method, which allows also non-euro payments.

   
   After the payment is completed, the project receives the funds and Rovas distributes them to the shareholders according to the rules set by the project owner when setting up the project.

2. The Rovas payment processor - suitable for web sites and web applications with own user database. This monetizing approach was chosen by the freemap.sk web application, and is described in the section Case 1 of the blog post The NEO way to finance collaborative and FOSS projects.
   The Rovas Payment Processor page provides implementation instructions. The application source code is available for inspection in GitHub and any Rovas-registered user can see the shareholders and work reports filed in the Rovas project for the Freemap application.
3. The Rovas API provides the most direct way for an external application to interact with Rovas. One example how the API was used is the Case 2 of the above mentioned blog post. It describes a monetization scheme, where consumers must reward the project before they are allowed to access the project content.

   The Rovas API provides also endpoints that support use cases not related to monetization. For example, in the nabezky.sk portal mentioned in the blog, content authors can file a work report and earn Chrons without leaving nabezky.sk. All they have to do is to enter the labor time and (optionally) the desired reward in a Rewards section of the content-creation form, as shown below:

   

   The work report verification required from all Rovas users who post their own reports can also be done outside of Rovas. Here is how it is done in the nabezky.sk application:

   
   In this illustration, a post is read by a user, who was designated by Rovas as a verifier, for the work report filed by user "plama". Only the verifier can see the approval radio buttons directly below the post and can therefore approve or deny the reported labor time.

Projects in Rovas have shareholders, who can be either individual users or other projects. The reward-sharing functionality allows rewards made to a project to be distributed according to the work time users reported in the project or a set percentage share negotiated among the shareholders. Rewards can cascade down through project shareholders to any number of sub-projects. For example, a FOSS project that relies on other projects for functionality or data can automatically funnel a percentage of every reward they get to those sub-projects. Rovas will take care of distributing the rewards (Chrons, Euros, or Merits) to the last dependent, whether it is an individual or a project.

The Reward-sharing settings in the Project form provide a slider for setting the portion of a reward that will be distributed in the form of Merits. If the value is less than 100%, controls for distributing the non-Merit portion of the reward appear. The project owner can direct that portion to a single user who will receive Chrons or Euros, or to the project itself. In the second case, funds flow into the project, and any worker that is a shareholder in the project can exchange their Chrons for Euros at the project-specific exchange rate, which might be more favorable than the Rovas generic rate.

The project page shows individual and project shareholders, as well as their shares in the project.

Rovas providers tools for searching projects and work reports. The individual work reports can be displayed complete with proof of work evidence and other information. The total tally of hours spent working on individual projects is also available on the Projects page.

The Work report page can be filtered by a number of parameters. Shown in the inset is a detail from a work report, where proof of work can be seen, togehter with the links to the report verification tickets.