Your staging tests should never send a webhook to a production customer. In PayloadPuffin, the app keeps them apart, not a naming convention in your payloads.
An app holds everything for one environment: its API keys, destinations, events, deliveries and channels. Use one app per environment, such as staging and production. There is no separate environment setting. The app is the environment.
Apps belong to an organization, which holds your members, plan and bill.
An app is a boundary
An API key works for exactly one app, and every request it makes reads and writes that app's data. An ID from another app doesn't exist inside it, so a GET for it returns 404. That's why a staging key can't reach a production destination, even by mistake.
A channel is different. It addresses events inside an app, typically one per customer, and narrows which destinations receive an event. It doesn't keep anything apart: a key for the app can address every channel in it.
Add an app
Owners and admins add an app with Add app in the app switcher at the top of the console's sidebar. The first app is created when you set up your organization.
Delete an app
Only an owner can delete an app, with Delete app in Settings. The console lists what will happen and asks you to type the app's name first. You can't undo it.
The app stops at once: its API keys stop working, new events are refused, and its deliveries stop. On the next daily cleanup, PayloadPuffin wipes its events, deliveries, stored requests and responses, destinations, transforms, analytics and API keys. Usage it already counted stays on the bill. The organization and its other apps aren't affected. To delete everything, see Delete an organization.
Next steps
API keys explains the credential that acts on one app.