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

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# Payzone Cash

> Accept Payzone Cash payments from customers in Morocco, and check the PSPs that process Payzone Cash through Payrails.

<picture noZoom>
  ![Payzone Cash logo](https://assets.payrails.io/img/logos/payzonecash/logo-full-bleed.svg)
</picture>

Payzone Cash lets customers in Morocco order online and pay in cash. The customer gets a payment code at checkout and presents it at a payment point in the Payzone network. Payrails processes Payzone Cash through Payzone as the payment service provider (PSP).

## How a Payzone Cash payment works

Payzone Cash is a cash voucher payment method:

1. The customer selects Payzone Cash at checkout.
2. Payrails creates a cash reservation with Payzone and returns a redirect URL to a Payrails page that shows the payment code.
3. The customer presents the code at a payment point in the Payzone network and pays in cash.
4. Payzone notifies Payrails of the payment, and Payrails updates the payment.

The payment stays pending until the customer pays. Payrails captures Payzone Cash payments immediately, so a paid payment is final. To stop a payment that is still pending, cancel it. To return funds after a paid payment, [refund it](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md).

## Supported currencies and countries

Payzone Cash supports MAD (Moroccan dirham) as its presentment currency.

Payzone Cash is available to customers based in:

<table>
  <thead>
    <tr><th>Regions</th><th>Countries</th></tr>
  </thead>

  <tbody>
    <tr><td>**Africa**</td><td>🇲🇦 Morocco</td></tr>
  </tbody>
</table>

## Integrate Payzone Cash

Choose the PSP that processes Payzone Cash for you. The guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

> [card]
>
> Payzone logo
>
> PayzonePayzone Cash via Payzone
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/payzone-cash/payzone.md)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[Payzone](https://docs.payrails.com/docs/integrations/payment-methods/payzone-cash/payzone.md)</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</td></tr>
    <tr><td>[Delayed / Manual Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✖</td></tr>
    <tr><td>[Instant Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✔</td></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</td><td>✔</td></tr>
    <tr><td>[Refund / Reverse](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md)</td><td>✔</td></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</td><td>✖</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](https://docs.payrails.com/docs/resources/payments/authorization-flags.md)</td><td>✖</td></tr>
  </tbody>
</table>

## Ways to integrate Payzone Cash

* **Payrails SDK:** the [Web SDK](https://docs.payrails.com/docs/sdks/web.md) shows Payzone Cash when your workflow returns it as a payment option.
* **Payrails API:** call [lookup payment options](https://docs.payrails.com/docs/orchestration/payment-acceptance/lookup-payment-options.md), then authorize with `payzoneCash` as the `paymentMethodCode`. The PSP guide lists the `meta` fields that PSP requires.

In both cases, confirm the final result through [webhook notifications](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status.


## Related topics

- [Payzone](https://docs.payrails.com/docs/integrations/payment-providers/payzone.md)
- [Payzone Cash via Payzone](https://docs.payrails.com/docs/integrations/payment-methods/payzone-cash/payzone.md)
- [GCash](https://docs.payrails.com/docs/integrations/payment-methods/gcash.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.