YaqeenDocs
Back to Yaqeen

Explanation

How Yaqeen decides

How Yaqeen links parties, what kinds of risk it looks for, what a recommendation contains, and why a person always makes the final decision.

Yaqeen recommends holds. It does not hold money. It looks at each payout before its deposit day, together with the stores, owners, buyers and bank accounts around it, and recommends a hold when the payout looks risky. A reviewer on your team makes the decision.

Linking parties#

A store can look fine alone. The risk often shows only when you link it to other stores, owners, buyers and bank accounts.

Yaqeen treats two kinds of link differently:

  • Exact identifiers are the owner's national ID or iqama, the bank account (IBAN) and the commercial registration (CR) number. Yaqeen stores each as a keyed hash. Two records with the same value are the same party, and holds tied to that party are grouped into one case.
  • Weaker links, such as contact details or devices, are shared by many unrelated people, like a family or the staff of one shop. They never decide on their own that two people are one. They can add to the risk of a payout and appear as a reason a reviewer can check.

What it looks for#

Yaqeen looks at how money and orders move, not only at single transactions. Its checks fall under six broad patterns:

PatternIn short
Collection (تجميع)Many payments gathered in a short time.
Pass-through (تمرير)Money paid out almost as fast as it comes in.
Distribution (توزيع)One amount spread across many parties.
Circulation (تدوير)Money that moves among linked parties and comes back.
Shared beneficiary (مستفيد مشترك)Payouts from unrelated stores ending in one place.
Unusual behaviour (سلوك غير معتاد)Activity far outside the normal range for the store.

It also uses the operational records you send, such as payment attempts, logins, deliveries and refunds. The more of the tables you send, the more it can see.

What a recommendation contains#

Each recommendation has a risk score from 0 to 1 and a short list of reasons in plain words, each pointing at records the reviewer can open. Recommendations are ordered so the most urgent come first in the review queue.

Yaqeen is tuned to keep wrong holds on ordinary stores rare, because a hold delays a real merchant's money. Your organization chooses how holds are reviewed and how long they last in its settings.

A person decides#

A recommendation is not a decision. A reviewer reads the reasons and approves or rejects with a note. Holds are never released by the model, and a large hold needs a second person. A merchant can appeal, and a person reviews every appeal. Every step goes into the audit log.

Telling us when it was wrong#

When a reviewer rejects a recommendation or an appeal is accepted, that outcome is recorded. Tell your Yaqeen contact about a missed case or a run of wrong holds, so it can be checked.

Details of how detection is built and tested are shared with customers under a non-disclosure agreement on request.

Up Down to moveEnter to openEsc to close