Settings

The Settings page (/settings) is read-only: it surfaces your organization identity and the static connection details your systems need to reach the platform. There is no edit form here — profile and membership changes happen elsewhere (see Manage below). Complete Before you begin first if you haven’t already; this page is where you find the values that walkthrough asks you to set up.

Identity

The Identity panel shows who you are and which organization is active:

• Organization (Logto) is the organization_id string claim issued by Logto for your active organization — the identity-provider side of your membership.

• Organization ID is the internal Switchbench org_id (a bigint), the identifier every API call and dashboard page is actually scoped to. It is a separate value from the Logto claim above, set at /cp/me time — don’t substitute one for the other in your own integration.

  If your account belongs to more than one organization, switch which one is active with the Active organization switcher in the top bar; this page always reflects whichever one is currently selected.

• Signed in as and User ID identify you, the signed-in operator, within that organization.

None of these values are used directly in your own integration code — your integration authenticates with an API key or a client certificate (see Before you begin), not with the org or user IDs shown here.

Connection details

The Connection details panel shows the two base addresses every integration is built on, plus the shared TCP service ports.

REST API endpoint

The base URL for the platform’s REST API — the host you send structured transaction calls to (for example POST /transaction/sale/pos), authenticated with an API key from the API Keys page. See Initiating a test transaction over REST for the full request contract.

This value is environment-specific: the test and production dashboards show different hosts, so copy the value shown on this dashboard rather than hardcoding a host from documentation or another environment.

Data plane host (mTLS)

The hostname your ISO 8583 or HSMaaS client connects to for the mutually authenticated TLS data plane. Point your client here and present the client certificate issued from the Certificates page — SMP resolves your organization from that certificate, not from anything in the connection itself. See Visa ISO 8583 over mTLS TCP or Mastercard ISO 8583 over mTLS TCP for the wire-level contract, depending on which network you’re integrating.

Service ports

The table below the two connection fields lists the shared TCP ports on the data plane host — one per protocol/engine, not one per organization. The destination port selects which engine handles the connection (Visa, Mastercard, or payShield HSMaaS); your client certificate, not the port, selects your organization.

Manage

The Manage section links out to where each related action actually happens:

• Members & roles opens the in-app Organization page to invite members and assign roles.
• Profile & MFA opens your identity provider’s external account console — when one is configured for this environment. Many environments have no self-service account console: the self-hosted Logto OSS install this platform runs on ships only a hosted sign-in flow and a loopback-only admin console, not an end-user profile page. When no console is configured, this page shows an honest Unavailable state instead of a link that would 404 — ask your organization administrator to update your profile or reset MFA in that case.
• Client certificates opens the in-app Certificates page to issue or revoke the mTLS client certificates your systems present on the data plane.
• Products & trials opens the Products page to see which products your organization can use, start a trial, and manage billing when it is enabled.