[Components](https://oods-foundry.com/components) / financial

# PaymentEventTimeline

Lists recorded payment events and timestamps.

Generated from @oods/foundry 0.10.1

- Categories

  financial

- Contexts

  timeline

- Readiness

  `proven-in-generated-apps`

## Playground

This component's contract doesn't list typed props, so the playground shows its documented example.

Documented example `billing-payment-events` : mount, Payment events with chronological last and next dates and $19.99 USD.

The render follows the page's theme switch: light, dark or high contrast. Both frameworks render the same example.

The real PaymentEventTimeline, live

React

## Payment events

$19.99 USD · succeeded

1. **Last payment** Jan 1, 2026
2. **Next payment** Feb 1, 2026

Vue

## Payment events

$19.99 USD · succeeded

1. **Last payment** Jan 1, 2026
2. **Next payment** Feb 1, 2026

## Code

The documented example. HTML is the markup the React component renders for it, which @oods/component-styles styles.

**React**

```
import { PaymentEventTimeline } from '@oods/components-react';
import '@oods/component-styles/css';

export function Example() {
  return (
    <PaymentEventTimeline
      lastPayment="2026-01-01T00:00:00Z"
      nextPayment="2026-02-01T00:00:00Z"
      paymentStatus="succeeded"
      amount={1999}
      currency="usd"
    />
  );
}
```

## Props, slots and events

Contract version 1.1.0. Types are from the React declarations in @oods/components-react.

Props

| Prop | Type | Required | Documented example |
| - | - | - | - |
| `event` | `CollectionEvent \| undefined` | no | |
| `lastPayment` | `string \| undefined` | no | `2026-01-01T00:00:00Z` |
| `nextPayment` | `string \| undefined` | no | `2026-02-01T00:00:00Z` |
| `paymentStatus` | `string \| undefined` | no | `succeeded` |
| `amount` | `number \| undefined` | no | `1999` |
| `currency` | `string \| undefined` | no | `usd` |
| `minorUnits` | `number \| undefined` | no | |
| `title` | `string \| undefined` | no | |

### Slots

none

### Events

none

## States

populated, empty

## Accessibility

- Role

  `none`

- How it gets its name

  `heading` on `h1,h2,h3,h4,h5,h6`

### Keyboard

The contract lists no keyboard behaviour.

### Obligations in the contract

- Native semantic elements retain their names and content
- Public payment-event ID over the same shared payment timeline primitive as PaymentTimeline, without a payment-method term. Last and next payment are chronological UTC dates. Missing next payment is No payment scheduled; missing last is No previous payment. Amount, currency and payment status remain visible.

Public payment-event ID over the same shared payment timeline primitive as PaymentTimeline, without a payment-method term. Last and next payment are chronological UTC dates. Missing next payment is No payment scheduled; missing last is No previous payment. Amount, currency and payment status remain visible.

## Tokens

The token roles this component reads.

- `billing.text`
- `billing.surface`
- `billing.border`

## Readiness

The evidence recorded for this component, with its label.

`proven-in-generated-apps`: catalog_list gives this label when generated React and Vue apps in the runtime sweep that ships with this version both use the component. That sweep was measured on the published 0.4.1, not on this version.

Readiness evidence

| Evidence | React | Vue |
| - | - | - |
| state | implemented-evidence-complete | implemented-evidence-complete |
| versioned contract | passed | passed |
| target implementation | passed | passed |
| package export | passed | passed |
| public declaration | passed | passed |
| dependency closure | passed | passed |
| framework scenario | passed | passed |
| accessibility | verified | verified |
| interaction | not-applicable | not-applicable |
| visual themes | verified | verified |

PaymentEventTimeline presents content and owns no focusable control or action; authored child actions remain the consumer's responsibility.

## Use your own

You can replace this component with your own React or Vue component. Map it, and generated code imports yours at the exact version you name. A contract report, run in a real browser, lists what your component met, what it didn't, and what wasn't checked.

The `component_map` call, with the parts in angle brackets yours to fill:

```
{
  "action": "create",
  "apply": true,
  "externalSystem": "<your design system>",
  "externalComponent": "<YourPaymentEventTimeline>",
  "oodsTraits": [
    "Billable"
  ],
  "substitution": {
    "component": "PaymentEventTimeline",
    "react": {
      "package": "<your-package>/react",
      "version": "<exact version>",
      "export": "<YourPaymentEventTimeline>"
    },
    "vue": {
      "package": "<your-package>/vue",
      "version": "<exact version>",
      "export": "<YourPaymentEventTimeline>"
    }
  }
}
```

## How this page was made

Generated at build from the published data, each source with the hash of what was read. [The page's manifest](https://oods-foundry.com/components/payment-event-timeline/manifest.json).

- **Contract**: `@oods/component-contracts@0.10.1 componentContracts.PaymentEventTimeline` `sha256:240dbc2bf398…`
- **Documented example**: `@oods/component-contracts@0.10.1 sharedScenarios billing-payment-events` `sha256:ce9e5fe2ba23…`
- **Catalog entry (catalog_list)**: `generated/0.10.1/system/catalog.json PaymentEventTimeline` `sha256:1ffc00f0149e…`
- **React readiness**: `@oods/components-react@0.10.1 readiness PaymentEventTimeline` `sha256:4ee15aa86b11…`
- **Vue readiness**: `@oods/components-vue@0.10.1 readiness PaymentEventTimeline` `sha256:b2024a591f5c…`
- **Prop types**: `generated/0.10.1/components/prop-types.json PaymentEventTimeline` `sha256:92ee464709c8…`