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

# Kiosk

> Accept cash payments in Egypt at Aman and Masary outlets, and check the PSPs that process Kiosk through Payrails.

Kiosk lets customers in Egypt pay in cash. They get a payment reference at checkout and pay it at an Aman or Masary outlet. Payrails processes Kiosk through Paymob as the payment service provider (PSP).

## How a Kiosk payment works

Kiosk is a redirect payment method with a delayed, offline payment step:

1. The customer selects Kiosk at checkout.
2. Payrails creates a payment intention with Paymob and returns a redirect URL to the Paymob checkout page.
3. The customer gets a payment reference on the Paymob page. Paymob also emails it to the customer.
4. The customer leaves the Paymob page with the reference. Paymob doesn't redirect back for Kiosk, so the customer isn't sent to your `returnInfo` URL. The payment stays pending.
5. The customer pays the reference in cash at an Aman or Masary outlet.
6. Paymob notifies Payrails, and Payrails updates the payment.

The payment can stay pending for hours or days, until the customer pays. Payrails captures Kiosk payments immediately, so a paid reference is final.

## Supported currencies and countries

Kiosk supports EGP (Egyptian pound) as its only presentment currency.

Kiosk is available to customers based in:

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

  <tbody>
    <tr><td>**Africa**</td><td>🇪🇬 Egypt</td></tr>
  </tbody>
</table>

## Integrate Kiosk

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

> Paymob logo
>
> PaymobKiosk via Paymob
>
> [Open](https://docs.payrails.com/docs/orchestration/payment-methods/kiosk/paymob.md)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[Paymob](https://docs.payrails.com/docs/orchestration/payment-methods/kiosk/paymob.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 Kiosk

* **Payrails SDK:** the [Web SDK](https://docs.payrails.com/docs/orchestration/checkout-sdks/web) shows Kiosk 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 `kiosk` 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

- [Kiosk via Paymob](https://docs.payrails.com/docs/orchestration/payment-methods/kiosk/paymob.md)
- [Paymob](https://docs.payrails.com/docs/orchestration/integrations/paymob.md)
- [FawryPay](https://docs.payrails.com/docs/orchestration/payment-methods/fawrypay.md)


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