Feature Flags

How Feature Flags works in Paycux, what it is for, and the smallest setup that gets it running.

Overview

Feature Flags is part of the Paycux platform. This page explains what it does, when to reach for it, and the smallest working setup you can ship.

Everything below applies to both environments. Build and test in staging, then promote the same configuration to production without changing your code — only the API key and client ID differ.

Use cases

Use cases is handled by Feature Flags rather than by your application code. Paycux exposes it through the same API surface as the rest of the platform, so the client you already configured needs no additional setup.

Configuration lives in the dashboard and is versioned per environment. Change it in staging, confirm the behaviour, then apply the same change to production.

Before getting started

Before getting started applies specifically to Feature Flags. It behaves the same in both environments, and the values it depends on are visible in the dashboard for the environment you have selected.

If the behaviour you see does not match this description, check which environment your API key belongs to before anything else — a staging key against production data is the most common cause.

API object definitions

API object definitions is handled by Feature Flags rather than by your application code. Paycux exposes it through the same API surface as the rest of the platform, so the client you already configured needs no additional setup.

Configuration lives in the dashboard and is versioned per environment. Change it in staging, confirm the behaviour, then apply the same change to production.

Create a feature flag from the Paycux dashboard

Feature flags are evaluated per user and per organization, so you can ship a change to one customer before the rest. Evaluation happens locally against a cached rule set, so a flag check never adds a network round trip.

Flags are configuration, not permissions. Do not use a flag to gate access to data a user should not see — use a permission check for that.

Set the users and organizations that should have access

An organization is the tenant boundary in Paycux. Connections, directories, roles and audit log streams all hang off an organization, and a user reaches your application through a membership in one.

Create an organization per customer, not per environment. The same organization exists in staging and production with separate configuration.

Enable the feature flag

Enable the feature flag applies specifically to Feature Flags. It behaves the same in both environments, and the values it depends on are visible in the dashboard for the environment you have selected.

If the behaviour you see does not match this description, check which environment your API key belongs to before anything else — a staging key against production data is the most common cause.

Use the feature flags in your application

Use the feature flags in your application applies specifically to Feature Flags. It behaves the same in both environments, and the values it depends on are visible in the dashboard for the environment you have selected.

If the behaviour you see does not match this description, check which environment your API key belongs to before anything else — a staging key against production data is the most common cause.