KYC Tenure API: the “time signal” your onboarding is missing

Fraudsters are getting faster.

They create accounts, request credit, cash out incentives, or reroute payouts in minutes—often before your traditional KYC stack has even finished blinking. You can throw more document checks at the problem, but you’ll pay for it twice: in costs (manual review, vendor fees, exception handling) and in conversion (drop-off, false positives, frustrated customers).

So what’s the missing ingredient? Time.

Not the time it takes you to verify someonebut the time a mobile number has actually lived on the network.

That’s the purpose of Orange KYC Tenure API: a simple, high-signal check that answers a question your risk engine should be asking on day one:

“Is this phone number’s lifetime tenure older than the date (or threshold) my policy requires?”

KYC Tenure checks whether a phone number’s lifetime tenure is older than a customer-provided date helping you strengthen onboarding and authentication decisioning with a network-backed trust signal, and reduce exposure to synthetic identities and high-risk signups.

Why KYC Tenure matters (and why fraudsters struggle to fake it)

A fake document can be generated. A stolen identity can be replayed. A device fingerprint can be rotated.

But history is harder to fabricate at scale.

Many high-velocity attacks (mule accounts, instant-loan scams, promotional abuse) show the same pattern: they’re executed using fresh numbers, recently activated lines, or recently reassigned identities. Tenure acts as a silent discriminator between “established” and “newly-created-for-fraud” phone identities.

KYC Tenure gives you that signal programmatically, so you can make smarter decisions before money moves.

What the KYC Tenure API actually does (and what it doesn’t)

It does

• Verifies whether a phone number’s lifetime tenure exceeds a date you provide (e.g., “older than 90 days”).
• Uses historical anonymized data and Orange’s tenure analysis methods to produce an operational risk signal that supports onboarding, authentication decisioning, and fraud prevention.
• Is positioned for fraud prevention and trust use cases in digital identity journeys.

It doesn’t

• It is not proof of legal identity. It doesn’t confirm a person is who they claim to be; it indicates whether the number has sufficient “history/tenure.”
• It should not be used as a single “approve/deny” gate everywhere. Its best use is risk-based routing: fast-track trusted users, step-up checks for fresh numbers.

The high-impact use case: risk-based onboarding without the friction tax

When you treat onboarding like a single rigid funnel, you end up punishing good users to catch bad ones. Tenure lets you flip the model:

A practical decision pattern (that product and fraud teams can align on)

1. User enters phone number during signup / account opening / wallet creation.
2. Your backend calls KYC Tenure with a threshold aligned to the journey risk (e.g., stricter for credit/payouts than for low-risk signups).
3. If tenure is high enough:
   • fast-track the user through a lighter path
   • reduce manual review volume
   • lower dependence on intrusive step-up methods
4. If tenure is too short:
   • trigger stronger KYC
   • add step-up authentication
   • hold payouts or sensitive changes
   • optionally route to manual review

This is exactly how you turn a simple yes/no signal into a real operating lever: cost control, lower fraud exposure, and better conversion—at the same time.

Built for fraud teams, friendly for developers

KYC Tenure is designed to be straightforward to operationalize:

• Threshold-based outcome: easy to plug into policy engines and decision trees.
• Network-backed signal: rooted in network-level observation rather than user-declared data.
• Privacy and standards posture: Orange positions the API as CNIL/GDPR compliant and CAMARA certified, built on anonymized historical analysis.

And if you want to move fast before going live, Orange provides a Network APIs Playground to explore mocked CAMARA APIs (including KYC Tenure) and validate scenarios prior to production.

Where KYC Tenure fits in a modern anti-fraud stack

KYC Tenure API is strongest when combined with adjacent network signals:

• Number Verification: verify the phone number as a robust authentication component.
• SIM Swap: assess whether a SIM change happened recently (often used in account takeover).
• KYC Match: validate user identity attributes by matching them against operator KYC data—complementary to tenure’s “history” signal.

Orange explicitly positions Tenure + Match as complementary: KYC Tenure = risk indicator, KYC Match = identity consistency check.

Make “time” a first-class risk signal

Fraud teams don’t lose to fraudsters because they lack rules. They lose because their rules don’t have enough ground truth. KYC Tenure adds a network-backed, policy-friendly signal that’s:

• fast to interpret
• easy to integrate into decisioning
• effective at separating “fresh” identities from established ones
• usable without adding steps that hurt legitimate users

If your growth depends on digital onboarding, you don’t need more friction. You need better signals.

Explore the KYC Tenure API product details and documentation, and start validating your fraud policies with the Network APIs Playground.