> ## 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.

# 1Voucher

> Accept 1Voucher payments from customers in South Africa, and check the PSPs that process 1Voucher through Payrails.

<picture noZoom>
  ![1Voucher logo](https://assets.payrails.io/img/logos/1voucher/logo-full-bleed.svg)
</picture>

1Voucher is a prepaid voucher payment method in South Africa. Customers buy a 1Voucher with cash at a retail outlet, then pay online by redeeming the voucher PIN.

Payrails processes 1Voucher through Flutterwave. Pick the PSP below for its setup steps and request examples.

## How a 1Voucher payment works

1Voucher is a redirect payment method:

1. The customer selects 1Voucher at checkout.
2. Payrails returns a redirect URL from the PSP, and the customer goes to the PSP's payment page.
3. The customer enters their 1Voucher PIN and phone number, and confirms the payment.
4. The PSP sends the customer back to your `returnInfo` URL.
5. Payrails receives the final result from the PSP and updates the payment.

Each payment is single-use: the customer redeems a voucher for every payment. Payrails captures 1Voucher payments immediately, so a successful payment is final. To return funds, [refund the payment](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md).

## Supported currencies and countries

1Voucher supports ZAR (South African rand) as its only presentment currency.

1Voucher is available to customers based in:

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

  <tbody>
    <tr><td>**Africa**</td><td>🇿🇦 South Africa</td></tr>
  </tbody>
</table>

## Integrate 1Voucher

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

> [card]
>
> Flutterwave logo
>
> Flutterwave1Voucher via Flutterwave
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/1voucher/flutterwave.md)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[Flutterwave](https://docs.payrails.com/docs/integrations/payment-methods/1voucher/flutterwave.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 1Voucher

* **Payrails SDK:** the [Web SDK](https://docs.payrails.com/docs/sdks/web.md) shows 1Voucher when your workflow returns it as a payment option, and redirects the customer to the PSP's payment page. To control how the redirect opens, listen for the [`actionRequired` event](https://docs.payrails.com/docs/sdks/web/guides/action-required-event).
* **Payrails API:** call [lookup payment options](https://docs.payrails.com/docs/orchestration/payment-acceptance/lookup-payment-options.md), then authorize with `1voucher` 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. Don't treat the customer's return to your `success` URL as proof of payment.


## Related topics

- [1Voucher via Flutterwave](https://docs.payrails.com/docs/integrations/payment-methods/1voucher/flutterwave.md)
- [Flutterwave](https://docs.payrails.com/docs/integrations/payment-providers/flutterwave.md)
- [Multibanco via Stripe](https://docs.payrails.com/docs/integrations/payment-methods/multibanco/stripe.md)


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