Content-Type:      application/json
EM-Signature:      9f2a7c…            // HMAC-SHA256 of the raw body
EM-Event-Dialect:  everydaymoney@2026-08-01

# Sign the bytes as received. Parsing and re-serialising first will
# change them, and the signature will not match.
# Compare in constant time.

{ "error": { "code": "insufficient_funds",
            "message": "this payout needs 16.83; the wallet holds 4.20" } }

---
name: everydaymoney
description: Read payouts, balances and settlement statistics from EverydayMoney, and raise a case when a customer says a payment marked successful never arrived. Use for questions about payout status, failure rates, wallet balance, corridor pricing, or a specific transaction.
---

# EverydayMoney

Payouts into Africa, settled from a USDC wallet. This skill reads your
organisation's own data and can open a case about a payment.

## Credential

A personal access token, as `Authorization: Bearer <token>`. Create one in the
console under **Tokens**. Two things about it that matter here:

- **It expires.** Every token carries an expiry date; there is no permanent one.
  A 401 usually means it lapsed rather than that anything is wrong.
- **It cannot exceed the person who made it.** A token issued by somebody who
  cannot see live keys cannot see live keys either, whatever it asks for. If a
  request is refused, the answer is not a different endpoint — it is that this
  token was never allowed to do that.

Never print the token, echo it into a message, or write it to a file.

## Base URL

    https://api.everydaymoney.eu          production
    https://sandbox-api.everydaymoney.eu  sandbox

Test tokens behave identically against the sandbox.

## The full reference

    GET /openapi.json

Unauthenticated, and generated from the running service rather than written
beside it — so it describes the deployment answering you, not a document that
drifted. Fetch it when you need a field this skill does not mention, an exact
response shape, or the bounds on a query parameter. What is below is the useful
subset, not the whole surface.

**It does not say what *you* may do.** Every operation declares that a
credential is required; none of them declares which role satisfies it. Two
tokens reading the same document get different answers, because authority is a
property of the token and not of the endpoint. So a 403 is not a sign you called
the wrong thing — it is the answer.

The reference also omits the console and platform endpoints entirely. Those need
a browser session or a platform admin, so they are not doors this token can
open, and describing them would only invite you to knock.

## Amounts are strings

`"1250.00"`, never `1250.0`. Read them as decimals and never as floats — a
float cannot hold `0.1` exactly, and money that is nearly right is wrong. When
reporting a figure, quote it exactly as returned. Do not round, reformat, or
convert between currencies.

## What to call

### How are payouts doing?

    GET /v1/stats?days=7

Totals, per-country breakdown, failure reasons, open cases, and `funds_held`.
Prefer this over paginating payouts — it is one call and it is what the console
shows.

`funds_held` is the figure to lead with when somebody asks whether anything
needs attention. It counts payouts whose money left the wallet and has neither
been delivered nor come back. It is **not** the same as failures: a failure that
was reversed is closed business.

### Find one payout

    GET /v1/payouts?reference=invoice-4821    exact, by your own reference
    GET /v1/payouts?q=254712                  partial: phone, id, reference
    GET /v1/payouts/{id}

### What still needs chasing

    GET /v1/payouts?funds=held

The list a person actually wants when something has gone wrong. `held` means
out of the wallet, not delivered, not returned — and it does not resolve by
waiting.

### Money

    GET /v1/balance          available and reserved
    GET /v1/wallet/ledger    every movement, newest first

### Where we can pay, and what it costs

    GET /v1/corridors
    GET /v1/corridors/{country}/requirements?method=bank_account
    GET /v1/pricing

### A customer says the money never arrived

This is the one thing this skill writes.

    POST /v1/cases
    {
      "payout_id": "pay_…",
      "summary": "customer called, says nothing arrived, checked 14:00 Tue"
    }

`summary` is what the complainant said, in their words — not your paraphrase of
what you think happened. Add `detail` for anything structured they gave you: the
reference they quoted, when they checked, which branch they visited.

    GET  /v1/cases
    POST /v1/cases/{id}/resolve
    { "status": "upheld" | "rejected" | "investigating", "resolution": "…" }

Raising a case **never moves money**. It records that somebody disputes an
outcome we call successful, so a person can investigate. Do not tell anybody a
refund is on its way — you have not caused one and cannot.

Do not resolve a case you raised on a customer's word alone. `upheld` and
`rejected` are findings, and a finding needs somebody who looked.

## Attribution

If your harness knows which person asked, pass it:

    EM-On-Behalf-Of: alice@company.com

This is recorded for audit and is not verified. It does not grant anything and
never changes what a token may do.

## Rules

- **Never invent a figure.** If a call fails, say the call failed. A plausible
  number is worse than no number, because somebody will act on it.
- **Never state that money has moved** unless a payout's own status says so.
  `pending` is not `completed`.
- **Quote the reference somebody gave you** when reporting on a payout, so they
  can check it themselves.
- If asked to send a payout, decline and say why: this token reads and works
  cases; moving money is deliberately outside what any bot may do here.