FAQ
Questions that come up on the first technical call.
Does Saifuro see card data?
No. Credentials are tokenized at the edge, so card numbers never reach our systems. Substitution on the settlement path is performed by the VGS proxy, not by Saifuro. Funds do not reach us either: settlement is executed by licensed payment providers.
Can I deploy it myself?
No. Saifuro is a closed product delivered through direct implementation, and integration tooling is issued at onboarding. See getting access.
What happens if Saifuro is unavailable?
Failure mode is set by policy, per class of operation. Critical categories fail closed by default. You can choose to fail open for selected classes, and that choice is stored in the policy and visible in the log.
How is this different from spending limits at my payment provider?
Provider limits attach to an account or a card. If your agents use three providers, you maintain three sets of rules and reconcile them by hand.
A Saifuro mandate attaches to an agent and a principal, applies across providers, and leaves a decision log with the policy version attached to every verdict.
How fast can an agent's authority be revoked?
On the next request. Revoking a mandate needs no change to the agent's code and no action at the provider: the next call comes back deny_revoked.
Who owns the data and the log?
You do. The log is exportable at any time. Agent conversation content is not collected.
Which protocols and providers are supported?
Saifuro works through your existing payment providers and does not ship its own rail.
On the protocol side we track the agentic payment standards as they settle: AP2 for authorization and proof of intent, ACP for agent checkout, x402 and MPP for machine to machine settlement. Tracking is not support. A specific protocol is named here when the integration reaches production, under the same status rule as everything else in this documentation.
One provider adapter is running in production today. It is named under NDA on request, and it will be listed here once that provider approves being named. Adapters for the providers you already use are built during implementation. What the rule looks like in practice: VGS handles card tokenization in production and is named on the security page because it approved that.