Project details#
Settings › Project details edits the project document: name, description, status, locales, capabilities (which areas the project has at all), contact and legal details. The project's locales decide how many tabs every localized document has — add one here before writing content in it.
Environments#
Below the form sits the Environments · Demo card. A project runs on Production; Demo is a separate copy for trying things out, and the console opens it only when Demo is enabled for that project. The card shows the state, who set it and when. Enabling is done by the platform team — ask your platform contact; once it is on, each member additionally needs the Demo grant in Settings › Members to switch environments. Disabling closes the project's Demo copy in the console for everyone; the Demo data is kept and comes back when Demo is enabled again.
Payments#
Settings › Payments configures the payment services the checkout offers: each service is its own card — Add in the toolbar picks a new one, the bin on a card removes it, and both take effect at once.
Stripe is one card: its checkboxes pick the services — Stripe Checkout (hosted page), Stripe payment (on-page) and Stripe subscription — and below them sits the setup, because from that moment the project cannot take money without it:
- Where the money is collected. Own Stripe account is the implemented mode: the project charges on its own account. Connected account — the platform collecting and paying out to you — is coming soon.
- Keys. The publishable key (
pk_…) and the account id are public config the storefront reads to mount Stripe.js. The secret key (sk_…) is stored encrypted and never shown again; typing a new one replaces it, leaving the box empty keeps it. The card tells you which account those keys really belong to and whether it is live or test — a test key on a production project takes no real money. - Webhooks. Stripe calls back when a payment or subscription changes; without those callbacks a payment succeeds at Stripe and the order never completes. Check reports what is registered, Set up webhooks registers what is missing and projects the signing secrets so every delivery is verified. Recreate is for endpoints made by hand in the Stripe dashboard, whose signing secret Stripe will not reveal a second time.
Payment methods#
Below the service cards sit the configuration cards of installed payment-gateway modules and Payment methods — the list the checkout actually offers, saved with its own Save. Without any row the checkout takes the Stripe services ticked above; cash, cash on delivery and gateway modules exist only as a row in that list. The list, the gateway modules and the order page's payment actions (Mark paid, the payment alert) are described in Payments.
Carriers#
Settings › Carriers sets up shipping — the carriers the checkout offers with their prices and countries. Add in the toolbar adds a carrier (on Demo also the simulated Test carrier), the bin on a carrier's card removes it; the page shows:
- Shipping — the sender name and country, the VAT rate on the shipping fee, the label format (PDF or ZPL), and whether the shipment moves the order status by itself (ready → shipping → delivery → completed).
- One card per carrier — the carrier's credentials (stored encrypted, never shown again — an empty box keeps what is stored), its account numbers and defaults, a Test environment switch where the carrier has one, and Verify, which makes one cheap call to prove the credentials work. A carrier whose integration is not available yet shows Not supported yet; you can still prepare its account. The simulated Test carrier (Demo only) lets you try the whole flow without a contract.
- Carriers from modules — a carrier installed as a module shows its own configuration card here too.
- Delivery methods — what the checkout offers: the carrier and its service, home delivery or a pickup point / box, the name in each language, the price, free shipping from an order total, the countries it ships to, and whether cash on delivery is allowed. This list is public — the storefront reads it — so it never holds credentials. A carrier module that is disabled or not verified yet is listed but cannot be picked (module disabled / not verified); a method that already uses one keeps it and shows the reason beside the carrier. Saving refuses an enabled method on such a carrier, or a service the carrier's module does not list — untick Enabled to park the method until the module is ready. The checkout leaves out every method whose carrier module is disabled or unverified.
Both pages are manager-only.