@eventcatalog/create-eventcatalog 4.3.3 → 4.3.4

package/templates/default/domains/Payment/entities/Payment/index.mdx

@@ -1,140 +0,0 @@
----
-id: Payment
-name: Payment
-version: 1.0.0
-identifier: paymentId
-aggregateRoot: true
-summary: Represents payment transactions for orders in the e-commerce system.
-owners:
-  - dboyne
-properties:
-  - name: paymentId
-    type: UUID
-    required: true
-    description: Unique identifier for the payment
-  - name: orderId
-    type: UUID
-    required: true
-    description: Order this payment is associated with
-    references: Order
-    referencesIdentifier: orderId
-    relationType: hasOne
-  - name: customerId
-    type: UUID
-    required: true
-    description: Customer who made the payment
-    references: Customer
-    referencesIdentifier: customerId
-    relationType: hasOne
-  - name: amount
-    type: decimal
-    required: true
-    description: Payment amount
-  - name: currency
-    type: string
-    required: true
-    description: Currency code (e.g., USD, EUR, GBP)
-  - name: paymentMethod
-    type: string
-    required: true
-    description: Payment method used
-    enum: ['credit_card', 'debit_card', 'paypal', 'stripe', 'bank_transfer', 'apple_pay', 'google_pay']
-  - name: paymentMethodDetails
-    type: object
-    required: false
-    description: Additional payment method specific details
-    properties:
-      - name: cardLast4
-        type: string
-        description: Last 4 digits of card number
-      - name: cardType
-        type: string
-        description: Card type (Visa, MasterCard, etc.)
-      - name: expiryMonth
-        type: integer
-        description: Card expiry month
-      - name: expiryYear
-        type: integer
-        description: Card expiry year
-  - name: status
-    type: string
-    required: true
-    description: Current payment status
-    enum: ['pending', 'processing', 'completed', 'failed', 'cancelled', 'refunded', 'partially_refunded']
-  - name: transactionId
-    type: string
-    required: false
-    description: External payment processor transaction ID
-  - name: gatewayResponse
-    type: object
-    required: false
-    description: Raw response from payment gateway
-  - name: billingAddress
-    type: Address
-    required: true
-    description: Billing address for the payment
-    references: Address
-    referencesIdentifier: addressId
-    relationType: hasOne
-  - name: processedAt
-    type: DateTime
-    required: false
-    description: Date and time when payment was processed
-  - name: failureReason
-    type: string
-    required: false
-    description: Reason for payment failure if applicable
-  - name: refunds
-    type: array
-    items:
-      type: PaymentRefund
-    required: false
-    description: Refunds associated with this payment
-  - name: createdAt
-    type: DateTime
-    required: true
-    description: Date and time when the payment record was created
-  - name: updatedAt
-    type: DateTime
-    required: false
-    description: Date and time when the payment record was last updated
----
-
-## Overview
-
-The Payment entity manages all payment transactions in the e-commerce system. It tracks payment details, status, and relationships with orders and customers, supporting various payment methods and refund scenarios.
-
-### Entity Properties
-
-<EntityPropertiesTable />
-
-## Relationships
-
-- **Order:** Each payment belongs to one `Order` (identified by `orderId`).
-- **Customer:** Each payment is made by one `Customer` (identified by `customerId`).
-- **Address:** Each payment has a billing `Address` (identified by `billingAddress`).
-- **PaymentRefund:** A payment can have multiple `PaymentRefund` entities for partial or full refunds.
-
-## Payment States
-
-```
-pending → processing → completed
-    ↓         ↓           ↓
-cancelled  failed    refunded/partially_refunded
-```
-
-## Examples
-
-- **Payment #1:** $299.99 credit card payment for Order #12345, completed successfully.
-- **Payment #2:** $150.00 PayPal payment for Order #67890, failed due to insufficient funds.
-- **Payment #3:** $500.00 bank transfer, completed with $50.00 partial refund.
-
-## Business Rules
-
-- Payment amount must match the order total
-- Payment status transitions must follow valid state machine
-- Failed payments should include failure reason
-- Completed payments cannot be cancelled
-- Refunds cannot exceed the original payment amount
-- Payment method details are encrypted and PCI compliant
-- Transaction IDs from payment gateways must be stored for reconciliation

