# Fictional practice scenario: Harbor Learning subscriptions

Harbor Learning is considering recurring billing. Its project proposal names a new hosted payment service and says the service uses tokenization. The current payment-flow diagram describes one-time payments only. The service configuration and customer-side connections have not yet been verified.

## What the learner should notice

- A new payment capability and provider service are proposed.
- The current diagram may not describe the planned flow.
- The provider’s general statement is not correlated to Harbor’s exact configuration.
- The decision owner and required source records have not been identified.

## Useful next questions

1. Which payment channels and payment stages will the new design support?
2. Where will account data be entered, transmitted, or stored, and what records confirm that?
3. Which systems, services, connections, supporting services, and provider responsibilities change?
4. Which flow diagrams and inventories need review, and who owns those records?
5. Who is accountable for evaluating potential impact and documenting the result?

The scenario intentionally leaves these facts unanswered. The exercise is to prepare the handoff, not to infer a scope result from a hosted page or a provider label.
