> ## Documentation Index
> Fetch the complete documentation index at: https://ekacare-quickstart-cleanup.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Payments

> Financial transactions for patient services within Core EMR

## Payments & Transactions

A **Payment** (or **Transaction**) represents a financial record created when a patient pays for a healthcare service. Payment records capture essential financial details required for billing, reconciliation, and reporting within the **Core EMR**.

Each payment includes information such as the **amount**, **payment method**, **receipt ID**, and the **current payment status**.

Read more : ([API Reference - Payments](/api-reference/doc-tool/payment-api/get-transaction-status)) section.

***

## Use Cases

### Patient Billing and Checkout

Record patient payments at the time of consultation, procedures, diagnostics, or other services directly within the EMR workflow.

### Multi-Mode Payment Tracking

Support and track different payment methods such as cash, card, UPI, wallets, or bank transfers under a unified transaction model.

### Receipt Generation and Reconciliation

Generate receipt IDs and maintain transaction records to support accounting, audits, and financial reconciliation.

### Partial and Split Payments

Handle scenarios where payments are made in parts or across multiple payment methods for a single visit or invoice.

### Refunds and Adjustments

Track refunded, reversed, or adjusted payments while maintaining a complete financial audit trail.

### Reporting and Financial Analytics

Enable revenue tracking, daily collections, payment status summaries, and clinic-level financial reporting.

### Integration with Practice Management Systems

Integrate payment records with billing, invoicing, and accounting systems used by hospitals and clinics.

***

## Notes & Considerations

* **Status-driven lifecycle**\
  Payments typically move through states such as initiated, completed, failed, or refunded.

* **Service linkage**\
  Payments should be associated with visits, appointments, procedures, or invoices for accurate financial mapping.

* **Auditability**\
  All updates to payment records should be traceable to support audits and compliance.

* **Gateway-agnostic**\
  Core EMR records payment outcomes while actual processing may be handled by external payment gateways.

* **Operational validation**\
  Clinics should verify completed payments before closing encounters or issuing final documents.

***

## Ideal For

* Clinics and hospitals
* Practice management systems
* Diagnostic centers
* Multi-location healthcare networks

Read more : ([API Reference - Payments](/api-reference/doc-tool/payment-api/get-transaction-status)) section.