---
type: "post"
id: "putting-a-transformer-inside-every-card-authorization-analysis-5b20e0"
slug: "putting-a-transformer-inside-every-card-authorization-analysis-5b20e0"
title: "Putting a Transformer Inside Every Card Authorization"
description: "Ramp says its card transformer reads each cardholder’s previous transactions in real time, on every card authorization."
retrieval_nugget: "Ramp says its card transformer reads each cardholder’s previous transactions in real time, on every card authorization."
published_at: "2026-10-08"
updated_at: "2026-10-08"
record_date: "2026-10-08"
date_kind: "published_at"
topics: []
source_urls: ["https://builders.ramp.com/post/sequence-aware-card-fraud"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:putting-a-transformer-inside-every-card-authorization-analysis-5b20e0"
status: "published"
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:5004a477bbf2ce891458b30a671c4d749245380866e51749ae15bcb818575123","reviewed_at":"2026-10-08T08:02:40.023Z","source_evidence_count":1,"verified_claim_count":2,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":2,"implication_count":1,"watch_condition_count":1,"related_record_count":0}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"Transaction history can make card-authorization fraud scoring more selective without increasing the number of flagged transactions.","observed_facts":[{"text":"Ramp says its card transformer reads each cardholder’s previous transactions in real time, on every card authorization.","source_urls":["https://builders.ramp.com/post/sequence-aware-card-fraud"]},{"text":"Ramp reports that the model ranks fraud 14% better than its predecessor and caught 32% more fraud dollars while flagging the same number of transactions.","source_urls":["https://builders.ramp.com/post/sequence-aware-card-fraud"]}],"mechanism":"A transformer processes each cardholder’s prior transactions at authorization time, allowing the model to score a new purchase in sequence context.","why_now":"Ramp has published comparative outcome figures for this real-time approach, making the claimed trade-off between detection and flag volume concrete.","implications":["The relevant operational measure is not only how many transactions a model flags, but how much fraud value those flags capture."],"evidence_boundary":"These performance figures are reported by Ramp; the source does not provide independent validation or establish that the results generalize to other issuers or systems.","watch_conditions":["Look for independently reported results, or deployment details showing how the model performs across different portfolios and over time."],"related_records":[],"new_branch_reason":"No prior New Runtime record is supplied for this specific Ramp card-authorization model and its reported comparison, so it merits a distinct analytical record."}
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/putting-a-transformer-inside-every-card-authorization-analysis-5b20e0/","markdown":"https://newruntime.com/posts/putting-a-transformer-inside-every-card-authorization-analysis-5b20e0.md","json":"https://newruntime.com/posts/putting-a-transformer-inside-every-card-authorization-analysis-5b20e0.json"}
---

# Putting a Transformer Inside Every Card Authorization

## Retrieval answer

Ramp says its card transformer reads each cardholder’s previous transactions in real time, on every card authorization.

Ramp says its card transformer reads each cardholder’s previous transactions in real time, on every card authorization. The source describes a model that evaluates a transaction in the context of an individual history rather than treating each authorization as an isolated event. Ramp reports that the model ranks fraud 14% better than its predecessor and caught 32% more fraud dollars while flagging the same number of transactions.

Thesis: Transaction history can make card-authorization fraud scoring more selective without increasing the number of flagged transactions. Mechanism: A transformer processes each cardholder’s prior transactions at authorization time, allowing the model to score a new purchase in sequence context. Why now: Ramp has published comparative outcome figures for this real-time approach, making the claimed trade-off between detection and flag volume concrete. For payment operators, the reported result suggests that richer contextual scoring may improve the yield of a fixed review or flagging burden.

Evidence boundary: These performance figures are reported by Ramp; the source does not provide independent validation or establish that the results generalize to other issuers or systems. First implication: The relevant operational measure is not only how many transactions a model flags, but how much fraud value those flags capture. First watch condition: Look for independently reported results, or deployment details showing how the model performs across different portfolios and over time.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)