> For the complete documentation index, see [llms.txt](https://blufin360-api-documentation.gitbook.io/blufin360_api_documentation-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blufin360-api-documentation.gitbook.io/blufin360_api_documentation-docs/banking/overview.md).

# Overview

Use these APIs to move, collect, track, and reconcile money through the bluFin360 platform.

bluFin360 provides Banking APIs for payment workflows used in payouts, collections, reconciliation, and fund management. These APIs are designed for fintechs, merchants, marketplaces, and enterprises that need reliable, programmable access to banking rails.

Banking operations are critical for fintech, lending, insurance, marketplaces, gig platforms, and any business that handles money movement at scale.

Our Banking API stack supports six interconnected operations. Each is designed to balance speed, reliability, and operational control based on your use case:

{% stepper %}
{% step %}

### [<mark style="color:$primary;">Initiate fund transfer</mark>](/blufin360_api_documentation-docs/banking/initiate-fund-transfer.md)

Fund Transfer initiates a payout from your merchant account to any beneficiary via regulated banking rails — IMPS, NEFT, RTGS, or UPI (VPA).

Because it involves an actual fund movement through banking infrastructure, Fund Transfer is the standard method for all outbound payment operations.

**Common use cases**

* Vendor & supplier payouts
* Employee salary disbursals
* Partner & affiliate settlements
* Driver & gig worker payments

**Key characteristics**

* Supports IMPS, NEFT, RTGS, UPI
* Internal & external transfer modes
* Returns UTR on settlement
* Real-time IMPS & UPI processing
* Full transaction audit trail
  {% endstep %}

{% step %}

### [<mark style="color:$primary;">Collections</mark>](/blufin360_api_documentation-docs/banking/collections.md)

Collections generates a UPI payment instrument — an Intent Link, QR code, or Intent Data — that a payer uses to transfer money into your merchant account.

It validates the payer's account and creates a time-bound collection request with configurable validity windows, supporting all major UPI apps.

**Common use cases**

* Customer payment collection
* Order & invoice payments
* Merchant checkout flows
* In-app & mobile payment UX
* QR-based POS payments

**Key characteristics**

* Intent Link, QR, or Intent Data modes
* Optional payer account validation
* Configurable validity window
* Works with all major UPI apps
* Target device & app selection
  {% endstep %}

{% step %}

### [<mark style="color:$primary;">Check Transaction Status</mark>](/blufin360_api_documentation-docs/banking/check-transaction-status.md)

Check Transaction Status lets you query the current state of any Fund Transfer or Collection at any point using your `merchant_ref_id`.

Use it to build polling-based status UX, retry logic, or to confirm outcomes before triggering downstream workflows.

**Common use cases**

* Status polling for pending transactions
* Confirmation before order fulfilment
* Retry & fallback logic
* Reconciliation workflows
* Support & ops dashboards

**Key characteristics**

* Works for both payouts & collections
* Idempotent — safe to poll repeatedly
* Returns UTR when settled
* Minimal request body (2 fields)
  {% endstep %}

{% step %}

### [<mark style="color:$primary;">Fetch Balance</mark>](/blufin360_api_documentation-docs/banking/fetch-balance.md)

Fetch Balance syncs and returns the live available balance on your merchant account directly from the banking partner in real time.

Use it before initiating high-value transfers, for daily reconciliation, or to power balance displays in your operations dashboard.

**Common use cases**

* Pre-transfer balance checks
* Daily reconciliation & reporting
* Operations & finance dashboards
* Low-balance alerting systems

**Key characteristics**

* Live balance from the banking partner
* Returns account number, IFSC & type
* Includes sync timestamp
* Minimal request — just the account ID
  {% endstep %}

{% step %}

### [<mark style="color:$primary;">Refunds</mark>](/blufin360_api_documentation-docs/banking/refunds.md)

Refunds initiates a return of funds to the original payer against a successful collection transaction. Supports both full and partial refund amounts.

The refund is credited back to the payer's source account and is tracked with its own UTR alongside the original collection UTR for full audit traceability.

**Common use cases**

* Order cancellation refunds
* Partial service / delivery refunds
* Subscription cancellations
* Customer dispute resolution
* Failed fulfilment reversals

**Key characteristics**

* Full & partial refund amounts
* Credited to original payer source
* Linked to original collection via UTR
* Reason field for audit trail
* Only against SUCCESS collections
  {% endstep %}

{% step %}

### [<mark style="color:$primary;">Transaction status callback</mark>](/blufin360_api_documentation-docs/banking/transaction-status-callback.md)

The Transaction Status Callback delivers a real-time webhook to your configured URL the moment any transaction reaches a terminal state — `SUCCESS` or `FAILED`.

Because it is push-based, it eliminates the need for polling and enables instant downstream automation such as order fulfilment, notifications, or reconciliation triggers.

**Common use cases**

* Instant order fulfilment triggers
* Real-time payment notifications
* Automated reconciliation pipelines
* Payout confirmation to beneficiaries
* Low-latency event-driven systems

**Key characteristics**

* Push-based — no polling needed
* Covers payouts, collections & refunds
* Full transaction payload in body
* UTR included on SUCCESS
* Requires HTTP 200 acknowledgement
  {% endstep %}
  {% endstepper %}