/v1/payment-riskPayment Risk API
Evaluate an email address at the point a payment decision is being made. Designed for finance, fraud and payment approval workflows.
Common use cases
Check one email address
Send a JSON object containing email.
curl -X POST https://api.threatprevent.io/v1/payment-risk \
-H "Content-Type: application/json" \
-H "x-api-key: YOUR_API_KEY" \
-d '{"email":"accounts@example.com"}'{
"endpoint": "payment-risk",
"risk": "low",
"risk_score": 20,
"source_type": "payment_scan",
"target": "hashed-or-normalised-target",
"charged": true,
"is_free": false,
"unit_price_pence": 25,
"billable_units": 1,
"total_price_pence": 25,
"charged_from_credit_pence": 25,
"overage_pence": 0,
"remaining_credit_pence": 2475
}Interactive API explorer
Response will appear here.
/v1/payment-risk/bulkBulk Payment Risk
Submit up to 10,000 email addresss in one HTTP request. Billing is calculated by records processed.
curl -X POST https://api.threatprevent.io/v1/payment-risk/bulk \
-H "Content-Type: application/json" \
-H "x-api-key: YOUR_API_KEY" \
-d '{"emails":["accounts@example.com","finance@example.org","payee@example.net"]}'{
"results": [
{
"email": "accounts@example.com",
"risk": "low"
},
{
"email": "finance@example.org",
"risk": "medium"
},
{
"email": "payee@example.net",
"risk": "low"
}
],
"charged": true,
"is_free": false,
"unit_price_pence": 25,
"billable_units": 3,
"total_price_pence": 75,
"charged_from_credit_pence": 75,
"overage_pence": 0
}Interactive API explorer
Response will appear here.
Risk interpretation
No significant risk signal identified from the intelligence currently available.
A risk signal warrants additional review before making the decision.
Significant risk indicators are present and the decision should be escalated.
Escalate and independently verify before payment.
Review the payee and payment context before proceeding.
Proceed according to your normal payment controls.
Decision-support notice
Threat intelligence is time-sensitive and cannot provide visibility of every threat. Risk results should be used as an additional decision signal rather than as the sole control for critical business decisions.