package/templates/default/domains/Payment/entities/PaymentMethod/index.mdx

@@ -1,80 +0,0 @@
----
-id: PaymentMethod
-name: PaymentMethod
-version: 1.0.0
-identifier: paymentMethodId
-summary: Represents a payment instrument a customer can use, like a credit card or bank account.
-owners:
-  - dboyne
-
-properties:
-  - name: paymentMethodId
-    type: UUID
-    required: true
-    description: Unique identifier for the payment method.
-  - name: customerId
-    type: UUID
-    required: true
-    description: Identifier of the customer who owns this payment method.
-    references: Customer
-    relationType: hasOne
-  - name: type
-    type: string # (e.g., CreditCard, BankAccount, PayPal, ApplePay)
-    required: true
-    description: The type of payment method.
-  - name: details # Contains type-specific details (masked, tokenized)
-    type: object
-    required: true
-    description: Contains type-specific, often sensitive details (e.g., last 4 digits of card, card brand, bank name, account type, token). **Never store raw PANs or sensitive data.**
-    # Example structure for CreditCard:
-    # details:
-    #   brand: "Visa"
-    #   last4: "1234"
-    #   expiryMonth: 12
-    #   expiryYear: 2025
-    #   cardholderName: "Jane Doe"
-    #   gatewayToken: "tok_abc123xyz"
-  - name: isDefault
-    type: boolean
-    required: true
-    description: Indicates if this is the customer's default payment method.
-  - name: billingAddressId # Link to the billing address associated with this method
-    type: UUID
-    required: true
-    description: Identifier for the billing address verified for this payment method.
-  - name: status
-    type: string # (e.g., Active, Expired, Invalid, Removed)
-    required: true
-    description: Current status of the payment method.
-  - name: createdAt
-    type: DateTime
-    required: true
-    description: Timestamp when the payment method was added.
-  - name: updatedAt
-    type: DateTime
-    required: true
-    description: Timestamp when the payment method was last updated.
----
-
-## Overview
-
-The PaymentMethod entity represents a specific payment instrument registered by a customer, such as a credit card or a linked bank account. It stores necessary (non-sensitive) details required to initiate payments and links to the associated customer and billing address.
-
-**Security Note:** Sensitive details like full card numbers or bank account numbers should **never** be stored directly. Rely on tokenization provided by payment gateways.
-
-### Entity Properties
-
-<EntityPropertiesTable />
-
-## Relationships
-
-- **Customer:** A payment method belongs to one `Customer`.
-- **Address:** Linked to a specific billing `Address`.
-- **Payment:** Used to make `Payment` transactions.
-- **Subscription:** May be designated as the payment method for a `Subscription`.
-
-## Examples
-
-- Jane Doe's default Visa card ending in 1234, expiring 12/2025, status Active.
-- John Smith's linked bank account (Chase, Checking), status Active.
-- An old MasterCard ending in 5678 belonging to Jane Doe, status Expired.

package/templates/default/domains/Payment/entities/Transaction/index.mdx

