Skip to content

Party.screen

POST /{namespace}/parties/{party}/screen

Screen checks a Party against official registers and restricted-party lists and keeps the result as a Screening.

Noun
Party
Mode
do
Event
Party.screened

Inputs

InputTypeRequiredDescription
partyPartyrequiredThe Party to check: a Customer, Supplier, Partner or the Company’s own owners.
marketslist of MarketThe Markets whose lists apply. Defaults to the Party’s and the Startup’s Markets.

Outputs

OutputTypeRequiredDescription
screeningScreeningrequiredThe Screening, with the lists checked, their versions, any matches and the outcome.
partyPartyrequiredThe Party screened.

Effects

  • Emits Party.screened.
  • Performed by the Risk Analyst.
  • Two-way: it runs at once, in the try, send and do modes.
  • Runs before the Party’s first money move and again when its details change.
  • A match holds the Party’s pending Orders and opens an Approval with the match attached.
  • Records Stripe’s own verification result as a Screening with via: stripe on the same Party.

Refuses when

CheckErrorFixThen call
The key is valid, but its scopes do not allow this operation.forbiddenUse a key whose scopes cover the operation, or ask an owner of the namespace to grant them.Party.screen

When it waits

GateDefault
Decision classLow: two-way, nothing at stake
Delay windowNone: it runs once review passes.
LimitThe call Limit of the Permission it runs under.
Over the LimitIt waits pending for an Approval from the Founder. Approved, it runs; refused, it ends refused with limit-exceeded; unanswered by its deadline, it ends canceled.