Transaction: transaction_id uuid identotency_id uuid from_account_id uuid to_account_id uuid amoun decimal status enum transaction_start timestamp transaction_end timestamp payments_create: user_id uuid payment_account_id uuid balance decimal currency varchar(16) status ENUM created_time timestamp update_time timestamp

Based on the described structures, a model for handling transactions and payments in Go can be proposed.

To ensure transaction idempotency, the identotency_id field is used — a unique identifier that prevents the same operation from being executed multiple times.

Example structures in Go:

type TransactionStatus string

const (
    StatusPending   TransactionStatus = "pending"
    StatusCompleted TransactionStatus = "completed"
    StatusFailed    TransactionStatus = "failed"
)

type Transaction struct {
    TransactionID    uuid.UUID
    IdempotencyID    uuid.UUID
    FromAccountID    uuid.UUID
    ToAccountID      uuid.UUID
    Amount           decimal.Decimal
    Status           TransactionStatus
    TransactionStart time.Time
    TransactionEnd   time.Time
}

type PaymentStatus string

const (
    PaymentActive   PaymentStatus = "active"
    PaymentInactive PaymentStatus = "inactive"
)

type PaymentCreate struct {
    UserID          uuid.UUID
    PaymentAccountID uuid.UUID
    Balance         decimal.Decimal
    Currency        string
    Status          PaymentStatus
    CreatedTime     time.Time
    UpdateTime      time.Time
}

Working with such structures is important:

• Use database transactions for atomic operations.
• Check IdempotencyID before creating a new transaction to avoid duplication.
• Update transaction and payment statuses based on the operation results.

This approach allows reliable management of financial operations and maintains data consistency.