Provider mappings

What it is

Provider mappings connect RevenueCat product IDs or entitlement IDs to Meterly packages.

When to use it

Create mappings before expecting RevenueCat webhooks to create Meterly grants.

How to use it

How they work

A mapping belongs to a RevenueCat integration. RevenueCat product_id maps to Provider product ID and is checked first. RevenueCat entitlement_ids maps to Provider entitlement ID when product_id has no match. RevenueCat entitlement_id is a legacy fallback. The mapping points to one Meterly package. The package expiration policy controls the bucket created by a successful RevenueCat grant. RevenueCat app_user_id becomes the external customer identity for the grant. One RevenueCat event creates at most one Meterly grant.