# Confirm a payment reached the worker

> Confirm a payment reached the worker: 3 companies fully do it, 2 with a limit, 7 carry the tag. Every listing in Payroll infrastructure with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/payroll.payment-status/
- Markdown: https://www.anchorterminal.com/niches/payroll.payment-status/index.md (~1,100 tokens)
- Slim: https://www.anchorterminal.com/niches/payroll.payment-status/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/payroll.payment-status/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 3 | 2 | 7 | 12 | 3 |

## What counts as done

For each payment, a status from the vendor (pending, paid, returned or failed) with amount and pay date that matches what was sent, from the API or a signed webhook, and returned payments named with a reason.

How agents ask for it: did everyone get paid; has the driver's pay landed; which payments failed; mark this payment as paid

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Check (Check Technologies, Inc.)**: Payments carry attempts with paid, failed and refund states, failed attempts show detail and retry options, and payment webhooks are signed with HMAC-SHA-256 in Check-Signature.
- **Gusto (Gusto, Inc.)**: GET ACH transactions returns each payment's payment_status (unsubmitted, submitted, successful, failed), recipient, check date and an error_code, with ACH return codes documented.
- **Salsa (Salsa Software Inc.)**: Money movement exposes payment status (PENDING, AWAITING, COMPLETE, ON_HOLD, FAILED) and disbursement status including RETURNED, and webhooks carry a Webhook-Signature over id, timestamp and body.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Everee (Everee, Inc.)**: Net payouts read PENDING, PAID, RETURNED or SUPERSEDED with amount and send date, with signed, timestamped net-payout webhooks. acc-25 saw a payout stay PENDING for days after the payment was PAID, and acc-24 found payment history carried no payout status.
- **Zeal (Puzzl Group Inc.)**: Checks carry disbursement_status and the Transaction Update webhook reports processing, settled and returned with status_detail. The webhook 'signature' is the shared secret itself in Puzzl-Signature, not a signature of the payload.

- not this job: Argyle (Argyle Systems Inc.): Paystub destinations show where past pay went, but there is no payment the agent sent and no payout status to reconcile against.
- not this job: Employment Hero Payroll (Employment Hero Pty Ltd): GET payrun/{id}/payments lists bank payment lines (account, amount, lodgement reference) and an ABA file; there is no paid, pending or returned status, since the employer's bank moves the money.
- not this job: Finch (Profound Platform Inc. (dba Finch)): Finch reports past pay runs from the employer's system; it sends no payments and exposes no payout status.
- not this job: Paychex (Paychex, Inc.): Checks show processed or unprocessed with net pay and check date; no paid, pending or returned status for the deposit was found.
- not this job: PayFit (PayFit SAS): A monthly payment file can be downloaded; there is no per-payment status.
- not this job: Worklio (Worklio, Inc.): Webhooks cover payroll states up to Finalized and check-generation progress is readable, but no per-payment paid, pending or returned status was found.

## What stops agents finishing

- status endpoint omits payout state (acc-24)
- payout stays pending for days after the payment is paid (acc-25)

## Around it

Before: payroll.preview-and-approve. After: accounting.journal-entry, messaging.notify.

## Where this comes from

Weight 12 of 100 in Payroll infrastructure: 3 of 27 accounts (acc-24, acc-25, acc-12); all three hit a gap between the payment status and the bank payout

As data: https://www.anchorterminal.com/api/v1/use-cases/payroll.payment-status.json, or the MCP tool get_use_case with id payroll.payment-status. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
