Skip to main content
​
Improvement

​
Smarter Condition Fields in the Rule Editor

The rule editor’s condition field suggestions are now served by the backend, so the type-ahead always matches the exact request shape your rules evaluate against — including nested credential fields and your $.metadata.* paths. Fields that are unavailable on your instance, such as raw PAN paths below SAQ-D, are omitted automatically.
​
New ReleaseImprovement

​
Run Specter Within SAQ A and SAQ A-EP Scope

Specter now runs on instances assessed at SAQ A or SAQ A-EP — you no longer need a SAQ-D environment to use it. Below SAQ-D, Specter actively enforces the boundary that keeps your assessment scope small: request bodies carrying a raw card number (PAN) outside the designated credential field are rejected with a 422 validation error, and Interceptor payloads are scanned so raw card data never reaches your instance.The platform test-card policy applies on every instance: on the Test tier, decision requests accept only known test cards; on the Production tier, test cards are rejected. Violations return a 403 with a clear classifier.
​
New Release

​
Specter Is Live

Specter — the risk and fraud decisioning component of the Composable Payment Architecture — is now generally available on the Test and Production tiers. Evaluate payments against your own rulesets and get an allow, block, or review decision in real time. Integrate through the Decision API, or drop the Interceptor into your existing PSP traffic without changing your payment flow. External risk engines plug in through Link backends.Start with the overview and plans and access.