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

# Collections — All Rails

> An overview of every Payaza collection channel: hosted checkout, API gateway, virtual accounts, mobile money, and digital wallets.

<div style={{ fontSize: "16px", lineHeight: "24px" }}>
  Payaza Collections covers every way your business can accept money: hosted
  checkout, API-driven card and wallet flows, bank-transfer rails via virtual
  accounts, and regional mobile money. This page maps each rail to how you
  integrate and where to go next in these docs.
</div>

<CardGroup cols={3}>
  <Card title="Payaza Collections" icon="layer-group" href="https://payaza.africa/collections/">
    Full product overview of every collection channel Payaza supports.
  </Card>

  <Card title="Payaza Checkout" icon="cart-shopping" href="https://payaza.africa/checkout">
    Hosted checkout experience for low-code online payments.
  </Card>

  <Card title="API Reference" icon="book" href="/api-reference/introduction">
    Full endpoint list from the Payaza OpenAPI spec.
  </Card>
</CardGroup>

## Choose your collection rail

<div style={{ fontSize: "14px", lineHeight: "22px", opacity: 0.92 }}>
  Pick the channel that matches your customer journey. Many integrations combine
  rails — for example checkout for web, virtual accounts for bank transfers, and
  mobile money for wallet-first markets.
</div>

<CardGroup cols={2}>
  <Card title="Hosted Checkout" icon="cart-shopping" href="#hosted-checkout">
    Low-code online payments with Payaza-hosted pages.
  </Card>

  <Card title="API & payment gateway" icon="code" href="#api-gateway">
    Server-side collections: cards, wallets, and status APIs.
  </Card>

  <Card title="Virtual accounts" icon="building-columns" href="#virtual-account-collections">
    Receive bank transfers into dynamic or reserved account numbers.
  </Card>

  <Card title="Mobile money & regional" icon="mobile" href="#momo-regional">
    MoMo, XOF, ZAR, SLE, and OTP-assisted collections.
  </Card>

  <Card title="Apple Pay & Google Pay" icon="wallet" href="#apple-google-pay">
    Wallet-based mobile and web payments.
  </Card>
</CardGroup>

***

<span id="hosted-checkout" />

### Hosted Checkout

<div style={{ fontSize: "16px", lineHeight: "24px" }}>
  **Payaza Checkout** is the hosted checkout experience for selling online with
  minimal front-end work — ideal when you want fast time-to-market and Payaza to
  handle payment UI and security presentation.
</div>

<div style={{ fontSize: "14px", lineHeight: "22px", marginTop: "12px" }}>
  **When to use:** ecommerce, invoices with a redirect link, or any flow where
  you do not need a fully custom card form on your own domain.
</div>

<Steps>
  <Step title="Align on currency and pricing">
    Confirm supported currencies and commercial terms with your Payaza contact
    before go-live.
  </Step>

  <Step title="Configure your checkout profile">
    Set branding, return URLs, and success or failure handling to match your
    customer journey.
  </Step>

  <Step title="Reconcile with webhooks and references">
    Map Payaza transaction references to your orders the same way you would for
    API-initiated collections.
  </Step>
</Steps>

