> ## Documentation Index
> Fetch the complete documentation index at: https://docs.withacclaim.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Collect Overview

> Accept payments through hosted or embedded experiences, virtual accounts, or the Console. Collect payer details and reconcile incoming funds in one place.

Bring funds into your business with clarity and control.
Acclaim’s collect capabilities power incoming payments from **customers, policyholders, and partners** across payment methods and currencies.

From requesting payment to reconciling funds, every pay-in is **tracked, validated, and connected** to your workflows.

***

## How collect works

Collect is built around a simple lifecycle: **request**, **collect details**, **receive funds**, and **reconcile**.

1. **Create a payment request or provision a collection method**
   Define the amount, currency, and payer, or assign a virtual account to receive funds. Payment requests can be created via API or the Console.

2. **Collect payer details or funds**
   Use a hosted or embedded experience, or receive funds directly via bank transfer into a virtual account.

3. **Receive funds**
   The payer completes the payment using the selected method or sends funds to the assigned account.

4. **Track and reconcile**
   Monitor status, receive webhooks, and match incoming funds to your internal records.

***

## Core concepts

### Payment requests

A **payment request** represents a request for funds from a payer.

It defines:

* Amount and currency
* Payer
* Payment method options

Payment requests can be fulfilled through hosted or embedded flows.

***

### Payment methods

Payment methods define **how funds are collected**.

Examples include:

* Bank debit methods
* Cards
* Local payment methods

Available methods vary by country and currency.

***

### Virtual accounts

A **virtual account** is a bank account assigned to you to receive incoming transfers from payers.

Use virtual accounts to:

* Collect funds via **bank transfer**
* Assign unique account details to a payer or workflow
* Simplify reconciliation of incoming payments

Funds received into virtual accounts are automatically tracked and can be matched to your internal records.

***

### Payers

A **payer** represents the individual or business sending funds.

Payers can be:

* Known and stored for reuse
* Collected dynamically during the payment flow
* Associated with virtual account activity

***

### Reconciliation

All incoming payments are tracked and structured for reconciliation.

You can:

* Match payments to internal records
* Track payment status and outcomes
* Export data for reporting

***

## Ways to collect payments

Choose the integration that fits your experience:

* **Embedded elements** — integrate payment collection directly into your application
* **Hosted pages** — send a payment link for a fully managed experience
* **Virtual accounts** — receive bank transfers directly from payers
* **Console** — create and manage payments on behalf of payers

***

## Key behaviors

* Payment requests can exist **before payer details are known**
* Payment collection can be **payer-driven (hosted/embedded)** or **transfer-based (virtual accounts)**
* Payment methods and requirements vary by **country and currency**
* Status updates are delivered via **webhooks**
* All payments are **tracked from request to settlement**

***

## Summary

* Collect enables you to **request, receive, and reconcile funds**
* Payment requests and virtual accounts are the core ways to collect funds
* Hosted and embedded experiences handle payer interaction
* Every payment is **tracked and connected to your workflow**