Payment Fraud Alerts

From CDQ
Capability/Payment Fraud Alerts
Jump to navigation Jump to search
Name Name of a concept, e.g. a data model concept. In contrast to terms, the name does not depend on a given context, e.g. a country-specific language. Payment Fraud Alerts (category: , sort rank: 540, product: Financial Risk Services)
Short description Informal and short human-readable definition of a concept. Alerts from peers for fraudulent bank accounts.
Description Informal and comprehensive human-readable definition of a concept. B2B invoice scams are on the rise, not by "Script Kiddies", but by professional networks, operating on a global scale. Fraudsters send falsified invoices from "real" vendors but with a fraudulent bank account. Payment fraud prevention requires high resources, e.g. big data analytics and “cold calls” at vendors to verify new or changed bank account data. If a Data Sharing peer uncovers a payment fraud (case or attempt), information is shared with community, immediately (at least the bank account which is used for the attack). Other Data Sharing peers receive this information, screen their open payments, and block suspicious transactions.
Release status The release status in terms of development progress or maturity of a product feature or a business capability.<br/><code>EMPTY</code> (0): No feature considered yet, just rough idea for capability.<br/><code>IDEA</code> (1): Just an idea, not yet designed in detail.<br/><code>DESIGN</code> (2): Software design ready, development not yet started.<br/><code>DEVELOPMENT</code> (3): Software development in progress.<br/><code>ALPHA</code> (4): First functional release, in terms of a Minimal Viable Product (MVP).<br/><code>BETA</code> (5): Tested by selected users.<br/><code>RC</code> (6): Release candidate, fully tested, not yet used in production by many customers.<br/><code>LIVE</code> (7): Used in production by customers, fully monitored and supported.<br/><code>DEPRECATED</code> (-1): End of life planned, but still available.<br/><code>EOL</code> (-2): End of life, historic service, no longer available.<br/><code>BROKEN</code> (-3): Service was used in production but is currently not available. However, CDQ tries to repair or reactivate it. LIVE
Use cases Not used in any use case
Apps No app provides this capability
APIs No API provides this capability

Features

Feature Short description Informal and short human-readable definition of a concept. Release status The release status in terms of development progress or maturity of a product feature or a business capability.<br/><code>EMPTY</code> (0): No feature considered yet, just rough idea for capability.<br/><code>IDEA</code> (1): Just an idea, not yet designed in detail.<br/><code>DESIGN</code> (2): Software design ready, development not yet started.<br/><code>DEVELOPMENT</code> (3): Software development in progress.<br/><code>ALPHA</code> (4): First functional release, in terms of a Minimal Viable Product (MVP).<br/><code>BETA</code> (5): Tested by selected users.<br/><code>RC</code> (6): Release candidate, fully tested, not yet used in production by many customers.<br/><code>LIVE</code> (7): Used in production by customers, fully monitored and supported.<br/><code>DEPRECATED</code> (-1): End of life planned, but still available.<br/><code>EOL</code> (-2): End of life, historic service, no longer available.<br/><code>BROKEN</code> (-3): Service was used in production but is currently not available. However, CDQ tries to repair or reactivate it.
Payment Fraud Attack Database CDQ Data Sharing community members disclose known fraud cases in a database and use this database to check if a given bank account was used for a known attack or if a given business partner was affected by an attack. LIVE
Payment Fraud Attack Disclosure Maintain an identified fraud attack in order to warn the other community members. BETA
Payment Fraud Attack Monitoring Peer-based alerts about uncovered payment fraud cases. BETA