Outbound events

Signed lifecycle events with durable delivery.

RebateCardX delivers at least once. Consumers verify the signature, deduplicate by event_id and process events idempotently.

Route recovery

Return an unmatched request to a known Rebate Cards path.

The requested route is outside the current website map, so navigation returns to published program information.

  1. 01 / Request

    Unknown pathname

    A browser asks for a route that is not present in the current site map.

  2. 02 / Router

    Path resolution

    • Normalise the request
    • Compare published routes
    • Preserve a clear 404 response
  3. 03A / Option

    Return home

    Restart with the main Rebate Cards business-model overview.

  4. 03B / Option

    Explore industry models

    Continue to rebate models, economics, insights or contact.

  5. 04 / Website

    Published navigation

    Only current, intentional destinations are presented as available pages.

  6. 05 / Recovery

    A valid next request

    The visitor selects a known destination and resumes the information journey.

Illustrative website route-recovery flow. This panel describes navigation only and does not create a Rebate Card entitlement or service commitment.

Delivery contract

Persist first. Acknowledge only after your boundary accepts the event.

Each delivery includes an event ID, event type, occurrence time, tenant and aggregate references, schema version and signed raw body.

  • campaign.activated
  • order.eligibility_evaluated
  • award.created
  • award.held
  • claim.completed
  • card.issued
  • card.status_changed
  • transaction.updated
  • funding.settled
  • dispute.updated
  • integration.degraded