Feature

Payment System

Overview

The Payment System in Klinik Gunung Semeru handles all financial transactions related to medical services, screenings, and examinations. The system supports multiple payment methods, generates receipts, and maintains comprehensive transaction records.

Core Components

1. Transaction System

Transactions Table: General transaction records (may or may not be linked to patients)
Payments Table: Patient-specific payment records linked to medical services
AmountServices Table: Predefined service pricing and types

2. Payment Flow

Patient completes screening process
Cashier processes payment at the counter
System records transaction and updates payment status
Generates receipt (nota) for patient
Updates screening and patient payment status

3. Key Features

Multiple payment methods (cash, transfer, etc.)
Payment proof upload
Receipt generation in PDF format
Duplicate payment detection
Payment history and analytics

API Endpoints

Create Payment Transaction

POST /api/screening/payment/service

Request Body:

{
  "patient_id": 123,
  "type": "screening",
  "amount_paid": 50000,
  "payment_method": "cash",
  "amount_service_id": 1,
  "payment_proof": "file_upload"
}

Response:

{
  "success": true,
  "message": "Transaksi berhasil dibuat dan pembayaran tercatat.",
  "data": {
    "transaction": {
      "id": 456,
      "uuid": "550e8400-e29b-41d4-a716-446655440000",
      "type": "screening",
      "amount_paid": 50000,
      "payment_method": "cash"
    },
    "payment": {
      "id": 789,
      "uuid": "550e8400-e29b-41d4-a716-446655440001",
      "no_transaction": "PAY-1703123456-1234",
      "amount_paid": 50000,
      "payment_status": true
    },
    "screening_updated": 101
  }
}

Update Payment Transaction

POST /api/screening/payment/service/{id}

Request Body:

{
  "patient_id": 123,
  "type": "screening",
  "amount_paid": 55000,
  "payment_method": "transfer",
  "payment_proof": "file_upload"
}

Get Pending Payments

GET /api/screening/payment?page=1&per_page=10&search=john

Response:

{
  "data": [
    {
      "id": 123,
      "uuid": "550e8400-e29b-41d4-a716-446655440000",
      "name": "John Doe",
      "email": "john@example.com",
      "screenings": [
        {
          "id": 456,
          "payment_status": "pending"
        }
      ],
      "amountServices": [
        {
          "id": 1,
          "type": "screening",
          "amount": 50000
        }
      ],
      "physicalExaminations": [
        {
          "id": 789,
          "created_at": "2025-01-15T10:30:00Z"
        }
      ]
    }
  ],
  "meta": {
    "current_page": 1,
    "per_page": 10,
    "total": 1,
    "last_page": 1
  },
  "filters": {
    "search": "john",
    "payment_status": "pending"
  }
}

Get Payment History

GET /api/screening/payment/completed?page=1&per_page=10&search=john

Get Duplicate Payments

GET /api/screening/payment/duplicate?page=1&per_page=10&search=john

Generate Receipt (Nota)

GET /api/screening/payment/nota/{no_transaction}

Response: PDF download with filename nota_pembayaran_{no_transaction}.pdf

Delete Payment

DELETE /api/screening/payment/delete/{uuid}

Data Models

Transaction Model

Table: transactions

Fields:

uuid: Unique identifier
transaction_number: Auto-generated transaction number (TRX-{timestamp}-{random})
patient_id: Optional foreign key to patients table
type: Service type (screening, medicine, etc.)
amount_paid: Payment amount (decimal 2 places)
payment_method: Payment method (cash, transfer, etc.)
payment_proof: File path to payment proof (optional)
status: Transaction status