Monitor Ledger & Transactions

Track how funds move across accounts and cards — from balance updates to transaction-level activity.

Monitor financial activity across your platform with visibility into:

  • Ledger entries → Account-level balance changes (credits and debits)
  • Transaction activity → Card-level events such as funding and spending

This allows you to track:

  • Fund movements
  • Balance adjustments
  • Card usage and spending behavior

Monitoring Lifecycle

The sequence diagram below shows how to monitor ledger and transaction activity.

sequenceDiagram
    participant App as Your application
    participant PCE as PCE
    participant Ledger as Ledger Service
    
    App->>PCE: POST /ledger/list (Debit cards)
    PCE->>Ledger: Query account entries
    Ledger-->>PCE: Credit/debit records
    PCE-->>App: 200 — Ledger entries
    
    App->>PCE: POST /card/{id}/transactionActivity (Prepaid)
    PCE-->>App: 200 — Card transactions

Scenarios

Scenario 1: Retrieve Ledger Entries for Debit Card Activity

Use this scenario to view all credits and debits on an account linked to debit cards, useful for reconciliation and auditing.

Business Context: At month-end, a corporate finance team needs to reconcile card spending with their accounting system. They pull ledger entries for all accounts to match against expense reports. Each ledger entry shows the source (card purchase), amount, timestamp, and running balance — essential data for SOX compliance audits.

Flow

sequenceDiagram
    participant Finance as Finance Team
    participant App as Your application
    participant PCE as PCE
    participant ERP as Accounting (ERP)
    
    Finance->>App: Request monthly reconciliation
    App->>PCE: POST /ledger/list
    Note right of App: Filter by account.id, date range
    PCE->>PCE: Query ledger records
    PCE-->>App: 200 — Ledger entries
    App->>ERP: Export for reconciliation

Prerequisites

  • Account (id: 88712) exists and has transaction history.
  • Ledger data is available (near real-time, up to 5 minutes latency for high-volume).
  • User has read permissions for the account.

Example Request

POST /v1/ledger/list

{
  "criteria": {
    "filters": [
      {
        "key": "account.id",
        "operator": "EQ",
        "values": ["88712"]
      },
      {
        "key": "type",
        "operator": "IN",
        "values": ["CREDIT", "DEBIT"]
      },
      {
        "key": "createdOn",
        "operator": "BETWEEN",
        "values": ["2026-06-01", "2026-06-30"]
      }
    ]
  },
  "page": 1,
  "size": 50
}

Audit Trail: All ledger entries are immutable and include createdOn timestamps. For SOX compliance, retain ledger data for a minimum of 7 years.

Example Response

{
  "status": "success",
  "data": [
    {
      "id": "led-001",
      "type": "DEBIT",
      "amount": "125.50",
      "balance": "874.50",
      "description": "Card purchase - Amazon",
      "createdOn": "2026-07-09T10:30:00Z",
      "account": {
        "id": "4011856"
      }
    },
    {
      "id": "led-002",
      "type": "CREDIT",
      "amount": "1000.00",
      "balance": "1000.00",
      "description": "Account funding",
      "createdOn": "2026-07-08T09:00:00Z",
      "account": {
        "id": "4011856"
      }
    }
  ],
  "page": 1,
  "totalPages": 1,
  "totalRecords": 2
}

Scenario 2: Retrieve Transaction Activity for Prepaid Card

Use this scenario to view the complete transaction history for a prepaid card, including loads, unloads, and spending.

Flow

sequenceDiagram
    participant App as Your application
    participant PCE as PCE
    
    App->>PCE: POST /card/{id}/transactionActivity
    PCE->>PCE: Query card transactions
    PCE-->>App: 200 — Transaction history
    Note right of App: Includes loads, holds, settlements

Prerequisites

  • Prepaid Card is issued.
  • Card has transaction history (loads or spending).

Example Request

POST /v1/customer/id/{customerId}/issuance/card/id/{cardId}/transactionActivity

{
  "page": 1,
  "size": 20
}

Example Response

{
  "status": "success",
  "data": {
    "cardId": "12345",
    "availableBalance": "372.50",
    "transactions": [
      {
        "id": "txn-001",
        "type": "SETTLEMENT",
        "amount": "27.50",
        "merchant": "Starbucks",
        "status": "COMPLETED",
        "createdOn": "2026-07-09T08:15:00Z"
      },
      {
        "id": "txn-002",
        "type": "LOAD",
        "amount": "400.00",
        "description": "Card funding",
        "status": "COMPLETED",
        "createdOn": "2026-07-08T14:00:00Z"
      }
    ]
  }
}

Scenario 3: Filter Ledger by Date Range

Use this scenario to retrieve ledger entries within a specific date range for reporting or reconciliation.

Flow

sequenceDiagram
    participant App as Your application
    participant PCE as PCE
    
    App->>PCE: POST /ledger/list
    Note right of App: Filter by lastUpdatedOn
    PCE-->>App: 200 — Filtered entries

Prerequisites

  • Account exists with transaction history.
  • Date range is within available data retention period.

Example Request

POST /v1/ledger/list

{
  "criteria": {
    "filters": [
      {
        "key": "account.id",
        "operator": "EQ",
        "values": ["4011856"]
      },
      {
        "key": "lastUpdatedOn",
        "operator": "GTE",
        "values": ["2026-07-01T00:00:00Z"]
      },
      {
        "key": "lastUpdatedOn",
        "operator": "LTE",
        "values": ["2026-07-31T23:59:59Z"]
      }
    ]
  }
}

What Can You View?

Data TypeScopeWhat It Represents
Ledger EntriesAccount-level (Debit)Credits and debits impacting account balance
Transaction ActivityCard-level (Prepaid)Funding and spending events for individual cards

View Ledger Entries (Debit Cards)

Ledger records provide a structured view of all account-level financial entries, including credits and debits resulting from card activity or funding operations.

Retrieve Ledger Entries

Use the POST /v1/ledger/list API to fetch ledger records based on specific criteria.

Supported Filters:

ParameterDescription
typeFilter by CREDIT or DEBIT entries
lastUpdatedOnRetrieve records based on last update timestamp
account.idFilter by specific account

Ledger data is available with a latency of up to 15 minutes.


View Transaction Activity (Prepaid Cards)

Transaction activity provides detailed visibility into how funds are used on Prepaid cards, including both funding and spending events.

Retrieve Transaction Activity

Use the POST /v1/customer/id/{id}/issuance/card/id/{id}/transactionActivity API to fetch transaction history for a specific card.

This data reflects:

  • Actual available balance
  • Complete transaction history

The transaction activity includes detailed information for the following event types:

  • Funding operations: Card load (adding funds) and unload (withdrawing funds) transactions.
  • Spending operations: Card activity such as hold, release, and settlements.


Did this page help you?
.readme-logo { display: none !important; }