TBC Bank Integration Service Client

Helper for working with the .NET 8.0 C# class library that provides a type-safe, immutable wrapper around TBC Bank's Integration Service Standard+ SOAP API.

Project Context

This is a .NET 8.0 class library providing a functional, immutable abstraction over TBC Bank's SOAP API. The library emphasizes type safety, immutability, and functional error handling.

Build and Test Commands

When asked to build or test:

```bash

Build the solution

dotnet build

Run all tests

dotnet test

Run a specific test

dotnet test --filter "FullyQualifiedName~TestClassName.TestMethodName"

Run the demo console application

dotnet run --project AppifySheets.TBC.IntegrationService.Client.DemoConsole

```

Architecture Guidelines

Core Design Principles

1. **Immutable Data Structures**: All data types must be immutable records or value objects

2. **Functional Programming**: Use `CSharpFunctionalExtensions` for Result pattern and error handling

3. **Type Safety**: Strong typing with specific interfaces for different transfer types

4. **SOAP Abstraction**: Complex SOAP operations wrapped in clean, type-safe API

Project Structure

`AppifySheets.TBC.IntegrationService.Client` - Main client library

- `SoapInfrastructure/` - SOAP request/response classes per operation

- `TBCSoapCaller.cs` - Main entry point for API calls

`AppifySheets.Immutable.BankIntegrationTypes` - Shared immutable types and value objects

`AppifySheets.TBC.IntegrationService.Tests` - xUnit tests with Shouldly assertions

`AppifySheets.TBC.IntegrationService.Client.DemoConsole` - Example usage

Key Components

1. **TBCSoapCaller**: Main service class handling SOAP communication with certificate authentication

2. **Request/Response IO Classes**: Type-safe wrappers for each SOAP operation (e.g., `ImportSinglePaymentOrdersRequestIo`)

3. **Transfer Type Interfaces**: Different interfaces for various transfer types (`ITransferWithinBank`, `ITransferToOtherBankNationalCurrency`, etc.)

4. **Value Objects**: Strongly-typed wrappers like `BankAccountV`, `CurrencyV`, `BankAccountWithCurrencyV`

Development Instructions

Adding New SOAP Operations

When asked to add a new SOAP operation:

1. Create request/response IO classes in `SoapInfrastructure/[OperationName]/`

2. Implement `ISoapRequestIo<TResponse>` interface on the request class

3. Use immutable records for all data structures

4. Add XML serialization attributes matching TBC's SOAP schema exactly

5. Create helper methods if the operation is complex (reference `GetAccountMovementsHelper` as example)

6. Add corresponding tests in the test project

Working with Transfer Types

When implementing or modifying transfer operations:

All transfer types must implement specific interfaces defining required fields

Use `BankTransferCommonDetails` for common transfer fields

Each transfer type has its own validation rules and required fields

Ensure immutability: use records with init-only properties

Add `PersonalNumber` field support where applicable (ongoing work)

Testing Approach

When writing tests:

Use xUnit framework with Shouldly for assertions

Mock SOAP responses for unit tests

Integration tests require valid TBC API credentials and certificates

Test both success and error scenarios

Validate immutability and type safety

Error Handling Pattern

When handling errors:

Use `Result<T>` pattern from CSharpFunctionalExtensions

Convert SOAP faults to meaningful error messages

Implement validation at multiple levels:

- Value object construction

- Request validation

- SOAP response validation

Return descriptive error messages to callers

Certificate Authentication

When working with authentication:

X.509 certificates (.pfx files) are required

Use `TBCApiCredentials` for username and password

Use `TBCApiCredentialsWithCertificate` to add certificate path and password

Never commit certificates or credentials to version control

Code Style Conventions

Use immutable records over classes where possible

Prefer functional composition over inheritance

Use descriptive, intention-revealing names

Keep SOAP infrastructure separate from business logic

Add XML documentation comments for public APIs

Follow .NET naming conventions (PascalCase for public members)

Important Notes

The `PersonalNumber` field is being added across transfer operations (work in progress)

SOAP request/response structures must match TBC's schema exactly

Value objects enforce constraints at construction time

All API calls return `Result<T>` for explicit error handling

The demo console application provides usage examples

TBC Bank Integration Service Client

TBC Bank Integration Service Client

Project Context

Build and Test Commands

Build the solution

Run all tests

Run a specific test

Run the demo console application

Architecture Guidelines

Core Design Principles

Project Structure

Key Components

Development Instructions

Adding New SOAP Operations

Working with Transfer Types

Testing Approach

Error Handling Pattern

Certificate Authentication

Code Style Conventions

Important Notes

Reviews (0)