Capacity is not a credential
A UPG slot is not an API key and does not create a second project identity. The application continues to authenticate with the project’s normal AvraAPI credentials.Workspace Entitlement
Includes the base capacity and any optional extra capacity.
Project Attachments
Active UPG project slots attached to connected projects.
Gateway Configurations
The project’s own encrypted gateway credentials.
Attach a project
An authorized Workspace member selects an eligible connected project and attaches an available slot. In the same protected operation, AvraAPI validates the entitlement and creates or resumes the project’s UPG integration anchor. The project still needs an active gateway configuration before it can start a checkout.Release a project slot
Releasing a slot immediately prevents new checkout creation for that project. The project’s encrypted configurations are retained so the same project can be reattached later without re-entering credentials. An already-created payment session can still complete through its signed, project-bound completion context. This avoids abandoning a customer who was already redirected to a provider.Plan changes
A Workspace has one active UPG base entitlement at a time. Changes can include a first plan activation, a billing-cycle change, an upgrade, added capacity, or a scheduled downgrade.Gateway access is plan-aware. A configured gateway that is outside the current entitlement is not available for new checkout until the Workspace plan permits it.