@@ -1,80 +0,0 @@
----
-id: Transaction
-name: Transaction
-version: 1.0.0
-identifier: transactionId
-summary: Represents a low-level interaction with a payment gateway or processor (e.g., authorize, capture, refund, void).
-owners:
-  - dboyne
-
-properties:
-  - name: transactionId
-    type: UUID
-    required: true
-    description: Unique identifier for this specific gateway transaction.
-  - name: paymentId
-    type: UUID
-    required: true
-    references: Payment
-    relationType: hasOne
-    description: Identifier of the parent Payment this transaction belongs to.
-  - name: type
-    type: string # (e.g., Authorize, Capture, Sale, Refund, Void, Verify)
-    required: true
-    description: The type of operation performed with the payment gateway.
-  - name: gatewayReferenceId
-    type: string
-    required: true
-    description: Unique transaction ID provided by the external payment gateway.
-  - name: amount
-    type: decimal
-    required: true
-    description: The amount associated with this specific transaction operation.
-  - name: currency
-    type: string # ISO 4217 code
-    required: true
-    description: Currency of the transaction amount.
-  - name: status
-    type: string # (e.g., Success, Failure, Pending)
-    required: true
-    description: Status reported by the gateway for this specific operation.
-  - name: responseCode # Gateway-specific code
-    type: string
-    required: false
-    description: Response code returned by the payment gateway.
-  - name: responseMessage # Gateway-specific message
-    type: string
-    required: false
-    description: Detailed message or reason returned by the gateway.
-  - name: processedAt
-    type: DateTime
-    required: true
-    description: Timestamp when the transaction was processed by the gateway.
-  - name: rawRequest # Optional, for debugging - consider security implications
-    type: text
-    required: false
-    description: Raw request payload sent to the gateway (use with caution).
-  - name: rawResponse # Optional, for debugging - consider security implications
-    type: text
-    required: false
-    description: Raw response payload received from the gateway (use with caution).
----
-
-## Overview
-
-The Transaction entity logs the individual interactions with an external payment processor (like Stripe, PayPal, Adyen) that occur as part of processing a `Payment`. This provides a detailed audit trail of gateway operations, including authorizations, captures, refunds, and any associated success or failure responses.
-
-### Entity Properties
-
-<EntityPropertiesTable />
-
-## Relationships
-
-- **Payment:** A transaction is part of one `Payment`.
-
-## Examples
-
-- **Authorization Success:** Type: Authorize, PaymentID: PAY-98765, GatewayRef: auth_abc, Amount: $19.99, Status: Success.
-- **Capture Success:** Type: Capture, PaymentID: PAY-98765, GatewayRef: ch_def, Amount: $19.99, Status: Success (following the authorization).
-- **Authorization Failure:** Type: Authorize, PaymentID: PAY-98766, GatewayRef: auth_ghi, Amount: $50.00, Status: Failure, ResponseCode: 'declined', ResponseMessage: 'Insufficient Funds'.
-- **Refund Success:** Type: Refund, PaymentID: PAY-98760, GatewayRef: re_jkl, Amount: $25.00, Status: Success.

package/templates/default/domains/Payment/flows/PaymentProcessed/index.mdx

@@ -1,82 +0,0 @@
----
-id: PaymentFlow
-name: Payment Flow for customers
-version: 1.0.0
-summary: Business flow for processing payments in an e-commerce platform
-owners:
-  - dboyne
-steps:
-  - id: 'customer_place_order'
-    title: Customer places order
-    next_step: 'place_order_request'
-  - id: 'place_order_request'
-    title: Place order
-    message:
-      id: PlaceOrder
-      version: 0.0.1
-    next_step:
-      id: 'payment_initiated'
-      label: Initiate payment
-  - id: 'payment_initiated'
-    title: Payment Initiated
-    message:
-      id: PaymentInitiated
-      version: 0.0.1
-    next_steps:
-      - 'payment_processed'
-      - 'payment_failed'
-  - id: 'payment_processed'
-    title: Payment Processed
-    message:
-      id: PaymentProcessed
-      version: 0.0.1
-    next_steps:
-      - id: 'adjust_inventory'
-        label: Adjust inventory
-      - id: 'send_custom_notification'
-        label: Notify customer
-  - id: 'payment_failed'
-    title: Payment Failed
-    type: node
-    next_steps:
-      - id: 'failure_notification'
-        label: Notify customer of failure
-      - id: 'retry_payment'
-        label: Retry payment
-  - id: 'adjust_inventory'
-    title: Inventory Adjusted
-    message:
-      id: InventoryAdjusted
-      version: 1.0.1
-    next_step:
-      id: 'payment_complete'
-      label: Complete order
-  - id: 'send_custom_notification'
-    title: Customer Notified of Payment
-    type: node
-    next_step:
-      id: 'payment_complete'
-      label: Complete order
-  - id: 'failure_notification'
-    title: Customer Notified of Failure
-    type: node
-  - id: 'retry_payment'
-    title: Retry Payment
-    type: node
-    next_step:
-      id: 'payment_initiated'
-      label: Retry payment process
-  - id: 'payment_complete'
-    title: Payment Complete
-    type: node
-    next_step:
-      id: 'order-complete'
-      label: Order completed
-  - id: 'order-complete'
-    title: Order Completed
-    type: node
----
-
-### Flow of feature
-
-<NodeGraph />

