For accounts payable, treasury and ERP integrators

The record at the moment of payment

Your payment run already has a rule for holding a wire. What it lacks is the dated record of what the official files printed for the payee at that moment — and what changed since the last time you looked. One call returns both. We do not hold payments and we do not flag payees; your rule does, and the receipt is the record of why it fired or did not.

One call, before funds release

POST https://alphacovenantholdings.com/api/batch/receipt
X-Api-Key: acv_…
{ "name": "Wellpath LLC", "uei": "JL99G1YPJKK9",
  "partner_reference": "wire-2026-10-03-0412",
  "since": "r_<previous receipt_id for this payee>" }

→ 201 { "receipt_id", "sha256", "checked_at",
        "since": { "changes": [ { "field": "sam.count", "old": 0, "new": 1, "source": "SAM.gov Exclusions…" } ],
                   "rows_now_for_changed_sources": { "sam": { "entries": [ … ] } },
                   "reads_as": "1 line differs from receipt r_… read 2026-09-03 …" },
        "did_not_answer": [], "not_read": [ … ], "receipt": { … } }

Keys beat names: UEI, CAGE, LEI, NPI, EIN. With a key the match is exact; with a bare name the receipt prints exact-printed-name rows as candidates for your reviewer. Fifteen seconds to two minutes: about twenty endpoints are queried live for each call, the rest are read from files we hold with their fetch date and SHA-256 printed — the receipt's source_telemetry block shows which was which and how long each took, so a slow or silent source is on the record, never hidden.

Your rule, written plainly

A typical release rule in SAP Ariba, Coupa, Tipalti, Kyriba or a nightly script: hold if any since.changes row raises a count on sam, leie, ofac, state, csl or uflpa, or if sam, leie or ofac is in did_not_answer. Route the hold to a named reviewer with the receipt id. Nothing in the receipt decides; your rule and your reviewer do, and the file shows what they saw.

Model procedure text for your AP manual: the Evidence Clause — AP payment run. Duty Sheet for the controller: ap-pre-disbursement.

What it is not

Not a circuit breaker, not real-time surveillance, not a sanctions screen with fuzzy matching, not a determination that a payee is eligible. The LEIE changes about monthly and the SAM extract daily; we re-read a payee when you ask and when a held file changes (public log). Treasury's Do Not Pay portal is agency-only and is not read.

Terms

Self-serve, by card, key issued at once: Basic $99/month — 5,000 single receipts (this call); Monitor $499/month — 50,000 calls including rosters and watches. Enterprise and state payment-run volume by annual agreement with the row limit printed on the key. The single free receipt stays free; billing never changes what a source returned.

Start — pay by card or try 25 rows free on /roster · spec: /api/batch/spec

For a year at a time: the Payment-Time API Agreement — 1,000,000 receipts, measured availability with written credits, the agreement text public.