Reference
FAQ
Questions people ask about Sentinel.
No. It answers allow, review or block, and your own system acts on that.
You decide in advance whether to fail open (let payments through and score them later) or fail closed. Most teams fail open for small amounts and hold large ones. Sentinel stores every event it accepts, so the record stays complete.
Any of them: mobile money, cards, bank transfers, instant payments and stablecoins. Every rail goes through the same API, and
rail is a field rules can test.Wherever you run Sentinel: on your servers or in your cloud account, never on Somu Labs servers. Today nothing leaves your network at all. See Data flows.
Yes. Regulators require a named person, the MLRO, and people make the final calls. Sentinel makes them faster and keeps the record.
The reports you file and the records you show them. Regulators don't log in to Sentinel. Reporting and evidence packs are planned; today you can show decisions with their reasons, alert notes and closures, and an audit log you can verify.
About 15 minutes to a first decision on a local install, under a day to deploy to staging, and about two weeks to full integration, including time where you send events but ignore the decisions. See the integration plan.
No. That's your identity verification provider's job. Send Sentinel the result as an entity attribute.
Licensing and metering aren't built yet. The plan: a warning at 80% and again at 100%, scoring never stops, and you move up a tier at the next billing cycle. See Licensing and metering.
Yes. Every decision stores the rule keys and versions that fired and the feature values they saw. Every rule version is kept, and the audit log shows which key created it and which approved it.