Is the rule engine different for each industry?
No — every industry example uses the same rule engine: vaults, per-agent budgets, and plain-language rules that resolve to ALLOW, ASK A PERSON, or BLOCK. What changes per industry is which conditions a company sets (a PO match, a signed brief, a warehouse scan, a statement match, currency, time of day), not the underlying mechanism.
What happens to a payment request the rules don't cover?
It's blocked by default. Rules are checked top to bottom and the first match wins — fraud checks like a bank-detail change or a duplicate invoice are checked first, then amount tiers, then other domain rules. Anything not explicitly covered is blocked, not allowed by default.
Can an AI agent ever hold a company card number or bank login?
No. An agent requests a payment; a credential — a single-use virtual card locked to a specific payee and amount, or a bank transfer — is only issued after the rules and any required approval clear. The agent never sees a reusable card number or bank login.
Are these 10 industries running on real customer data?
No. Pink Agentic AI Payments is in early access with a front-end prototype and working rule engine. The illustrative numbers, sample companies, and example logs in each industry page are prototype sample data, not real customers or real transactions.