# RunOnProof UK Vendor Payment-Detail Change Continuous Authorization

> RunOnProof UK Vendor Payment-Detail Change Continuous Authorization is a paid API for AI agents from cdo-production.up.railway.app, paid per call via x402, $0.2/call, status unknown (last checked 2026-09-15).

Authorize a scoped, single-use UK vendor payment-detail change with company/sanctions controls and a fresh independent challenge before updating payee details.

## Facts

- Endpoint: POST https://cdo-production.up.railway.app/v1/gb/solutions/vendor-change-continuous-authorization
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/runonproof-uk-vendor-payment-detail-change-continuous-authorization-996ccdee
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EA40OZh3lJH12lJmXEXV2

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability runonproof-uk-vendor-payment-detail-change-continuous-authorization-996ccdee -d '<json body>'
```

Example prompt: I need to authorize a payment detail change for UK company 12345678 — the current payee fingerprint is 'fp-vendor-old-001' and the proposed one is 'fp-vendor-new-001'. The prior authorization reference is 'AUTH-2024-XYZ', the challenge type is BANK_PROVIDER_CONFIRMATION with reference 'CHK-REF-001' verified just now and valid until tomorrow, and the idempotency key is 'idem-key-20240601-001'. Can you get continuous authorization for this change?

## When to prefer this

Use this endpoint specifically when you need a continuous, scoped, single-use authorization for a UK vendor payment-detail change — particularly when you already have a prior authorization reference and a fresh independent challenge. It is distinct from a one-shot payment authorization and from initial onboarding checks. Prefer it when your compliance workflow requires an expiring authorization gate before updating payee details, with sanctions and Companies House controls applied at the moment of change rather than at onboarding.

## Known failure modes

- Challenge expired (valid_until in the past) — authorization refused
- Company number not found or invalid format — validation error
- Proposed payee fingerprint matches a sanctioned entity — authorization denied
- Prior authorization reference not recognized or already consumed — rejection
- Idempotency key mismatch between body and header — request rejected
- Challenge type not accepted for the requested change scope — error response
- Company has active sanctions flags — authorization blocked

## How this service works

Authorize a scoped UK vendor payment-detail change with current company/sanctions controls and a fresh independent challenge. Use before changing the payee, then continue monitoring through separate technical controls. The authorization is expiring and single-use.

## Output

Returns a scoped, single-use authorization decision indicating whether the proposed payee change is approved under current company and sanctions controls, along with an authorization reference, expiry timestamp, and details of the control checks performed. The authorization is time-limited and cannot be reused.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "change": {
   "type": "object",
   "required": [
    "company_number",
    "current_payee_fingerprint",
    "proposed_payee_fingerprint",
    "prior_authorization_reference",
    "challenge",
    "idempotency_key"
   ],
   "properties": {
    "challenge": {
     "type": "object",
     "required": [
      "type",
      "verified_at",
      "valid_until",
      "reference"
     ],
     "properties": {
      "type": {
       "enum": [
        "PREVIOUSLY_VERIFIED_BINDING",
        "BANK_PROVIDER_CONFIRMATION",
        "CUSTOMER_CONFIRMATION",
        "CHALLENGE"
       ]
      },
      "reference": {
       "type": "string",
       "maxLength": 200,
       "minLength": 1,
       "description": "Non-secret reference to the evidence held by the caller."
      },
      "valid_until": {
       "type": "string",
       "format": "date-time",
       "description": "Expiry of the caller/provider evidence; must be in the future."
      },
      "verified_at": {
       "type": "string",
       "format": "date-time",
       "description": "When the caller or provider verified the binding."
      }
     },
     "additionalProperties": false
    },
    "company_number": {
     "type": "string",
     "pattern": "^(?:(?:[A-Z]{2}|[0-9]{2})?[0-9]{6}|[0-9]{8})$",
     "description": "Companies House company number, including any two-letter prefix when applicable."
    },
    "idempotency_key": {
     "type": "string",
     "pattern": "^[A-Za-z0-9._:-]{8,120}$",
     "description": "Caller-generated key. Send the identical value in the Idempotency-Key header."
    },
    "current_payee_fingerprint": {
     "type": "string",
     "maxLength": 200,
     "minLength": 8,
     "description": "Opaque caller-generated fingerprint; never send raw bank-account details."
    },
    "proposed_payee_fingerprint": {
     "type": "string",
     "maxLength": 200,
     "minLength": 8,
     "description": "Opaque caller-generated fingerprint; never send raw bank-account details."
    },
    "prior_authorization_reference": {
     "type": "string",
     "maxLength": 200,
     "minLength": 1,
     "description": "Reference to the currently approved vendor/payee binding."
    }
   },
   "additionalProperties": false
  },
  "idempotency_key": {
   "type": "string",
   "pattern": "^[A-Za-z0-9._:-]{8,120}$",
   "description": "Caller-generated key. Send the identical value in the Idempotency-Key header."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/runonproof-uk-vendor-payment-detail-change-continuous-authorization-996ccdee/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from cdo-production.up.railway.app](https://www.zero.xyz/host/cdo-production.up.railway.app/llms.txt)