DataSchutzHow CELT-UV works
A three-stage fraud prevention pipeline, running inside the payment gateway.
ITokenize
Wrap the payment in a one-time CELT-UV
The engine wraps the payment in a unique, one-time Cryptographic Ephemeral Limit Token — Upgraded Version. Dynamic spending limits and authorisation rules are bound directly to the token payload.
CELTUV_PAYLOAD {
token: ephemeral, single-use
spend_limit: dynamic
auth_rules: bound-to-payload
}
IIIngest
Five live vectors, evaluated pre-authorisation
The API is designed to ingest five live signals before a transaction is authorised, providing context about the session, device, location, transaction pattern and merchant.
App Behavior
Usage pattern match
Device
Integrity + ID check
Location
Geo consistency
Txn Pattern
Spend behaviour
Merchant
Risk score
IIIDecide
Interdict mid-transaction, or authorise
When risk signals exceed an institution’s configured threshold, the decision engine can support interdiction or additional controls. Transactions below that threshold can continue through the institution’s authorisation path.
VISUAL WALKTHROUGH · one transaction, start to finish
DECISION LOGIC
Authorisation path — no configured anomaly
Interdiction path — anomaly flagged pre-authorisation