> ## Documentation Index
> Fetch the complete documentation index at: https://paytectechnologies.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> Core terms used across the Zeam API Gateway documentation.

**Association**: A Zeam business tenant. Every application and all data are
scoped to one association. The gateway resolves it from your token; you never
pass it.

**Application**: A registered integration bound to one association.
Authenticates with client credentials, not a human login.

**Client ID / client secret**: The credentials exchanged at
[`POST /v1/auth/token`](/authentication/tokens) to obtain an access token.

**Application secret**: The secret sent on every protected request as the
`x-zeam-auth` header. Issued at registration as the `apiKey`.

**Access token**: A short-lived bearer token used in the `Authorization`
header. See [Access tokens](/authentication/tokens).

**Wallet**: An account that holds balances and has a Stellar public key
(`G…`). See the [API reference](/api-reference/introduction).

**Beneficiary**: A saved recipient (individual or business) under an
association.

**Connector**: A payment provider integration for a specific corridor,
exposed via [`GET /v1/connectors`](/api-reference/introduction).

**Corridor**: A combination of country, payment method, and direction
(on-ramp or off-ramp) that a connector serves.

**Quote**: A priced send or receive offer for a connector and amount, with a
rate, fees, and an expiry.

**Intent**: A transaction intent describing what should happen. Created with
[`POST /v1/intents`](/api-reference/introduction) and tracked by its state.

**Payment**: The execution of an intent, submitted for processing via
[`POST /v1/payments`](/api-reference/introduction) and accepted asynchronously.

**Webhook**: A registration that delivers payment-intent events to your
endpoint. Registered in the business portal; listed via
[`GET /v1/webhooks`](/api-reference/introduction). See [Webhooks](/webhooks/overview).

**Problem response**: The [RFC 7807](/platform/errors) error format returned as
`application/problem+json`.

**Request ID**: The `X-Request-Id` on every response (mirrored as `requestId`
in problem bodies), used to trace a request in support.