AVAILABLE

Vendor Risk

Remittance Change Detect

Compare fingerprinted submitted details to a customer-controlled vendor baseline. It never claims bank-account ownership.

Start free workspaceOpenAPI →

CONTRACT

Predictable for agents. Legible for reviewers.

REST
POST /v1/vendors/{reference}/remittance-check
MCP tool
check_remittance_change
Inputs
A vendor reference, remittance reference, and a customer-generated account fingerprint.
Returns
CLEAR or REVIEW_REQUIRED, evidence of a detected change, and an out-of-band next action.
Latency
Synchronous
Usage unit
Remittance check

AGENT-READABLE EXCEPTIONS

REMITTANCE_DETAILS_CHANGED

EXAMPLE REQUEST

POST /v1/vendors/northstar/remittance-check
Authorization: Bearer apc_...
Content-Type: application/json

{
  "remittance_reference": "WIRE-NORTHSTAR-02",
  "account_fingerprint": "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb"
}

REPRESENTATIVE RESPONSE

{
  "vendor_id": "vendor_01...",
  "decision": "REVIEW_REQUIRED",
  "exceptions": [
    {
      "code": "REMITTANCE_DETAILS_CHANGED",
      "severity": "HIGH",
      "retryable": false,
      "message": "Submitted remittance details differ from the customer-controlled baseline.",
      "suggested_next_action": "Verify the change out of band.",
      "evidence": {
        "vendor_reference": "northstar"
      }
    }
  ],
  "next_action": "Pause the change and complete out-of-band verification."
}
Structured outputStatus, decision, exceptions, evidence, confidence, and next action where relevant.
Tenant-scopedOnly the caller's organization records are searched or returned.
Read-onlyNo accounting record, vendor bank account, or payment is changed.

Try Remittance Change Detect with your own workflow.

Start with the trial workspace, inspect the result, then integrate with REST or MCP.

Start free workspaceRead the integration guide →