Planet Portal Repository Insights

Generated: 2026-01-06
Source: Deep GitHub repository analysis via code scanning

Executive Summary

The Planet Portal (pp-*) ecosystem is a .NET-based microservices architecture built primarily with:

• Runtime: .NET 8 (latest LTS)
• Primary Database: MongoDB (CosmosDB API compatible)
• Cache: Redis
• Message Broker: Kafka (via KafkaFlow)
• Background Jobs: Hangfire (with MongoDB storage)
• Authentication: Auth0 (M2M tokens, JWT validation)

---

1. Repository Inventory

Last scanned: 2026-01-09 | Total repos: 42

Planet Portal (pp-*) - Strategic Platform

Merchant Activation

Integra Portal

MAS Portal

Legacy/Other Portals

Archived Portals (Deprecated)

Test Automation

Infrastructure & Tooling

Status Legend

• ✅ Active: Last commit < 6 months
• ⚠️ Stale: Last commit 6-12 months
• ⛔ Stale: Last commit > 12 months
• 🗄️ Archived: Repository archived

Last scanned: 2026-01-09

---

2. pp-payments-api - Deep Dive

2.1 HTTP Gateway Integrations

The service acts as an aggregator/orchestrator connecting to 7+ downstream systems:

┌─────────────────────────────────────────────────────────────────┐
│                      pp-payments-api                             │
│                                                                  │
│  ┌─────────────────────────────────────────────────────────────┐│
│  │                    Gateway Clients                          ││
│  │                                                             ││
│  │  ┌─────────────┐  ┌─────────────┐  ┌─────────────────────┐ ││
│  │  │ Datatrans   │  │ Integra     │  │ DigitalGateway(DGW) │ ││
│  │  │ Gateway     │  │ Gateway     │  │ Gateway             │ ││
│  │  └──────┬──────┘  └──────┬──────┘  └──────────┬──────────┘ ││
│  │         │                │                     │            ││
│  │  ┌──────┴──────┐  ┌──────┴──────┐  ┌──────────┴──────────┐ ││
│  │  │ Web2Pay     │  │ IntegraPort │  │ IAM Gateway         │ ││
│  │  │ (Legacy)    │  │ al API      │  │                     │ ││
│  │  └─────────────┘  └─────────────┘  └─────────────────────┘ ││
│  │                                                             ││
│  │  ┌─────────────────────────────────────────────────────────┐││
│  │  │ Auth0 Clients (2 instances):                            │││
│  │  │  - Primary Auth0 (general M2M)                          │││
│  │  │  - MerchantActivation Auth0                             │││
│  │  └─────────────────────────────────────────────────────────┘││
│  └─────────────────────────────────────────────────────────────┘│
└─────────────────────────────────────────────────────────────────┘

2.2 Gateway Client Details

2.3 Gateway Factory Pattern

Uses IGatewayClientFactory to resolve the correct client based on payment type:

• Card-present → Integra
• E-commerce → Datatrans (or Web2Pay for legacy)
• APM → DigitalGateway

2.4 Interfaces Implemented by Gateways

// Payment action interfaces
IPaymentActionClient      // Captures, refunds, reversals
ITokenizationClient       // Card tokenization
INewPaymentClient         // Initialize new payments
IRefundUnreferencedClient // Unreferenced refunds
IInitializePaymentLinkClient // Pay-by-Link initialization

2.5 Data Stores

2.6 MongoDB Collections

├── TransactionLedgerCollection  → TransactionDocument, TransactionDetailsDocument, TransactionOverviewDocument
├── MerchantCollection           → MerchantDocument, MerchantsOverviewDocument, MerchantDetailsDocument
├── PaymentActionsCollection     → PaymentActionDocument
├── PaymentLinksCollection       → PaymentLinkDocument, PaymentLinkOverviewDocument, PaymentLinkDetailsDocument, PaymentLinkCheckoutDocument
├── PaymentMethodsCollection     → PaymentMethodDocument
├── TerminalCollection           → TerminalDocument, TerminalOverviewDocument, TerminalDetailsDocument
└── TerminalActionsCollection    → TerminalActionDocument

2.7 Background Services

---

3. pp-transaction-consumer - Deep Dive

