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

# Recipes

> End-to-end walkthroughs for corridors that need more than a standard charge.

Most collections follow the standard [mobile money charge](/guides/collections/mobile-money) flow:
you create the charge, the customer approves a prompt, you wait for a webhook.

Some markets do not work that way. These recipes cover corridors where the customer has to do
something **before or after** you create the charge — generate a code, redeem a voucher, or
confirm from a USSD menu.

<CardGroup cols={2}>
  <Card title="Africell — Gambia & DR Congo" icon="mobile" href="/recipes/africell-gmd-cdf">
    `GMD` and `CDF`. The customer confirms the payment from a USSD menu after you create the
    charge.
  </Card>

  <Card title="Orange Money — Burkina Faso" icon="mobile" href="/recipes/orange-money-burkina-faso">
    `XOF`. The customer generates a one-time payment code for the exact amount before you charge.
  </Card>

  <Card title="Orange Money — Côte d'Ivoire" icon="mobile" href="/recipes/orange-money-cote-divoire">
    `XOF`. The customer generates a 4-digit authorisation code by SMS before you charge.
  </Card>

  <Card title="OTT Voucher — Botswana" icon="ticket" href="/recipes/ott-voucher-botswana">
    `BWP`. The customer buys a voucher and gives you the PIN to redeem.
  </Card>
</CardGroup>

## What they have in common

<Steps>
  <Step title="Look up the operator code">
    Every recipe needs the right `momoOperatorId` — see
    [mobile money operators](/guides/mobile-money-operators).
  </Step>

  <Step title="Guide the customer through their step">
    Each page includes copy you can adapt for your checkout.
  </Step>

  <Step title="Create the charge">
    With any extra field the corridor requires — `otpCode` or `voucherPin`.
  </Step>

  <Step title="Confirm before fulfilling">
    A successful API response means accepted, not paid. Wait for the final status.
  </Step>
</Steps>

<Warning>
  In every one of these flows, **never ask the customer for their wallet PIN in your checkout**.
  The PIN belongs only in the operator's own prompt. Zerocash needs the one-time code or voucher
  PIN — never the wallet credential.
</Warning>