package/templates/default/domains/Payment/index.mdx

@@ -1,40 +0,0 @@
----
-id: Payment
-name: Payment
-version: 0.0.1
-summary: |
-  Domain that contains payment related services and messages.
-owners:
-  - dboyne
-services:
-  - id: PaymentService
-    version: 0.0.1
-  - id: FraudDetectionService
-    version: 0.0.1
-  - id: PaymentGatewayService
-    version: 0.0.1
-entities:
-  - id: Invoice
-  - id: Payment
-  - id: PaymentMethod
-  - id: Transaction
-  - id: Address
-badges:
-  - content: Payment Domain
-    backgroundColor: blue
-    textColor: blue
----
-
-## Overview
-
-The Payment Domain encompasses all services and components related to handling financial transactions within the system. It is responsible for managing payments, transactions, billing, and financial records. The domain ensures secure, reliable, and efficient processing of all payment-related activities
-
-### Architecture for the Payment domain
-
-<NodeGraph />
-
-### Entity Map
-
-A visualization of the entities in the Payment domain. Here you can see the relationships between the entities and how they are used in the domain.
-
-<EntityMap id="Payment" />

package/templates/default/domains/Payment/services/FraudDetectionService/events/FraudCheckCompleted/examples/check-flagged.json

@@ -1,50 +0,0 @@
-{
-  "eventId": "evt_fc_a7b8c9d0-7890-bcde-f012-345678901234",
-  "timestamp": "2024-03-16T19:05:50.219Z",
-  "type": "FraudCheckCompleted",
-  "source": "fraud-detection-service",
-  "data": {
-    "checkId": "chk_9e0f1a2b-3c4d-5e6f-7a8b-9c0d1e2f3a4b",
-    "assessmentId": "risk_4d5e6f7a-8b9c-0d1e-2f3a-4b5c6d7e8f9a",
-    "paymentId": "pay_6f7a8b9c-0d1e-2f3a-4b5c-6d7e8f9a0b1c",
-    "orderId": "ord_92860445",
-    "customerId": "cust_31207",
-    "result": "flagged",
-    "riskScore": 82,
-    "riskLevel": "high",
-    "checksPerformed": [
-      {
-        "name": "identity_verification",
-        "status": "passed",
-        "details": "Customer identity verified"
-      },
-      {
-        "name": "card_bin_check",
-        "status": "passed",
-        "details": "Card BIN matches issuing bank"
-      },
-      {
-        "name": "address_verification",
-        "status": "warning",
-        "details": "AVS returned partial match - postal code mismatch"
-      },
-      {
-        "name": "geolocation_check",
-        "status": "failed",
-        "details": "IP geolocation (Lagos, Nigeria) does not match billing country (US)"
-      },
-      {
-        "name": "impossible_travel_check",
-        "status": "failed",
-        "details": "Impossible travel detected between Portland, OR and Lagos in 2 hours"
-      }
-    ],
-    "processingTimeMs": 1205,
-    "fraudDetected": true,
-    "completedAt": "2024-03-16T19:05:50.219Z"
-  },
-  "metadata": {
-    "correlationId": "corr_11aa22bb-33cc-44dd-55ee-66ff77008899",
-    "modelVersion": "fraud-ml-v3.2.1"
-  }
-}

