Skip to main content
A UPG slot is a Workspace allocation assigned to one project. It is the permission boundary that lets the project use the Workspace’s Universal Payment Gateway entitlement.

Why slots exist

A project can keep historic Gateway Vault configuration after it leaves a Workspace or after its slot is released. That configuration alone must not be enough to start new payments. The SDK availability check requires an active slot before it exposes a usable payment method or creates a new checkout.
1

Workspace UPG plan

Supplies capacity to the Workspace.
2

UPG slot

Explicitly attached to a specific project.
3

Project

May use eligible Vault configurations.
4

Checkout session

Started successfully by the project.

What happens when a slot changes

The last rule prevents a buyer from being left with an unverified payment simply because an administrator changed capacity while the buyer was at the provider.

Check before rendering checkout

Call availability() on your backend whenever you prepare a checkout page. It returns ready, a safe reason when it is not ready, and public method metadata.
The matching PHP, Laravel, and Node.js tabs throughout this UPG section stay synchronized. Choose your SDK once and follow the same flow page-wide.
For buyer-facing recovery, see UPG Errors.
Last modified on October 1, 2026