slug: accrue-savings
provider: Accrue Savings
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 4
edges:
- tag: Webhooks
  spec_file: accrue-savings-webhooks-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.85
  evidence: '"Create a webhook", "Update a webhook", "Delete a webhook"; schema "InvalidWebhookTopicsResponse"'
  reason: Full CRUD lifecycle over outbound webhook subscriptions with topic selection maps directly to
    Webhook & Event Subscription Management. No business-domain capability is realised here.
- tag: Webhook Events
  spec_file: accrue-savings-webhook-events-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.78
  evidence: '"List Webhook Events", "Get a webhook event"; schemas "WebhookEvent", "WebhookTransactionFailed",
    "WebhookKycApproved"'
  reason: Read access to the outbound event log and typed event payload schemas is the delivery-reliability/event-schema
    side of webhook subscription management on the developer platform. Mapped as platform plumbing capability
    rather than any business-domain capability.
- tag: Rewards
  spec_file: accrue-savings-rewards-api-openapi.yml
  capability_id: BC-420.40
  capability_id_l1: BC-420
  capability_name: Loyalty & Retention Management
  confidence: 0.75
  evidence: '"Partner-issued rewards let trusted integrations credit customer wallets or create pre-issued
    rewards for recipients identified by phone number"; POST /api/v1/rewards ''Issue Reward'''
  reason: Issuing, updating and cancelling customer rewards is operation of a loyalty/reward programme,
    consistent with the vendor's stated rules-driven reward engine. Confident on loyalty; slight residual
    doubt as reward crediting also touches wallet funding.
- tag: Users
  spec_file: accrue-savings-users-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: '"Users represent the end users and are the parent container of Wallets"; operations "Create
    User", "List Users", "Update User", "Get User"'
  reason: CRUD over end-customer identity records (phone-number-keyed, with attached profile) is customer
    master/identity record keeping. The KYC-disclosure operation hints at regulatory onboarding, but the
    dominant surface is customer record management, so confidence is moderate rather than high.