Skip to main content
Version: v1

Business Use Case Document Template

A Business Use Case Document describes a real-world business process or scenario, detailing the actors, triggers, flows, and outcomes. It serves as a reference for both business and technical teams. This document outlines a template to follow while documenting business use cases, and should include:

Quick Overview​

  • Key benefits of the feature/use case
  • A real-world example (optional)

Get Started / Integration​

  • Link to configuration or integration guides
  • Brief steps to enable or integrate the feature

What is [Title of Module]?​

For Example What is 3D secure card?

Description about the module or feature.

Business Rules​

List the rules, constraints, or policies that govern the use case. Structure as follows:

Pre-Conditions​

  • Segregate by:
    • Merchant Configuration
    • Payment Method
    • Customer Wallet
    • Transaction Setup

Post-Conditions​

  • What must be true after the use case ends (success/failure outcomes)

Constraints​

  • Any business or technical constraints (e.g., retry caps, all-or-nothing, unique cards)

Retry & Recovery (if applicable)​

  • Describe retry logic, rollback, and recovery options
  • Provide best practices and example retry flows

Use Cases & Scenarios​

important
  • List the use cases separately for UI, API, and Edge Cases
  • Use expandable sections for each scenario type

For Example:

  • Use Case 1: Customer Makes Payment from wallet via UI
  • Use Case 2: Customer Makes Payment using 3DS via API
  • Use Case 3: Customer Adds 3DS to wallet
  • Use Case 4: Agent updates Payment method via API

API Scenarios​

API Scenarios
#Scenario...Outcome
1.........

UI Scenarios​

UI Scenarios
#Scenario...Outcome
1.........

Edge Cases​

Edge Cases
#ScenarioOutcomeRecovery
1.........

Use Case 1: [Title of Use Case] Eg: Customer Makes Payment​

Actors:

  • Customer

Trigger:

  • Merchant initiates checkout

Main Flow:

  1. Merchant initiates session and launches widget.
  2. Customer selects payment method and confirms.
  3. System processes payment and displays confirmation.

Alternate Flow:

  • If payment fails, system prompts for retry or alternate method.

Outcome:

  • Payment Completed and confirmation is sent to merchant.

Flow Diagrams​

Include flow diagrams using mermaid library.

Notifications (if applicable)​

  • Document webhook/event notification patterns, event types, and payloads

Status Reference (if applicable)​

  • Table mapping status codes to meaning, customer impact, and merchant action
  • List integration guides, refund docs, and other references