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 the busines use cases.

What is [Title of Module]?

For Example What is 3D secure card?

Description about 3D secure card

For Example: 3DS (3D Secure) is a security protocol that adds an extra layer of authentication for online credit and debit card transactions. When a card is enrolled in 3DS, the cardholder may be asked to enter a password or a one-time code to verify their identity during checkout. This process helps prevent unauthorized use of the card online.

Business Rules

List the rules, constraints, or policies that govern the use case. These may include:

• Preconditions (what must be true before the use case starts)

  For Example: To configure WS2 check, merchant settings need to be configured

• Postconditions (what must be true after the use case ends)

  For Example: Pre-Auth payments require capture post AUTHORIZATION to complete the payment

• Business policies or compliance requirements

  For Example: Only Customer can add a 3DS card

Business Use Case

important

• List the use cases seperately for UI and API
• Break down the functionality contextually

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

Use Case 1: [Title of Use Case]

For Example: Customer Makes Payment from wallet via UI

Flow Diagram should include below details

• Actors (who is involved)

  Agent/User

• Triggers (what starts the process)

  Merchant Initiates session request

• Main flow (step-by-step process)

  • Merchant initiates session and launches widget.
  • Customer selects payment method and confirms.
  • System processes payment and displays confirmation. Refer Manufacturer Card documentation

• Alternate flows (exceptions or variations)

• Expected outcomes

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 Flowdiagrams using mermaid library

Special Use Case

Describe any edge cases, exceptions, or unique scenarios that require special handling.

Example:

• Handling payment retries after a failed transaction.
• Processing refunds for partial orders.