bee.charge.vales_applied

Vales were applied to a bee charge - the other of the two facts a merchant cares about, alongside bee.charge.settled. Same deterministic-eventId idempotency contract.

Senders

• bee

Receivers

• hoja

Data schema

Each field maps to a type hint. | null indicates an optional field.

{
  "chargeRequestId": "string",
  "externalRef": "string | null",
  "cellId": "string",
  "communityId": "string",
  "status": "string",
  "totalCents": "number",
  "valesAppliedCents": "number",
  "cashCents": "number | null",
  "settledAt": "string (ISO datetime) | null",
  "occurredAt": "string (ISO datetime)"
}

Example payload

The following is a synthetic payload that matches the schema. Production payloads are signed with HMAC-SHA256 and delivered to each receiver's registered webhook endpoint.

{
  "chargeRequestId": "example-chargeRequestId",
  "externalRef": "example-externalRef",
  "cellId": "example-cellId",
  "communityId": "example-communityId",
  "status": "example-status",
  "totalCents": 0,
  "valesAppliedCents": 0,
  "cashCents": 0,
  "settledAt": "2026-04-17T12:00:00.000Z",
  "occurredAt": "2026-04-17T12:00:00.000Z"
}

See also

• Events registry index
• Webhooks integration guide
• Errors & retries

---

Generated from ecosystem-sdk/packages/mcp-server/src/registry/events.json. Do not edit by hand.