Compliance
5 Socure operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.
Who they are
Socure verifies consumer identities and predicts fraud from an identity graph assembled across many data sources, returning scores and reason codes rather than raw records. One product line covers KYC, synthetic-identity detection and document verification.
What a flow can call
/api/3.0/EmailAuthScoreThe main ID+ call. The endpoint name is legacy — the modules array is what decides the work.
/api/3.0/EmailAuthScoreSanctions, enforcement, PEP and adverse-media screening.
/api/3.0/transaction?referenceId=$data.socure_reference_idReplays a completed transaction by the referenceId the original call returned.
/api/3.0/reasoncodesEvery reason code and its meaning. Worth calling once to build a local lookup so a decline reason renders as words rather than as R185 — adverse-action notices need the words.
/api/5.0/documents/requestPredictive DocV — starts a session where the applicant photographs an ID and a selfie.
Where it sits in the decision
Screening answers the parts of a decision a regulator will ask about, so what matters is not only the verdict but the record of it. A partial match is the interesting case: rarely a decline on its own, and usually the point where the flow opens a case for a reviewer with the match evidence attached.
Whatever Socure returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.
Common questions
Add Socure as a connection in your workspace authenticating with an API key, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Socure in a decision without ever seeing the secret.
Yes. Socure runs a separate sandbox host, so a flow executing in Sandbox can make the real call against test credentials and you can read the actual response shape in the trace before anything reaches a customer. The flow does not change when it graduates — only which credentials answer.
5 operations, including “Verify identity and score fraud”, “Screen against watchlists (AML)”, “Re-read a past transaction”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Verify identity and score fraud”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.
Screening answers the parts of a decision a regulator will ask about, so what matters is not only the verdict but the record of it. A partial match is the interesting case: rarely a decline on its own, and usually the point where the flow opens a case for a reviewer with the match evidence attached.
Also in Compliance
Autentique5 operationsBrazilian electronic signature service, priced per document.
autentique.com.br
Clicksign6 operationsBrazilian electronic signature platform for regulated document flows.
clicksign.com
ComplyAdvantage3 operationsAML risk data: sanctions, PEP and adverse-media screening.
complyadvantage.com
Inscribe5 operationsDetects altered paystubs, bank statements and IDs.
inscribe.aiAn open database of sanctions targets, PEPs and watchlists.
opensanctions.orgReady when you are
Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.