package/templates/default/domains/Payment/services/FraudDetectionService/events/FraudCheckCompleted/examples/check-passed.json

@@ -1,45 +0,0 @@
-{
-  "eventId": "evt_fc_f6a7b8c9-6789-abcd-ef01-234567890123",
-  "timestamp": "2024-03-15T10:59:05.118Z",
-  "type": "FraudCheckCompleted",
-  "source": "fraud-detection-service",
-  "data": {
-    "checkId": "chk_3a4b5c6d-7e8f-9a0b-1c2d-3e4f5a6b7c8d",
-    "assessmentId": "risk_7a8b9c0d-1e2f-3a4b-5c6d-7e8f9a0b1c2d",
-    "paymentId": "pay_4b5c6d7e-8f9a-0b1c-2d3e-4f5a6b7c8d9e",
-    "orderId": "ord_92840123",
-    "customerId": "cust_10482",
-    "result": "passed",
-    "riskScore": 12,
-    "riskLevel": "low",
-    "checksPerformed": [
-      {
-        "name": "identity_verification",
-        "status": "passed",
-        "details": "Customer identity verified against government records"
-      },
-      {
-        "name": "card_bin_check",
-        "status": "passed",
-        "details": "Card BIN matches issuing bank in expected region"
-      },
-      {
-        "name": "address_verification",
-        "status": "passed",
-        "details": "AVS check returned full match on street and postal code"
-      },
-      {
-        "name": "velocity_check",
-        "status": "passed",
-        "details": "Transaction frequency within normal parameters"
-      }
-    ],
-    "processingTimeMs": 342,
-    "fraudDetected": false,
-    "completedAt": "2024-03-15T10:59:05.118Z"
-  },
-  "metadata": {
-    "correlationId": "corr_b2c3d4e5-f6a7-8901-bcde-f23456789012",
-    "modelVersion": "fraud-ml-v3.2.1"
-  }
-}

package/templates/default/domains/Payment/services/FraudDetectionService/events/FraudCheckCompleted/examples/examples.config.yaml

@@ -1,15 +0,0 @@
-check-passed.json:
-  name: Check Passed
-  summary: All fraud checks passed for a low-risk returning customer. Identity, card BIN, address, and velocity checks all cleared in 342ms.
-  usage: |
-    curl -X POST http://localhost:3000/events/publish \
-      -H "Content-Type: application/json" \
-      -d @check-passed.json
-
-check-flagged.json:
-  name: Check Flagged
-  summary: Fraud check flagged due to geolocation mismatch and impossible travel detection. Address verification returned a partial match.
-  usage: |
-    curl -X POST http://localhost:3000/events/publish \
-      -H "Content-Type: application/json" \
-      -d @check-flagged.json

package/templates/default/domains/Payment/services/FraudDetectionService/events/FraudCheckCompleted/index.mdx

@@ -1,50 +0,0 @@
----
-id: FraudCheckCompleted
-version: 0.0.1
-name: Fraud Check Completed
-summary: Emitted when a fraud check has been completed for a transaction
-owners:
-  - dboyne
-tags:
-  - payment
-  - fraud
-  - security
-badges:
-  - content: New
-    backgroundColor: green
-    textColor: white
-schemaPath: schema.json
----
-
-import Footer from '@catalog/components/footer.astro';
-
-## Overview
-
-The `FraudCheckCompleted` event is emitted when the fraud detection service has completed its analysis of a payment transaction. This event contains the risk assessment results and recommendations.
-
-## Schema
-
-<SchemaViewer title="FraudCheckCompleted Schema" schemaPath={frontmatter.schemaPath} />
-
-## Event Details
-
-- **Risk Score**: A numerical score from 0-100 indicating fraud risk
-- **Decision**: APPROVED, DECLINED, or MANUAL_REVIEW
-- **Reasons**: Array of reasons for the decision
-- **Confidence**: Confidence level of the fraud detection
-
-## Example Payload
-
-```json
-{
-  "transactionId": "txn_1234567890",
-  "paymentId": "pay_9876543210",
-  "riskScore": 25,
-  "decision": "APPROVED",
-  "reasons": ["Low risk merchant", "Customer history positive"],
-  "confidence": 0.92,
-  "timestamp": "2024-01-15T10:30:00Z"
-}
-```
-
-<Footer />

