Skip to main content
Specter offers two ways to get a decision. Both evaluate the same rulesets and return the same outcomes; they differ only in where the integration lives. The API pattern works for any schema — the built-in transaction payload or one you register; the interceptor pattern applies to card-payment flows on the built-in transaction schema.

​
API

You stay in full control of the flow: call Specter, inspect the decision, and decide whether to authorize, hold for review, or stop. This gives you the richest request (you choose exactly what context to send) and the most flexibility in how you handle each outcome.

​
Interceptor

Specter terminates the request, maps it into a decision, evaluates it, and then either transparently forwards the original request to the real destination (ALLOW) or returns a configured response (BLOCK / REVIEW) without contacting it. Your backend needs no decision logic — it only changes the URL it calls.

​
Which should I use?

API

Choose this when you control the payment backend and want maximum context and flexibility.

Interceptor

Choose this when you want fraud protection without changing backend logic.