CDQ Guards · Payment fraud prevention
Stop paying fraudulent accounts. Verify every payee before you release.
CDQ Fraud Guard verifies beneficiary bank accounts and scores their reliability from community-proven payment experience, so you release only validated accounts and catch fraud on the new or changed accounts that carry the highest risk.
Trusted by global enterprises
%20--%3e%3csvg%20version='1.1'%20id='Capa_1'%20xmlns='http://www.w3.org/2000/svg'%20xmlns:xlink='http://www.w3.org/1999/xlink'%20x='0px'%20y='0px'%20viewBox='0%200%202021%20628.6'%20style='enable-background:new%200%200%202021%20628.6;'%20xml:space='preserve'%3e%3cg%3e%3cpath%20d='M678.7,542.7c-15.1-0.4-28-12.8-28-28.1l0-501H485.7v552.3c0,27.1,21.9,49.2,48.8,49.2h288.6c27.1,0,48.8-22.1,48.8-49.2%20V13.6h-165l-0.2,501C706.8,529.9,693.9,542.3,678.7,542.7%20M1231.6,13.6H981.7c-29.6,0-53.7,24-53.7,53.9V615h165.3V112.8%20c0.1-15.4,12.6-27.6,27.9-27.6c15.4,0,27.8,11.9,28.2,27.1V615H1314V112.4c0.2-15.2,12.6-27.1,28-27.1c15.3,0,27.9,12.2,28,27.6%20V615h165.3V67.5c0-29.9-24.1-53.9-53.7-53.9L1231.6,13.6z%20M264.7,113.8c0.1-16.7-13.5-28.6-28-28.6h-28v304.2h28%20c14.6,0,28.1-11.6,28-28.2V113.8z%20M375.5,463.9H208.7V615h-165V13.6h332.9c29.8,0,53.1,24.2,53.1,54.2v341.9%20C429.6,439.7,405.5,463.9,375.5,463.9'/%3e%3cpath%20d='M1812.3,389.5V112.6c-0.4-15.3-12.7-27.1-28.1-27.1c-15.2,0-27.8,12.2-28,27.5v276.5L1812.3,389.5z%20M1812.3,615V464h-56.1%20v151h-165V67.5c0-29.9,24.1-53.9,53.7-53.9h278.7c29.6,0,53.7,24,53.7,53.9V615L1812.3,615z'/%3e%3c/g%3e%3c/svg%3e)
A collective trust signal no single company could build alone
There is no official directory mapping bank accounts to their true owners. Fraud Guard closes that gap by pooling anonymized payment experience across the CDQ Data Sharing Community.
- Millions
of proven, operationally validated accounts in the shared Bank Trust Pool
- 5 modules
feed each Trust Score: fraud alerts, payment experiences, prevalidation, tax-payer lists, macroeconomic data
- 4 steps
to a secure upload: register, upload, trigger import, check status
CDQ Guards
What Fraud Guard does
Payments run on whatever bank details a payee provides, and fraudsters exploit that with fake invoices, man-in-the-middle attacks, and altered account changes. Fraud Guard turns pooled, community-proven payment experience into explainable trust signals you can act on.
Bank Trust Score & fraud detection
Quantifies the reliability of a payee account from aggregated, community-proven payment experience, returning a low, medium, or high trust rating. Scores rise with repeated successful payments and drop immediately when a fraud alert is linked to an account, so you can release, block, or escalate.
Bank Account Prevalidation
Validates account ownership (name-to-account) before accounts enter onboarding, master-data, or payment workflows, orchestrating external prevalidation providers in a configurable cascade and adding tax-payer-list and macroeconomic signals into an enriched Trust Score.
Fraud Case Management
A shareconomy service that pools known fraud cases across participating companies and matches them against your Bank Account Data Mirror to raise automated, account-level fraud alerts — without ever exposing account-owner data.
Payment Fraud Alerts
Record an identified fraud attack and warn other community members. A customer-managed notification list of workspace-level email recipients is configured in CDQ Cloud Apps, so the right people are alerted the moment a threat is found.
Bank Trust Score monitoring
Continuously monitors business-partner bank data in your Data Mirror for Trust Score changes or matches against new fraud cases, delivering results via Process Log or email with historical tracking and automated alerts.
Data verification & Bank Trust Pool
Standardizes uploads of payment data (for example SAP REGUH detailed or aggregated) through the Bank Account Data Mirror into the anonymized Bank Trust Pool via UI and API, replacing fragmented manual whitelists with an auditable, secure workflow.
Why CDQ Fraud Guard
Static reference tables, manual whitelists, and siloed ERP checks cannot see across companies and cannot keep pace with account changes. Fraud Guard is built differently.
Community intelligence, not siloed checks
Conventional validation is trapped inside one company's tables and whitelists. Fraud Guard draws on the CDQ Data Sharing Community's pooled, operationally proven payment history — a collective trust signal no single company could build alone.
Scores that adapt to fraud in near real time
Manual, static processes cannot keep pace with new or changed accounts. The Bank Trust Score updates continuously from community usage and drops immediately when a fraud attempt is linked to an account — targeting exactly the high-risk cases whitelists miss.
Explainable signals, not black-box verdicts
Outcomes are aggregated into explainable, summarized trust signals with full traceability and audit-ready evidence, rather than binary approve or reject. Every validated record is traceable to its source.
You keep control, sharing stays private
You set thresholds to match your own risk appetite — strict for high-value vendor payments, flexible for refunds. All contributed payment data is anonymized, and a reciprocity principle means only members who share owner mappings receive owner details back.
How Fraud Guard works
Four steps take you from raw payment data to validated releases and continuous monitoring — with the pool getting stronger on every upload.
Populate the Bank Account Data Mirror
Upload bank-account master data and payment-protocol data (for example SAP REGUH, detailed or aggregated) via UI or API, or integrate the Business Partner Data Mirror. Every upload is standardized and anonymized before routing into the Bank Trust Pool.
Setup
Verify at onboarding and score
During vendor or customer setup and change, new or updated payee accounts are validated against the Bank Trust Pool. The Trust Score gives a quantified reliability rating, ownership can be verified across contributors, and validated payer–payee mappings are stored in master data.
At onboarding
Validate before payment release
Before a batch is released, payee accounts are checked again against Trust Scores and your thresholds. Unknown, low-trust, and Fraud-Guard-flagged accounts are held or escalated, so only validated accounts are released for payment.
Before release
Monitor and feed back
Each upload updates the Bank Trust Pool, and fraud alerts — fake invoices, man-in-the-middle attempts — are linked to accounts to dynamically adjust Trust Scores. Monitoring surfaces changes and matches via Process Log or email, and audit logs provide compliance evidence.
Continuous
Frequently asked questions
What master-data, finance, procurement, and compliance teams ask before rolling out Fraud Guard.
What is CDQ Fraud Guard?
It is a collaborative, network-backed service that verifies beneficiary bank accounts and scores their reliability. It pools anonymized payer–payee payment experience from the CDQ Data Sharing Community into a Bank Trust Pool and calculates a Bank Trust Score for each account, so you can prevent payments to fraudulent or unverified accounts and release only validated ones.
Who is it for?
Enterprise teams exposed to payment and supplier-account risk: risk and fraud prevention, finance and treasury, procurement, and master-data management, plus compliance auditors who need audit-ready proof of validation. It fits large multinationals handling high payment volumes across many countries.
How does it integrate with SAP and our existing systems?
Fraud Guard plugs into ERP, treasury, and compliance workflows, including SAP MDG and REGUH payment-protocol import, and connects to CRM and finance systems. You work through CDQ Cloud Apps or the REST API, backed by the Business Partner Data Mirror, so real-time checks run without disrupting existing processes.
How is our data kept secure and who stays in control?
All contributed payment data is anonymized before it enters the Bank Trust Pool, and fraud cases are matched without exposing account-owner data. Insights are proposed, never enforced: you set the thresholds and keep control of every release, hold, or escalate decision. A reciprocity principle means only members who share owner mappings receive owner details back, and every validated record is traceable to its source and time.
How do we get started?
Book a demo with a CDQ expert. We will walk through your payment and onboarding workflows, populate the Bank Account Data Mirror from your master and payment-protocol data, and configure Trust Score thresholds and monitoring to match your risk appetite.
Book a demo
See Fraud Guard verify your payees
Book a demo with a CDQ expert to see how the Bank Trust Score, community fraud alerts, and prevalidation work against your own onboarding and payment flows — and how quickly you can start releasing only validated accounts.
Book your CDQ demo
Pick a 30-minute slot — see Fraud Guard working on your own data.