Payments and scams

Money going out and coming in: scam payments, vendor bank-detail fraud, incoming credits and check deposits. Ready-to-run Grayson recipes with real responses, cost and latency.

RecipeDecidesCost per 1,000 decisionsLatency (US-West)
Detect business email compromise in vendor paymentsCatch payments to a vendor's new bank account after a fake or compromised change request.$0.57 to $0.60221 to 284 ms
Detect check fraud in mobile and branch depositsRelease, hold or reject a check deposit that may be counterfeit, altered, stolen or a duplicate.$0.52 to $0.80212 to 291 ms
Detect fraudulent incoming ACH credits and transfersRelease, hold or return an incoming credit that may be proceeds of BEC, account takeover or payroll diversion.$0.47 to $0.76192 to 312 ms
Stop scam payments before they're sentCatch authorised push payment scams in the payment flow, and choose release, warn, hold and call, or block.$0.45 to $0.62210 to 255 ms

Each recipe has three examples with a realistic, detailed state: one with obvious fraud signals, one that is very likely legitimate, and one that is ambiguous. Cost is for those requests at $0.035 per million input tokens. Latency is the median of several calls of each through api.finic.ai from US-West; add your own network time from elsewhere.

See every category on the Recipes page.