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

# Mercoa Overview

## About Mercoa

Mercoa is an embedded financial automation platform. With Mercoa, any B2B platform can embed, offer, and monetize AP and AR automation for their users. Our full-service automation solutions allow you to launch invoice processing, approval workflows & automations, payment scheduling, billpay, working capital, email notifications, AI agents, and much more.

## Account Structure

Mercoa's account structure is designed to support complex B2B platforms with multiple customers and vendors. We use the following terminology to describe our account structure:

| Account | Description                                                                                                                                                          |
| ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| C1      | The platform/product team that embeds Mercoa (whether via our embed, React components, or API) within their product. If you are reading this, you are probably a C1. |
| C2      | The customer of a C1. A C2 is an entity that uses the C1's product and has access to Mercoa via the C1's product.                                                    |
| C3      | The counterparty of a C2. A C3 is an entity that either sends invoices to or receives invoices from a C2.                                                            |

### Accounts Payable vs. Accounts Receivable

In Mercoa's [accounts payable](/accounts-payable/creating-and-managing-payers) experience, the C2 is the payer and the C3 is the vendor.

In Mercoa's [accounts receivable](/accounts-receivable/creating-and-managing-vendors) experience, the C2 is the vendor and the C3 is the payer.

## Virtual Card Agent

Mercoa's [Virtual Card Agent](/guides/virtual-card-agent/introduction) automates the process of determining if a vendor accepts virtual card payments and then executes those payments at scale. Once you integrate Virtual Card Agent into your Bill Pay, you can utilize AI features that can:

* Automatically determine if a vendor accepts virtual card payments.
* Collect the correct payment information from vendors.
* Execute virtual card payments to vendors via email.
* Log into online portals to submit virtual card payments automatically.
* Reconcile virtual card payments after they are made.
* More coming soon!

Check out our [demo](https://mercoa.com/solutions/ai-agents) and [documentation](/guides/virtual-card-agent/introduction) for Mercoa Virtual Card Agent.

## API Object Model

Mercoa's API is based around CRUD operations organized around a set of objects that represent the data in Mercoa. Here is a simplified diagram of the object model: