Help
Glossary
One meaning for each term that Yaqeen uses in its API and documentation, in alphabetical order.
Each term has one meaning. The words match the API and the rest of this site. Where the product shows an Arabic name, it appears next to the English term.
A#
Admin. A staff role that runs the system: policy, accounts, API keys, webhooks, scoring runs, data loads and the sandbox. An admin can also decide holds. See Roles.
API key. A secret that a system uses instead of a person's sign-in. It starts with yq_live_ or yq_test_, is shown once, and has scopes. Only a hash is stored.
Appeal. A merchant's written challenge to an approved hold. A reviewer accepts it, which releases the hold, or rejects it. See How holds and appeals work.
Audit chain. The append-only log of every change, where each line holds a hash of the line before it. See How the audit chain works.
B#
Backtest. A test of a proposed policy or rule against past data before it is put into use.
C#
Case. A group of holds linked by an exact identifier: the same owner or the same payout bank account. A case can be assigned, annotated and closed with a conclusion.
D#
Detector. The part of Yaqeen that scores payouts and recommends holds. See How Yaqeen decides.
Dispute. A chargeback or dispute against a payout. Yaqeen sets its amount aside as a reserve and gives the merchant 10 days to answer. A reviewer decides it as won or lost.
E#
Exact identifier. A value that identifies one party: the owner's national ID or iqama, the bank account (IBAN) or the commercial registration (CR) number. Yaqeen stores each as a keyed hash. Two records with the same one are the same party.
F#
Feed. The endpoint POST /api/v1/ingest/feed/ that loads rows into one table, up to 5,000 per call.
H#
Hold. A recommendation to keep one payout back, kept until a person decides. Its statuses are recommended, approved, rejected and released. See Hold statuses.
I#
Idempotency key. A value you send in the Idempotency-Key header so that a retried decision runs only once. See Safe retries.
Intake. The process for a new store before its first payout: submit an application, mark the papers received, and approve.
K#
KYB. Know your business: the checks on a store and its owner. Intake follows a KYB checklist.
M#
MCP. Model Context Protocol, a standard way for an AI client such as Claude or Codex to call tools on a server. Yaqeen's MCP server has twelve read-only tools. See Connect Claude and Codex.
Merchant. A role for a store owner. A merchant sees only its own owner's holds, payouts and messages.
O#
OAuth. The sign-in standard that lets Claude or Codex act for a person without learning their password. The person signs in on a Yaqeen page and presses Allow. See Authentication.
Organization. One customer of Yaqeen, also called a tenant. Every person belongs to one, and each organization sees only its own data. See Organizations.
Owner. The person behind one or more stores, as in KYB.
P#
PKCE. A check in OAuth that ties a sign-in code to the client that asked for it, so a stolen code is useless. Yaqeen accepts the S256 method only.
Pattern. A fraud shape that the engine looks for. There are six: collection (تجميع), pass-through (تمرير), distribution (توزيع), circulation (تدوير), shared beneficiary (مستفيد مشترك) and unusual behaviour (سلوك غير معتاد).
Payout. Money that the platform pays to a store on its payout calendar. A hold is placed on one payout.
Policy. The settings that shape recommendations: hold length, appeal window, review time and detection settings. Each save is a new version.
R#
Reason. A sentence in English and Arabic, with evidence, that says why a hold was recommended. See How reasons are written.
Reserve. Money held back from a store for a stated reason until a date.
Reviewer. A staff role that decides holds and appeals, assigns cases and records conclusions.
S#
Sandbox. A second organization of yours for testing, with its own data and yq_test_ keys. Nothing in it reaches your real data. See Sandbox.
Scope. A permission on an API key: read, decide, ingest, scim or mcp.
Score. A number from 0 to 1 that the detector gives a payout. A higher score means a stronger recommendation.
Second-person approval. A control where a different reviewer or admin approves a large or risky change. See Second-person approval.
Shadow run. A trial of a proposed policy that counts what it would flag and places no hold.
Suppression. A rule that stops Yaqeen from recommending holds for a store, owner or bank account until a date. Every suppression ends and needs a second person.
T#
Tenant. Another word for an organization. See Organization.
W#
Weak link. A detail that many unrelated people can share, such as a phone, an address or a device. It can add a reason for a reviewer to check.
Webhook. An address that Yaqeen calls with a signed event when a hold or appeal changes. See Webhooks.
Related#
- FAQ: short answers using these terms
- Hold statuses: the exact status values