Documentation

Information for Fovea.Billing Users

Fovea's billing service will gradually be replaced by Iaptic. It's a new version of the same service, backward compatible, but distributed with different conditions.

What is the relation between Fovea and Iaptic?

In August 2020, iaptic SAS acquired the rights to distribute Fovea's Billing service. Being a company incorporated in France, it made it easier to access a number of services and build trust with our customers.

Fovea will continue to handle every technical aspects, while Iaptic handles the commercial side of the project. That is why we're rebranding our service as iaptic, a better name that also matches what you see on your invoices.

What has changed (or will)?

I you have already been using Fovea.Billing, here's a summary of what changed with the introduction of iaptic.com and what didn't.

New domain

  • validator.fovea.cc is now validator.iaptic.com.
  • billing.fovea.cc is now iaptic.com.

API v3

Iaptic introduces a version 3 of the REST API. It features some major changes:

v2 and v1 API endpoints are still available through a compatibility layer.

Teams

Administrators can add other member to their Team, those users can access the data for your application.

Google Subscription V2

Our server now validates google receipts for subscriptions using their newly introduced subscriptionv2 API. It's compatible with the new subscription model introduced in May 2022, which gives more options for the pricing of subscription products.

Pricing

Fovea's pricing model was unfair. Some free apps were making as many receipt validation requests (counted in millions) as other paid apps. But those apps having very few paying customers, and despite the massive cost to our infrastructure, they were still eligible for our free plan.

That's why we will now have 2 distinct quotas, depending on the plan: a maximum number of transactions and number of requests per month.

Some features like "Teams" will also only be available to the higher tier.

Check out our Pricing page for details.

How will the migration happen?

Step 0

For existing users, your data from Fovea.Billing is already available in iaptic.com. You can login with the same username and password and enjoy the new dashboard. Databases are synchronized 1-way, so data added through the old version of the service will also be available in iaptic.com.

As soon as we will be out of the beta period, it won't be possible to open new accounts in Fovea.Billing.

Step 1 - update your client

  • Use "https://validator.iaptic.com" instead of "https://validator.fovea.cc" as your validation URL.
    • You can find the exact URL in your Settings

Step 2 - update your server

Make API requests to https://validator.iaptic.com. Optionally, you can update your code to use API v3.

If there was only one good reason to upgrade to v3, it would be that it's better at tracking user entitlements. In the native platforms, there is no such thing as a "receipt identifier". Fovea did its best at generating one, in order to track the receipts and their updates so we can update the users' collection of purchases. But there were cases when it did not work properly.

Linking users to purchases solves the issue. The concept of receipt is only used internally as a mean to refresh purchases.

Invisible changes

We also updated our internal infrastructure to a solution that, we believe, will be more resilient to failure.

When will the Fovea.Billing website go away?

It will not go away. The old version of the service will remain live, until at least 2024. In the end, we will redirect requests from *.fovea.cc to iaptic.com, so everyone will be migrated to the new version of the service. It is backward compatible, so this will be invisible to the users.