3.1 Message Processing Architecture

Kafka Topics                    Consumer Handlers
─────────────                   ─────────────────
┌─────────────────────┐
│ Transaction Events  │ ──────► RequestCreatedHandler
│                     │ ──────► AcquirerRequestedHandler
│                     │ ──────► BinLookedUpHandler
│                     │ ──────► SchemeRespondedHandler
└─────────────────────┘

┌─────────────────────┐
│ Merchant Events     │ ──────► MerchantPaymentMethodChangedHandler
└─────────────────────┘

3.2 Kafka Configuration

• Framework: KafkaFlow
• Middleware Pipeline:
  • MessageLoggingMiddleware - Request/response logging
  • WithDLQDeserializationExceptionMiddleware - Dead letter queue for deserialization errors
  • WithDLQExceptionMiddleware - Dead letter queue for processing errors
  • ExceptionMiddleware - General exception handling
  • MessageConsumptionFilteringMiddleware - Message filtering

3.3 Outbox Pattern

Uses TransactionUpdateProcessor for reliable message delivery via outbox pattern.

---

4. Integration Architecture

4.1 Upstream Dependencies (pp-payments-api consumes)

External Systems:
├── datatrans-payment-gateway     → E-commerce payment processing
├── pgid-integrafe                → Card-present gateway (Integra FE)
├── integra-portal-web            → Integra portal API
├── pgid-dgw-core                 → Digital Gateway (APM)
├── Web2Pay                       → Legacy e-commerce (deprecated)
└── Auth0                         → Identity provider

4.2 Downstream Consumers (consume pp-payments-api events)

Internal Consumers:
├── pp-transaction-consumer       → Transaction event processing
├── pp-reports-api                → Report generation
├── Data Platform (Snowflake)     → Analytics & BI
└── Planet Portal UI              → Real-time updates via SignalR/WebSockets

4.3 Data Flow

┌──────────────────────────────────────────────────────────────────────────────┐
│                           Payment Request Flow                                │
│                                                                              │
│  Merchant    pp-webapp    pp-payments-api    Gateway    pp-transaction-      │
│  Portal                                      (DFS/     consumer              │
│                                              Integra)                        │
│    │            │              │               │            │                │
│    │ ─────────► │ ─────────►  │               │            │                │
│    │  Request   │  GraphQL/   │               │            │                │
│    │            │  REST       │ ────────────► │            │                │
│    │            │             │ Process       │            │                │
│    │            │             │ Payment       │ ─────────► │                │
│    │            │             │               │ Response   │                │
│    │            │             │ ◄──────────── │            │                │
│    │            │             │               │            │                │
│    │            │             │ ──────────────────────────►│                │
│    │            │             │ Kafka Event (Transaction   │                │
│    │            │             │ Status Update)             │                │
│    │            │             │               │            │ ───────────►   │
│    │            │             │               │            │ Update DB      │
│    │            │             │               │            │ Notify         │
│    │ ◄───────── │ ◄────────── │               │            │                │
│    │  Result    │  Response   │               │            │                │
└──────────────────────────────────────────────────────────────────────────────┘

---

5. Technology Patterns

5.1 Clean Architecture

Both pp-payments-api and pp-transaction-consumer follow Clean Architecture:

├── Domain          → Business entities, interfaces
├── Application     → Use cases, validators, interfaces
├── Infrastructure  → Data access, external services, gateways
└── Web/Consumer    → Entry points, controllers, handlers

5.2 HTTP Client Configuration

All HTTP clients use:

• IHttpClientFactory with named clients
• LoggingHttpMessageHandler for request/response logging
• AuthTokenHandler for Auth0 bearer token injection
• Configurable timeouts per gateway
• Health checks per gateway

5.3 Health Check Pattern

healthCheckBuilder.AddCheck<DatatransGatewayHealthCheck>(
    name: "Datatrans",
    failureStatus: HealthStatus.Degraded,
    tags: [HealthCheckConstants.OnReadinessTag]);

5.4 Authentication Flow

