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

# What Bumxpress Business does

> Understand the merchant payment platform before integrating the API.

Bumxpress Business gives merchants API access to payment collection, disbursement, transfer, customer, KYC, and webhook workflows.

The merchant API is designed for server-side integrations. Your backend creates customers, requests quotes, initiates money movement, stores returned resource IDs, and reconciles final status through webhooks or follow-up `GET` requests.

## What you can build

<CardGroup cols={2}>
  <Card title="Collect payments" icon="arrow-down-to-line" href="/guides/payins">
    Create quote-backed payins from supported customer payment rails.
  </Card>

  <Card title="Send payouts" icon="arrow-up-from-line" href="/guides/payouts">
    Disburse funds to recipients through supported local rails.
  </Card>

  <Card title="Move money across corridors" icon="route" href="/guides/transfers">
    Collect from a payer and disburse to a recipient in a two-leg flow.
  </Card>

  <Card title="Track status with webhooks" icon="webhook" href="/guides/webhooks">
    Receive asynchronous events as payment resources change state.
  </Card>
</CardGroup>

## Main resources

| Resource | Purpose                                                    |
| -------- | ---------------------------------------------------------- |
| Customer | The person or entity associated with a payment flow.       |
| KYC      | Customer identity and compliance information.              |
| Quote    | A short-lived pricing and routing lock for money movement. |
| Payin    | A collection from a payer.                                 |
| Payout   | A disbursement to a recipient.                             |
| Transfer | A two-leg collect-and-disburse flow.                       |
| Webhook  | An asynchronous event delivered to your integration.       |

## Integration model

Create requests return resource identifiers. Store those IDs in your own system and use them for reconciliation, customer support, retries, and webhook handling.