Skip to main content
This page covers fields specific to Tracer — Lerian’s real-time transaction validation engine. These fields are used across validation requests, rules, spending limits, and decision responses.

1. Validation requests


FieldDescriptionUsed in
requestIdClient-generated unique ID for idempotency and audit correlationTracer
transactionTypeType of transaction: CARD, WIRE, Pix, or CRYPTOTracer
subTypeTransaction subtype for additional context (e.g., debit, credit)Tracer
amountTransaction amount in cents (smallest currency unit, must be positive)Tracer
currencyISO 4217 currency code (3 uppercase letters)Tracer
transactionTimestampWhen the transaction occurred (RFC 3339 format with timezone)Tracer

2. Validation responses


FieldDescriptionUsed in
validationIdServer-generated unique identifier for the validation recordTracer
decisionValidation decision: ALLOW, DENY, or REVIEWTracer
reasonHuman-readable reason for the decisionTracer
matchedRuleIdsIDs of rules that matched and triggered the decisionTracer
evaluatedRuleIdsIDs of all rules that were evaluatedTracer
processingTimeMsProcessing time in millisecondsTracer
totalRulesLoadedTotal number of rules loaded for evaluationTracer
truncatedWhether the response was truncated due to size limitsTracer

3. Rules


FieldDescriptionUsed in
ruleIdUnique identifier for the ruleTracer
nameHuman-readable rule name (globally unique, max 255 characters)Tracer
descriptionRule purpose and logic explanation (max 1000 characters)Tracer
expressionCEL expression that must evaluate to boolean (max 5000 characters)Tracer
actionAction taken when the expression evaluates to true: ALLOW, DENY, or REVIEWTracer
scopesArray of scopes that determine which transactions this rule applies toTracer
statusRule lifecycle status: DRAFT, ACTIVE, INACTIVE, or DELETEDTracer
activatedAtWhen the rule was last activated (null if never activated)Tracer
deactivatedAtWhen the rule was last deactivated (null if never deactivated)Tracer

4. Spending limits


FieldDescriptionUsed in
limitIdUnique identifier for the limitTracer
nameHuman-readable limit name (max 255 characters)Tracer
descriptionLimit purpose and usage explanation (max 1000 characters)Tracer
limitTypeType of limit: DAILY, WEEKLY, MONTHLY, CUSTOM, or PER_TRANSACTION (immutable after creation)Tracer
maxAmountMaximum decimal amount as a string, for example "1000.00"Tracer
currencyISO 4217 currency code (immutable after creation)Tracer
scopesArray of scopes that determine which transactions this limit applies toTracer
statusLimit lifecycle status: DRAFT, ACTIVE, INACTIVE, or DELETEDTracer
activeTimeStartStart of the daily active window in HH:mm formatTracer
activeTimeEndEnd of the daily active window in HH:mm formatTracer
customStartDateStart date-time for CUSTOM limitsTracer
customEndDateEnd date-time for CUSTOM limitsTracer

5. Limit usage


FieldDescriptionUsed in
limitAmountTotal limit amount in centsTracer
currentUsageCurrent or projected usage after applying the transactionTracer
exceededWhether the limit was exceeded during validationTracer
periodLimit period type: DAILY, WEEKLY, MONTHLY, CUSTOM, or PER_TRANSACTIONTracer
scopeHuman-readable scope description (e.g., “account:uuid”, “segment:uuid”)Tracer
attemptedAmountTransaction amount being validated, in centsTracer

6. Scopes and targeting


FieldDescriptionUsed in
accountIdAccount identifier for scope targetingTracer
segmentIdSegment identifier for scope targetingTracer
portfolioIdPortfolio identifier for scope targetingTracer
merchantIdMerchant identifier for scope targetingTracer
transactionTypeTransaction type filter: CARD, WIRE, Pix, or CRYPTOTracer
categoryMerchant Category Code (4-digit MCC per ISO 18245)Tracer
countryMerchant country (ISO 3166-1 alpha-2, 2 uppercase letters)Tracer