┌────────────────────────────────────────────────────────────────────────────┐
│                        Auth0 M2M Token Flow                                 │
│                                                                            │
│  pp-payments-api                    Auth0                   Target Gateway │
│       │                               │                           │        │
│       │ ── Get M2M Token ──────────► │                           │        │
│       │ ◄─── Access Token ────────── │                           │        │
│       │                               │                           │        │
│       │ (Cache token in IMemoryCache) │                           │        │
│       │                               │                           │        │
│       │ ───── Request + Bearer Token ─────────────────────────►  │        │
│       │ ◄──────────── Response ──────────────────────────────── │        │
└────────────────────────────────────────────────────────────────────────────┘

---

6. Key Findings & Recommendations

6.1 Architectural Observations

6.2 Integration Points for TAM Alignment

E-commerce Path (Target: DFS/Datatrans)

• DatatransGatewayClient is fully implemented
• Supports: payments, tokenization, 3DS, Pay-by-Link

Card-Present Path (Target: Integra)

• IntegraGatewayClient handles payment actions
• IntegraPortalApiGatewayClient handles merchant management

APM Path (Target: DGW)

• DigitalGatewayGatewayClient implemented
• Routes via IGatewayClientFactory

6.3 Missing Documentation Gaps

1. ❌ No OpenAPI/Swagger specs found in repository roots
2. ❌ No explicit API versioning via Accept header (per PLT-004)
3. ⚠️ Environment configuration uses appsettings.{env}.json pattern

---

7. Related Repositories Discovered

From code analysis, these repositories interact with Planet Portal:

---

8. Configuration & Environments

8.1 Discovered Environment Configurations

From appsettings analysis:

• Local - Local development
• Integration - Integration testing
• Uat - User acceptance testing
• QA - Quality assurance
• Staging - Pre-production
• Production (implied)

8.2 Key Configuration Sections

{
  "Mongo": {
    "ConnectionString": "...",
    "DatabaseName": "...",
    "ReadPreference": "primary|secondaryPreferred",
    "TransactionLedgerCollection": "...",
    "MerchantCollection": "...",
    "PaymentActionsCollection": "...",
    "PaymentLinksCollection": "...",
    "PaymentMethodsCollection": "...",
    "TerminalCollection": "...",
    "TerminalActionsCollection": "..."
  },
  "Redis": {
    "ConnectionString": "..."
  },
  "Hangfire": {
    "DatabaseName": "...",
    "MinimumAvailableServers": 1,
    "CheckConnection": true,
    "BypassMigrations": false,
    "QueuePollInterval": "...",
    "SupportsCappedCollection": false,
    "JobExpirationTimeoutInDays": 7,
    "CancellationCheckInterval": "...",
    "WorkerCountPerProcessor": 2
  },
  "PaymentGateways": {
    "Datatrans": { "BaseUri": "...", "ApiKeyBase64": "...", "Timeout": "..." },
    "Integra": { "BaseUri": "...", "Timeout": "...", "SkipCertificateValidation": false },
    "IntegraPortalApi": { "BaseUri": "..." },
    "DigitalGateway": { "BaseUri": "...", "ApiKey": "...", "AuthorizationToken": "...", "Timeout": "..." },
    "Web2Pay": { "BaseUri": "...", "ApplicationId": "...", "Password": "...", "Timeout": "..." }
  },
  "Auth": {
    "Auth0": { "Domain": "...", "Timeout": "..." },
    "MerchantActivationAuth0": { "Domain": "...", "Timeout": "..." }
  },
  "Kafka": {
    "BootstrapServers": "...",
    "ConsumerGroup": "...",
    "Topics": { ... }
  }
}

---

Appendix A: Package References

pp-payments-api Key Dependencies

<PackageReference Include="Hangfire.Core" />
<PackageReference Include="Hangfire.Mongo" />
<PackageReference Include="MongoDB.Driver" />
<PackageReference Include="StackExchange.Redis" />
<PackageReference Include="Microsoft.AspNetCore.Authentication.JwtBearer" />

pp-transaction-consumer Key Dependencies

<PackageReference Include="KafkaFlow" />
<PackageReference Include="KafkaFlow.Microsoft.DependencyInjection" />
<PackageReference Include="MongoDB.Driver" />

---

Appendix B: Shared NuGet Packages

From WeArePlanet.* namespace analysis: