Phone-risk (fraud) provider

A COD parcel that gets refused at the door costs you the delivery both ways. The phone-risk check asks a provider what a phone number’s courier delivery history looks like — how many parcels that number has accepted versus refused, across the BD courier networks — before you ship.

Like payments and couriers, this is a shared, versioned package: each adapter maps its vendor’s payload onto one canonical result and one risk band, so switching provider is a config change, never an edit.

What’s available

Setting value	Provider
bdcourier	BDCourier
courier_insights	Courier Insights

The settings

Setting	Purpose	Default	Where
fraud_provider	The phone-risk provider to use	blank → the deployment default, then the first with credentials	Settings → Providers
FRAUD_DEFAULT_PROVIDER	Deployment-wide default	"" (unset)	.env
fraud credentials	API key for the provider	—	Integrations (encrypted)

Wiring it up

1. In the admin, go to Settings → Integrations & providers → Phone-risk.
2. Pick a provider, paste its API key, and enable it.
3. Hit Test connection to confirm the credentials load.

Credentials are handled securely — and never echoed

The API key lives only in the encrypted Integrations store, and is never returned by any endpoint. The config only names which provider is active; the admin shows a masked hint (…1234), never the key.

What it actually does

When a COD order is placed, Nudova looks the customer’s phone up with the active provider and stores a risk result. The lookup is gated to COD — a prepaid order carries no COD-refusal risk, so it never spends a lookup — and it can never break an order: a flaky provider is logged, and the order still goes through.

The result becomes a 0–100 risk score (a phone with a poor delivery ratio scores high) that shows on the order and on Fraud review.

This is what makes the COD auto-hold work

The score is exactly what the COD guardrails compare against. Set a risk threshold (Setup wizard, or Settings) and a risky COD order is held automatically before anyone can book a courier for it. Without a fraud provider configured there is no score, so only the COD value limit can hold an order.

See COD & fraud review.

No provider configured?

That’s a supported state — nothing breaks. You simply get no risk score, so:

• Orders are never auto-held on risk (the COD value limit still works).
• Fraud review shows orders without a score to sort by.

Related: COD & fraud review · Courier providers · Payment providers.