package/templates/default/domains/Payment/services/FraudDetectionService/events/FraudCheckCompleted/schema.json

@@ -1,44 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "type": "object",
-  "properties": {
-    "transactionId": {
-      "type": "string",
-      "description": "Unique identifier for the transaction"
-    },
-    "paymentId": {
-      "type": "string",
-      "description": "Unique identifier for the payment"
-    },
-    "riskScore": {
-      "type": "number",
-      "minimum": 0,
-      "maximum": 100,
-      "description": "Risk score from 0-100"
-    },
-    "decision": {
-      "type": "string",
-      "enum": ["APPROVED", "DECLINED", "MANUAL_REVIEW"],
-      "description": "Fraud check decision"
-    },
-    "reasons": {
-      "type": "array",
-      "items": {
-        "type": "string"
-      },
-      "description": "Reasons for the decision"
-    },
-    "confidence": {
-      "type": "number",
-      "minimum": 0,
-      "maximum": 1,
-      "description": "Confidence level of the decision"
-    },
-    "timestamp": {
-      "type": "string",
-      "format": "date-time",
-      "description": "When the fraud check was completed"
-    }
-  },
-  "required": ["transactionId", "paymentId", "riskScore", "decision", "timestamp"]
-}

package/templates/default/domains/Payment/services/FraudDetectionService/index.mdx

@@ -1,62 +0,0 @@
----
-id: FraudDetectionService
-version: 0.0.1
-name: Fraud Detection Service
-summary: Analyzes payment transactions for fraudulent activity and risk assessment
-repository:
-  url: 'https://github.com/eventcatalog/fraud-detection-service'
-receives:
-  - id: PaymentInitiated
-    version: 0.0.1
-    from:
-      - id: 'payments.{env}.events'
-        parameters:
-          env: staging
-  - id: PaymentProcessed
-    version: 0.0.1
-    from:
-      - id: 'payments.{env}.events'
-        parameters:
-          env: staging
-sends:
-  - id: FraudCheckCompleted
-    version: 0.0.1
-owners:
-  - dboyne
----
-
-import Footer from '@catalog/components/footer.astro';
-
-## Overview
-
-The Fraud Detection Service is responsible for analyzing payment transactions in real-time to detect potential fraudulent activity. It uses machine learning models and rule-based systems to assess risk and prevent financial losses.
-
-## Key Features
-
-- **Real-time Transaction Analysis**: Analyzes transactions as they occur
-- **Machine Learning Models**: Uses ML to identify suspicious patterns
-- **Risk Scoring**: Calculates risk scores for each transaction
-- **Automated Blocking**: Can automatically block high-risk transactions
-- **Manual Review Queue**: Flags medium-risk transactions for manual review
-
-## API Endpoints
-
-### REST API
-
-- `POST /api/fraud/check` - Submit transaction for fraud check
-- `GET /api/fraud/risk-score/{transactionId}` - Get risk score for transaction
-- `PUT /api/fraud/override/{transactionId}` - Manual override of fraud decision
-
-## Configuration
-
-```yaml
-fraud_detection:
-  risk_thresholds:
-    high: 80
-    medium: 50
-    low: 20
-  auto_block_threshold: 90
-  ml_model_version: '2.3.1'
-```
-
-<Footer />