> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://beta-docs.payabli.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://beta-docs.payabli.com/_mcp/server.

# Pay in transaction lifecycle

Because each money in transaction involves several parallel processes, Payabli provides different statuses you can track. This lets you monitor both the synchronous and asynchronous activities that a transaction is involved with.

This flowchart gives a high-level overview of how the statuses all fit together.

![a diagram that gives a high level overview for transaction statuses. This diagram is fully explained in the content following this image.](/_fern-files/beta-docs.payabli.com/a691baec0a79b4f0948cb16314328289a308d2a44283e9c008fda63668ab93bd/images/generated-diagrams/transaction-lifecycle.svg)

The following example showcases how the different money in statuses give a comprehensive view of an ideal transaction's lifecycle, from initial sale to final settlement.

#### Making the transaction

A customer logs into the payment portal and submits their payment. The payment method is verified, and the transaction is authorized, meaning the funds are recognized but not yet taken. The **TransStatus** is **Authorized (11)**.

The merchant captures the transaction, and the card is charged. The transaction status changes to **Captured (1)**, securing the funds for the transaction.

The transaction status is considered final after the batch closes, and the **TransStatus** won't change from **Captured (1)** except in rare circumstances. Now, the focus shifts to tracking other statuses.

Transaction status (TransStatus) represents the status of an individual payment in the system, providing a straightforward indication of whether the payment is approved, voided, declined, and so on.

![a diagram that shows how a transaction status updates.](/_fern-files/beta-docs.payabli.com/71df2a1077f3bcf18138ed14d205e51e28f62464688a21b932a6e289fa15224d/images/generated-diagrams/money-in-transaction-status.svg)

#### Batching transactions for processing

The payment, along with others submitted that day, are grouped into a batch for processing, and the **BatchStatus** is **Open (0)**. At this stage, **TransferStatus** is **Pending (0)**.

At the cutoff time, the batch that contains the payment is closed and the **BatchStatus** changes to **Closed (1)**. The batched transactions are verified, and are prepared for the next steps. **TransferStatus** and the transaction's **SettlementStatus** should now both be **In Transit (1)**.

Batch status (BatchStatus) tracks a group (batch) of transactions, which are multiple payments being processed together.

![a diagram that shows how a batch status updates.](/_fern-files/beta-docs.payabli.com/05bbd2ec9cf597df50bfc7c41541a0fecc0390ddddb228f0102dc6e820e3d2a8/images/generated-diagrams/money-in-batch-status.svg)

#### Moving the money

The transfer process starts, with funds leaving the payment processor's account and heading to the recipient's account. The **TransferStatus** and the transaction's **SettlementStatus** both change to **Transferred (2)**.

When the funds are deposited into the recipient's account, the **TransferStatus** and the **SettlementStatus** both change to **Funded (3)**.

Once a payment reaches the 'transferred' status, you can typically expect the funds to appear in your bank account within 1-2 business days.

Transfer status (TransferStatus) monitors the actual payment transfer to the recipient's bank account.

Payment funding status (SettlementStatus) helps track an individual transaction's progress through the settlement process, monitoring the journey of the funds.

![a diagram that shows how a transfer status updates.](/_fern-files/beta-docs.payabli.com/1a31b11a5dfd2d0d0c9a3447b57e04d55176c0aa3b70e8bdbb6d67d3dd203e27/images/generated-diagrams/money-in-transfer-status.svg)