Configure Revenipe

Before your app can use Revenipe, the Flutter SDK must be configured with your Revenipe public key.

The public key connects your client app to the correct Revenipe app and environment.

Before you start

Before configuring the SDK, make sure you have:

• installed the Revenipe Flutter SDK

• created a Revenipe app

• copied your public key from the dashboard

• selected the correct environment for testing or production

Step 1: Copy your public key

Open the Revenipe dashboard and select your app.

Go to App Settings and copy the public key for the environment you want to use.

• Use your sandbox public key while testing

• Use your production public key only for live apps

• Do not mix sandbox and production keys in the same build

Step 2: Configure the SDK

Configure Revenipe before calling any other SDK method.

Example
Flutter
Copy
await Revenipe.configure(
  publicKey: 'rpk_sandbox_...',
);

Step 3: Configure early in your app

Call the configuration method during app startup before login, product loading, purchase flows, entitlement checks, or usage tracking.

Example
Flutter
Copy
Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();

  await Revenipe.configure(
    publicKey: 'rpk_sandbox_...',
  );

  runApp(const MyApp());
}

Sandbox and production keys

Your public key determines which Revenipe app and environment the SDK connects to.

Use sandbox while building and testing your integration. Use production only when your products, provider setup, purchase flows, and entitlement checks are ready for real customers.

• Sandbox keys are used for testing

• Production keys are used for live apps

• Products, purchases, and customer access are environment-specific

Important

Your Flutter app should only use the Revenipe public key.

Never ship Stripe secret keys, restricted Stripe API keys, RevenueCat private keys, webhook secrets, database URLs, or other backend credentials inside your client app.

The public key identifies your Revenipe app and environment. It should not be used as a backend secret.

Next steps

After configuring the SDK, login a customer before fetching products, starting purchases, checking entitlements, or tracking usage.