Fraud
Allow, review or block before anything posts, with case management. About fraud scoring Live
- POST
/fraud/reportReport fraud on your own account - POST
/fraud/screening/{userReference}Screen a subject against third-party lists now - GET
/fraud/screening/{userReference}/historyA subject's screening history - GET
/fraud/screening/{userReference}/risk-stateThe current screening verdict the engine reads for this subject
POST Report fraud on your own account
POST /fraud/report
Opens a case and returns its reference immediately. Nigerian authorised-push-payment guidance gives the customer 24 hours to report (72 with justification) and obliges the institution to acknowledge within 24 hours quoting a unique case reference, then conclude the investigation within 14 days. The reference in this response is that acknowledgement, and both deadlines are returned with it.
Headers
| Name | Notes |
|---|---|
Authorization | Bearer token |
X-Tenant | Your tenant |
X-Environment | test or live |
Content-Type | application/json |
Example
Request body: CustomerFraudReportRequest · Response: CustomerFraudReportResponse
curl -X POST "https://api.bridgemoni.com/fraud/report" \
-H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
-H "X-Tenant: $BRIDGEMONI_TENANT" \
-H "X-Environment: $BRIDGEMONI_ENV" \
-H "Content-Type: application/json" \
-d '{
"caseType": "APP_FRAUD",
"narrative": "March payroll",
"reportChannel": "text",
"disputedTransactionReferences": [
"text"
]
}' {
"caseType": "APP_FRAUD",
"narrative": "March payroll",
"reportChannel": "text",
"disputedTransactionReferences": [
"text"
]
} {
"data": {
"reference": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e",
"caseNumber": "text",
"status": "OPEN",
"reportedAt": "2027-03-14T14:30:01",
"acknowledgementDueAt": "2027-03-14T14:30:01",
"investigationDueAt": "2027-03-14T14:30:01"
},
"description": "Report fraud on your own account"
} Responses
| Status | When |
|---|---|
200 | Fraud report received |
POST Screen a subject against third-party lists now
POST /fraud/screening/{userReference}
Runs synchronously, for an analyst who needs an answer during an investigation. Every account holder is already screened automatically at registration and rescreened on a schedule - this is for when that is not soon enough.
Headers
| Name | Notes |
|---|---|
Authorization | Bearer token |
X-Tenant | Your tenant |
X-Environment | test or live |
Path parameters
| Name |
|---|
userReference |
Example
Response: ScreeningResultResponse
curl -X POST "https://api.bridgemoni.com/fraud/screening/b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e" \
-H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
-H "X-Tenant: $BRIDGEMONI_TENANT" \
-H "X-Environment: $BRIDGEMONI_ENV" {
"data": {
"reference": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e",
"userReference": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e",
"decision": "CLEAR",
"providerCode": "provider code",
"matchCount": 1,
"highestMatchScore": 1,
"listNames": [
"text"
],
"politicallyExposed": true,
"adverseMedia": true,
"screenedAt": "2027-03-14T14:30:01"
},
"description": "Screen a subject against third-party lists now"
} Responses
| Status | When |
|---|---|
200 | Screening completed |
GET A subject's screening history
GET /fraud/screening/{userReference}/history
Append-only and newest first, so what was known at any past moment can be established rather than inferred from the current state.
Headers
| Name | Notes |
|---|---|
Authorization | Bearer token |
X-Tenant | Your tenant |
X-Environment | test or live |
Path parameters
| Name |
|---|
userReference |
Example
Response: List<ScreeningResultResponse>
curl -X GET "https://api.bridgemoni.com/fraud/screening/b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e/history" \
-H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
-H "X-Tenant: $BRIDGEMONI_TENANT" \
-H "X-Environment: $BRIDGEMONI_ENV" {
"data": [
{
"reference": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e",
"userReference": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e",
"decision": "CLEAR",
"providerCode": "provider code",
"matchCount": 1,
"highestMatchScore": 1,
"listNames": [
"text"
],
"politicallyExposed": true,
"adverseMedia": true,
"screenedAt": "2027-03-14T14:30:01"
}
],
"description": "A subject's screening history"
} Responses
| Status | When |
|---|---|
200 | Screening history retrieved successfully |
GET The current screening verdict the engine reads for this subject
GET /fraud/screening/{userReference}/risk-state
Headers
| Name | Notes |
|---|---|
Authorization | Bearer token |
X-Tenant | Your tenant |
X-Environment | test or live |
Path parameters
| Name |
|---|
userReference |
Example
Response: SubjectRiskStateResponse
curl -X GET "https://api.bridgemoni.com/fraud/screening/b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e/risk-state" \
-H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
-H "X-Tenant: $BRIDGEMONI_TENANT" \
-H "X-Environment: $BRIDGEMONI_ENV" {
"data": {
"userReference": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e",
"sanctionMatch": true,
"politicallyExposed": true,
"adverseMedia": true,
"highestMatchScore": 1,
"lastScreenedAt": "2027-03-14T14:30:01",
"nextScreenDueAt": "2027-03-14T14:30:01",
"screeningStale": true,
"manualRiskOverride": "NONE"
},
"description": "The current screening verdict the engine reads for this subject"
} Responses
| Status | When |
|---|---|
200 | Risk state retrieved successfully |
Generated from the OpenAPI document. Branch on the HTTP status: there is no machine-readable error code on the wire. Errors