Skip to content

Commit 9a990c5

Browse files
authored
Merge pull request #80 from Telefonica/adritid/tenure-samplecode-yaml-realoc
feat: add Tenure API landing page and sample code and relocate OpenAPI specs - Age Verify Landing - Scam Signal landing
2 parents cbee30e + bec0528 commit 9a990c5

File tree

7 files changed

+517
-2
lines changed

7 files changed

+517
-2
lines changed

.github/workflows/rdme-guides-openapi.yml

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -111,9 +111,13 @@ jobs:
111111
- name: Run `openapi` command 🚀
112112
uses: readmeio/rdme@v10
113113
with:
114-
rdme: openapi --file=./v0/catalog/knowyourcustomer/kyc_age_verification_openapi.yaml --key=${{ secrets.README_API_KEY }} --id=686d430f5c2fd20018ce7556
114+
115+
rdme: openapi ./v0/catalog/ageverification/kyc_age_verification_openapi.yaml --key=${{ secrets.README_API_KEY }} --id=686d430f5c2fd20018ce7556
116+
115117

116118
- name: Run `openapi` command 🚀
117119
uses: readmeio/rdme@v10
118120
with:
119-
rdme: openapi --file=./v0/catalog/knowyourcustomer/kyc_tenure_openapi.yaml --key=${{ secrets.README_API_KEY }} --id=6874e6f254f6aa3161e0c45b
121+
122+
rdme: openapi --file=./v0/catalog/knowyourcustomer/kyc_tenure_openapi.yaml --key=${{ secrets.README_API_KEY }} --id=6874e6f254f6aa3161e0c45b
123+
Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
---
2+
title: Age Verification API
3+
excerpt: The Age Verification API enables businesses to verify if users meet required age thresholds for age-restricted services using verified data from mobile network operators, ensuring compliance with regulations while protecting privacy.
4+
category: 681879c3afc1a0003709c745
5+
---
6+
7+
The standardized Age Verification API allows businesses to determine if users meet required age thresholds for accessing age-restricted subscriptions and services using verified data from mobile network operators.
8+
9+
This API is essential in regulated sectors such as online gambling, alcohol sales, or digital media with age restrictions, helping to block unauthorized access and eliminate fake accounts. The Age Verification API enables this verification privately and in real-time.
10+
11+
> 📘 Want to give it a try?
12+
> Apply to join the [Developer Hub](https://opengateway.telefonica.com/en/developer-hub/join) and gain access to our Sandbox.
13+
14+
15+
16+
## Overview of the Age Verification API
17+
18+
### High level definition
19+
20+
The Age Verification CAMARA API is a software interface that enables businesses to verify if a user meets a specified age threshold by leveraging verified data collected and maintained by mobile network operators during SIM card registration or customer account setup.
21+
22+
### API Operations
23+
24+
The Age Verification CAMARA API specifies one operation:
25+
26+
- **POST /verify**: Verifies that the age of the subscriber associated with a phone number is equal to or greater than the specified age threshold value. The response may optionally include additional information such as identity match score, verified status, content lock, and parental control information.
27+
28+
[Check the API Reference](https://developers.opengateway.telefonica.com/reference/verifyage)
29+
30+
## Why Age Verification?
31+
32+
The Age Verification API helps businesses identify age thresholds of mobile line users in real-time, ensuring compliance with regulatory requirements while maintaining user privacy and streamlining verification processes.
33+
34+
### Process Simplification
35+
36+
Eliminates the need for users to submit identification photos or undergo biometric controls during initial interactions by leveraging verified data from mobile operators to confirm age instantly. This reduces friction in user onboarding while maintaining security and compliance.
37+
38+
### Trust and Traceability
39+
40+
Leverages data collected and verified by mobile operators during SIM card registration or customer account setup. This ensures age confirmation is based on a reliable, law-compliant source rather than user-provided data, reducing the risk of fraud and false information.
41+
42+
### Real-time Verification
43+
44+
Ideal for user verification, access control, and handling large transaction volumes without the common problems associated with document or image verification. Provides instant results that can be integrated into existing workflows seamlessly.
45+
46+
### Configurable Thresholds
47+
48+
The API allows adjustment of minimum age requirements (such as 18 or 21 years) according to business needs, industry requirements, or local laws. Verifications adapt to each market and include user-defined filters to improve accuracy and avoid incorrect results.
49+
50+
### Standardized Access
51+
52+
The CAMARA-standardized Age Verification API enables single integration to work with operators worldwide, without the need for custom agreements. This standardization simplifies development and reduces integration complexity across multiple markets.
53+
54+
### Privacy by Design
55+
56+
Uses only necessary data: indicates whether a person meets the minimum age requirement (e.g., 18 years) without sharing their birth date, documents, or other personal data. This better protects confidential information while ensuring compliance with privacy regulations.
57+
58+
### Enhanced Security Features
59+
60+
The API can optionally provide additional security information including:
61+
62+
- **Identity Match Score**: Indicates confidence level in the verification result
63+
- **Verified Status**: Shows if information has been verified against legally accepted identification documents
64+
- **Content Lock**: Indicates if the subscription has content filtering enabled
65+
- **Parental Control**: Shows if parental control features are activated
66+
67+
### Fraud Prevention
68+
69+
By utilizing verified operator data rather than user-submitted information, the API significantly reduces the risk of identity fraud, synthetic identities, and account manipulation commonly associated with traditional age verification methods.

v0/catalog/knowyourcustomer/kyc_age_verification_openapi.yaml renamed to v0/catalog/ageverification/kyc_age_verification_openapi.yaml

File renamed without changes.
Lines changed: 153 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,153 @@
1+
---
2+
title: Scam Signal API
3+
excerpt: The Scam Signal API provides advanced fraud detection capabilities leveraging telco network intelligence to identify and prevent fraudulent activities in real-time, protecting businesses and their customers from evolving threats.
4+
category: 681879c3afc1a0003709c745
5+
---
6+
7+
The Scam Signal API leverages mobile network operator intelligence to detect and prevent Authorized Push Payment (APP) fraud in real-time. By analyzing network patterns during transaction attempts, this API enables financial institutions to identify when customers are under active social engineering pressure and intervene before fraud completion.
8+
9+
Specifically designed for the critical detection window between fraud initiation and payment completion, Scam Signal has demonstrated proven effectiveness with early deployments reporting up to **41% reduction in successful scams** and **44% decrease in fraud losses**.
10+
11+
> 📘 Want to learn more about implementation?
12+
> [Contact our Expert Team](https://opengateway.telefonica.com/contactoexperto) to discuss technical implementation details and access requirements.
13+
14+
## Overview of the Scam Signal API
15+
16+
### High level definition
17+
18+
The Scam Signal CAMARA API provides real-time fraud detection by analyzing telco network signals to identify when customers are being manipulated during payment transactions. The API enables financial institutions to detect ongoing social engineering attacks and implement immediate protective measures.
19+
20+
### API Operations
21+
22+
The Scam Signal API delivers risk assessment capabilities through secure endpoints that analyze network metadata without accessing call content, ensuring privacy compliance while detecting fraud indicators.
23+
24+
**Available through expert consultation:**
25+
- Real-time fraud scoring methodologies
26+
- Integration patterns for existing fraud prevention systems
27+
- Customization options for specific use cases and risk thresholds
28+
- Performance benchmarks and accuracy metrics
29+
30+
## Why Scam Signal?
31+
32+
Traditional fraud detection systems struggle against Authorized Push Payment (APP) fraud because victims authorize legitimate transactions while under social engineering manipulation. Scam Signal addresses this critical gap by detecting the manipulation itself during the transaction window.
33+
34+
### Authorized Push Payment Fraud Targeting
35+
36+
APP fraud encompasses sophisticated social engineering attacks where criminals manipulate victims into authorizing payments to fraudulent accounts:
37+
38+
- **Bank Impersonation**: False security alerts requiring immediate fund transfers
39+
- **CEO Fraud**: Business email compromise targeting corporate finance teams
40+
- **Investment Scams**: Fake opportunities requiring urgent investment payments
41+
- **Romance Fraud**: Manipulated relationships leading to financial requests
42+
- **Vendor Impersonation**: Fake suppliers demanding payment redirections
43+
44+
### How APP Fraud Unfolds
45+
46+
Authorized Push Payment fraud operates through sophisticated social engineering where criminals manipulate victims during live interactions:
47+
48+
1. **Initial Contact**: Fraudsters impersonate trusted entities (banks, government agencies, family members) via phone, email, or messaging
49+
2. **Psychological Pressure**: Create urgency through fake emergencies, security alerts, or time-sensitive investment opportunities
50+
3. **Transaction Coaching**: Guide victims through legitimate banking processes while maintaining psychological control
51+
4. **Real-time Manipulation**: Continue coaching during payment execution to overcome security prompts and verification steps
52+
53+
**Critical Detection Window**: The period between fraud initiation and payment completion represents the optimal intervention opportunity.
54+
55+
### Real-time Detection Capabilities
56+
57+
**Live Fraud Identification**: Analyzes network signals to detect ongoing social engineering during payment attempts, enabling immediate intervention before transaction completion.
58+
59+
**Network Intelligence**: Leverages unique telco insights including call patterns, device behavior, and network metadata to identify manipulation indicators without accessing conversation content.
60+
61+
**Enhanced Fraud Models**: Integrates telco intelligence with existing fraud prevention systems, reducing false positives by **55%** while improving detection accuracy against sophisticated social engineering attacks.
62+
63+
**Adaptive Learning**: Continuously evolves to recognize new fraud patterns and criminal methodologies, staying ahead of emerging social engineering tactics.
64+
65+
**Privacy-Compliant Analysis**: Processes network metadata without accessing call content or personal communications, ensuring regulatory compliance while maintaining detection effectiveness.
66+
67+
### Implementation Scenarios
68+
69+
**Retail Banking Transaction Flow**:
70+
When a customer initiates a high-value or unusual transfer, the bank's fraud system queries Scam Signal API to analyze concurrent network activity. If scam indicators are detected, the system can:
71+
- Immediately pause the transaction pending verification
72+
- Display targeted fraud awareness messages
73+
- Redirect customers to secure verification channels
74+
- Trigger human agent intervention protocols
75+
76+
**Corporate Banking Protection**:
77+
Wire transfer requests showing scam indicators automatically initiate enhanced verification procedures. For example, when a finance officer receives an "urgent CEO directive" for immediate payment, the system detects manipulation signals and suggests mandatory call-back verification using predetermined contact methods.
78+
79+
**Payment Platform Integration**:
80+
Mobile payment apps, digital wallets, and peer-to-peer transfer services integrate real-time scam detection into existing fraud prevention workflows, enabling dynamic risk scoring adjustments based on social engineering indicators.
81+
82+
### Advanced Security Features
83+
84+
**Multi-Vector Analysis**: Combines network intelligence with transaction patterns, device behavior, and timing analysis to create comprehensive fraud risk profiles.
85+
86+
**Dynamic Risk Scoring**: Adjusts fraud confidence levels in real-time based on evolving network signals and behavioral indicators during transaction attempts.
87+
88+
**Intervention Flexibility**: Provides configurable response options from soft warnings to hard transaction blocks, allowing institutions to balance security with customer experience.
89+
90+
**Cross-Channel Protection**: Monitors fraud indicators across voice calls, SMS, messaging apps, and other communication channels used in social engineering attacks.
91+
92+
## Proven Business Impact
93+
94+
### Quantified Results
95+
Early deployments in UK financial institutions demonstrate significant fraud reduction:
96+
- **41% reduction** in successful scam completions
97+
- **44% decrease** in financial fraud losses
98+
- **55% fewer false positives** improving operational efficiency
99+
100+
### Integration Benefits
101+
102+
**Real-time Protection**: Immediate intervention at the critical moment of fraud attempt, during the narrow window between manipulation and payment completion.
103+
104+
**Enhanced Accuracy**: Reduces false positives while improving genuine fraud detection through unique telco intelligence unavailable to traditional fraud prevention systems.
105+
106+
**Operational Efficiency**: Focuses human review resources on genuine threats rather than false alarms, improving fraud team productivity and response times.
107+
108+
**Customer Experience**: Protects legitimate customers from sophisticated manipulation while maintaining smooth transaction flows for authentic payments.
109+
110+
**Regulatory Compliance**: Supports PSD2 Strong Customer Authentication, AML requirements, and emerging APP fraud prevention regulations across multiple jurisdictions.
111+
112+
**Seamless Deployment**: RESTful API design enables integration with existing fraud prevention platforms, transaction monitoring systems, and decisioning engines without infrastructure changes.
113+
114+
### Target Industries
115+
116+
**Financial Services**: Banks, credit unions, and payment processors requiring enhanced APP fraud protection during money transfers and high-risk transactions.
117+
118+
**Fintech Platforms**: Mobile payment applications, digital wallets, and peer-to-peer services seeking advanced fraud detection capabilities.
119+
120+
**Corporate Banking**: Enterprise treasury management systems protecting against business email compromise and vendor impersonation fraud targeting corporate accounts and supplier payment processes.
121+
122+
### Fraud Prevention Ecosystem Integration
123+
124+
Scam Signal enhances existing fraud prevention capabilities by adding unique telco intelligence that complements traditional detection methods:
125+
126+
**Enhanced with Other Open Gateway APIs**:
127+
- **SIM Swap Detection**: Identify recent SIM changes that may indicate account compromise
128+
- **Number Verification**: Confirm device ownership during suspicious transaction attempts
129+
- **Device Location**: Validate geographic consistency with expected user patterns
130+
- **KYC Match**: Cross-reference identity verification data for additional fraud indicators
131+
132+
**Traditional Fraud Tool Enhancement**:
133+
- **Behavioral Analytics**: Add social engineering pressure indicators to user behavior models
134+
- **Transaction Monitoring**: Enrich payment risk scoring with real-time communication analysis
135+
- **Identity Verification**: Supplement know-your-customer processes with live manipulation detection
136+
- **Risk Scoring Engines**: Integrate telco intelligence for more accurate fraud probability calculations
137+
138+
### Regulatory and Compliance Framework
139+
140+
**PSD2 Compliance**: Supports Strong Customer Authentication requirements by providing additional fraud risk indicators during payment initiation and authorization processes.
141+
142+
**AML Enhancement**: Contributes to Anti-Money Laundering programs by detecting social engineering patterns often associated with money mule recruitment and transaction layering schemes.
143+
144+
**Data Protection**: Operates within GDPR and other privacy frameworks by analyzing network metadata without accessing personal communications content or sensitive customer information.
145+
146+
**Industry Standards**: Built following GSMA Open Gateway standards and CAMARA API specifications, ensuring consistent implementation across global mobile network operators.
147+
148+
## Technical Implementation
149+
150+
Due to the sophisticated nature of fraud detection algorithms and the need to maintain effectiveness against evolving criminal tactics, technical implementation details are available exclusively through direct expert consultation.
151+
152+
> 💡 **Ready to enhance your fraud prevention capabilities?**
153+
> [Schedule a Technical Consultation](https://opengateway.telefonica.com/contactoexperto) with our Open Gateway team to discuss implementation requirements, integration patterns, and performance metrics tailored to your specific use case.
File renamed without changes.

0 commit comments

Comments
 (0)