knobit.org

C3 (2 points)

edu:Question

https://knobit.org/id/task/dii-event-rule-tuning/C3

Also as Turtle · JSON-LD · RDF/XML

dcterms:licensehttps://creativecommons.org/licenses/by/4.0/
owl:sameAshttps://bitbucket.org/reffa/ontology/id/task/dii-event-rule-tuning/C3
rdfs:labelC3 (2 points) en
schema:hasPartdii-event-rule-tuning C3: pass-through and collection kept as two mule stages, not an overlap
schema:hasPartdii-event-rule-tuning C3: a 7-day window rejected for the pass-through typology
schema:identifierC3
schema:position3
schema:textTypologies, 1 each. (a) CH-5 rejected and IP-03 kept: IP-02 (pass-through - a credit moved on within the hour) and IP-03 (collection - many senders paying into a new account over days) watch different stages of the money-mule typology on different events, and both already join the account's open case, so they do not raise two cases. (b) CH-3 rejected (or deferred for a back-test, for the typology's reason): mule pass-through on instant payments unfolds in minutes to hours; over 7 days ordinary flows (salary in, rent and bills out) match the 90% rule, and slow many-sender mules are IP-03's pattern, not IP-02's. en

Used by

has questionInstant payments rule tuning before go-live - expected volumes, double cases, typologies and a lagging feed (event rule design skills)
schema:isPartOfdii-event-rule-tuning C3: pass-through and collection kept as two mule stages, not an overlap
schema:isPartOfdii-event-rule-tuning C3: a 7-day window rejected for the pass-through typology