Payments
Sanctions screening as code: one policy, a different actuator per rail
The payment is final in under a second and your sanctions analyst is still opening the alert. On an instant rail there is no review window, so the screen has to clear or stop the payment in code, inside the latency budget. The policy model can be common across rails. The action on a hit cannot, because RTP, the card networks, and SEPA Instant each demand a different commit semantic.
Lead essay
Start here when you want the current Doric argument instead of a chronological archive.
Read the note