**Learn more:** [Payaza Checkout](https://payaza.africa/checkout)

***

<span id="api-gateway" />

### API & payment gateway

<div style={{ fontSize: "16px", lineHeight: "24px" }}>
  For full control, integrate the **payment gateway APIs**: direct card charges,
  optional auth/capture/void, refund and chargeback handling, and transaction
  status queries.
</div>

<div style={{ fontSize: "14px", lineHeight: "22px", marginTop: "12px" }}>
  **When to use:** custom checkout, mobile apps with native UX, or server-side
  orchestration with your own risk and retry policies.
</div>

<CardGroup cols={2}>
  <Card title="Card collection" icon="credit-card" href="/guides/card-collection">
    Charge, 3DS checks, and status queries.
  </Card>

  <Card title="Auth / capture / void" icon="lock-keyhole" href="/guides/auth-capture-void">
    Pre-authorise and settle in separate steps.
  </Card>

  <Card title="Refunds & chargebacks" icon="arrow-rotate-left" href="/guides/refunds-chargebacks">
    Post-payment reversals and disputes.
  </Card>

  <Card title="API reference" icon="book" href="/api-reference/introduction">
    Full endpoint list from the Payaza OpenAPI spec.
  </Card>
</CardGroup>

***

<span id="virtual-account-collections" />

### Virtual account collections

<div style={{ fontSize: "16px", lineHeight: "24px" }}>
  **Virtual accounts** let customers pay via bank transfer into a unique account
  number tied to an invoice, customer, or session. You generate accounts via
  API, monitor funding, and reconcile using transaction queries and
  notifications.
</div>

<div style={{ fontSize: "14px", lineHeight: "22px", marginTop: "12px" }}>
  **When to use:** large-ticket B2B, collections where cards are costly or
  unavailable, or when bank transfer is the preferred local rail.
</div>

<Card title="Virtual accounts guide" icon="building-columns" href="/guides/virtual-accounts">
  Create reserved or dynamic accounts, check status, and test funding in
  non-production environments.
</Card>

***

<span id="momo-regional" />

### Mobile money & regional collections

<div style={{ fontSize: "16px", lineHeight: "24px" }}>
  **Mobile money and regional rails** cover operator-led collections (including
  OTP steps) and multi-currency contexts such as XOF, ZAR, and SLE, using the
  subsidiary collections API for process and status.
</div>

<div style={{ fontSize: "14px", lineHeight: "22px", marginTop: "12px" }}>
  **When to use:** wallet-first markets, telco-led payments, or where card
  penetration is lower than mobile money.
</div>

<Card title="Momo, XOF & ZAR collections" icon="mobile" href="/guides/momo-collections">
  Process collection, OTP, and status by transaction reference and country code.
  Supports GHS, KES, UGX, TZS, XAF, XOF, ZAR, and SLE.
</Card>

***

<span id="apple-google-pay" />

### Apple Pay & Google Pay

<div style={{ fontSize: "16px", lineHeight: "24px" }}>
  **Apple Pay and Google Pay** provide tokenised wallet payments initiated via
  the mobile payment API, with transaction status available through the standard
  collection query endpoints.
</div>

<div style={{ fontSize: "14px", lineHeight: "22px", marginTop: "12px" }}>
  **When to use:** high-conversion mobile web and app checkout where customers
  expect one-tap wallet payment.
</div>

<Card title="Apple Pay & Google Pay" icon="wallet" href="/guides/apple-google-pay">
  Initiate wallet payments and poll for final status.
</Card>

***

## Cross-cutting practices (all rails)

<div style={{ fontSize: "14px", lineHeight: "22px" }}>
  Apply these regardless of channel so production behaviour stays predictable
  and auditable.
</div>

<AccordionGroup>
  <Accordion title="Idempotency and references">
    Generate a unique reference per collection attempt on your side; reuse it
    only when you intend a true retry of the same logical payment.
  </Accordion>

  <Accordion title="Status and webhooks">
    Treat gateway responses as provisional until your reconciliation layer
    confirms success. Poll status APIs where webhooks are delayed or missed.
  </Accordion>

  <Accordion title="Security">
    Keep API keys server-side, rotate credentials on schedule, and log without
    exposing PAN or secrets.
  </Accordion>
</AccordionGroup>

***

## Authentication

All Payaza API requests require an `Authorization` header using your Base64-encoded public API key.

```
Authorization: Payaza <base64-encoded-public-key>
```

The headers required vary slightly by collection rail:

| Rail                   | Authorization         | X-TenantID      | X-ProductID  | Content-Type       |
| ---------------------- | --------------------- | --------------- | ------------ | ------------------ |
| Card Collections       | `Payaza <base64-key>` | Not required    | Not required | `application/json` |
| Momo / XOF / ZAR / SLE | `Payaza <base64-key>` | `test` / `live` | `app`        | `application/json` |
| Apple Pay / Google Pay | `Payaza <base64-key>` | Not required    | Not required | `application/json` |
| Virtual Accounts       | `Payaza <base64-key>` | Not required    | Not required | `application/json` |
| Refunds & Chargebacks  | `Payaza <base64-key>` | Not required    | Not required | `application/json` |

<Card title="Authentication guide" icon="shield-check" href="/guides/authentication">
  Full setup instructions — retrieve your key, encode it, and make your first
  authenticated request.
</Card>