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

# OmanNet

> Accept OmanNet debit card payments from customers in Oman, and check the PSPs that process OmanNet through Payrails.

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

OmanNet is the domestic card scheme of Oman, operated under the Central Bank of Oman. Customers pay online with the OmanNet debit card their Omani bank issued. You accept OmanNet cards through the Payrails card flow: the customer enters their card details, and you authorize the payment with `card` as the `paymentMethodCode`.

Payrails processes OmanNet through Checkout.com. Pick the PSP below for its setup steps and request examples.

## How an OmanNet payment works

An OmanNet payment is a card payment with a bank confirmation step:

1. The customer selects card payment at checkout and enters their OmanNet card details, including the cardholder name.
2. Payrails sends the card payment to the PSP. The PSP recognizes the OmanNet card from its card number.
3. Payrails returns a redirect, and the customer confirms the payment on the page of their bank, often with a one-time password (OTP).
4. The PSP notifies Payrails of the final result, and Payrails updates the payment.

Each payment is single-use: the customer confirms every payment on its own. The PSP authorizes and captures OmanNet payments in one step, 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

OmanNet supports OMR (Omani rial) as its presentment currency. OMR uses three decimal places, so send amounts such as `"12.500"`.

OmanNet is available to customers based in:

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

  <tbody>
    <tr><td>**Middle East**</td><td>🇴🇲 Oman</td></tr>
  </tbody>
</table>

## Integrate OmanNet

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

> [card]
>
> Checkout.com logo
>
> Checkout.comOmanNet via Checkout.com
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/omannet/checkout-com.md)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[Checkout.com](https://docs.payrails.com/docs/integrations/payment-methods/omannet/checkout-com.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 OmanNet

* **Payrails SDK:** the [Web SDK card form](https://docs.payrails.com/docs/sdks/web/guides/accept-card-payments.md) collects OmanNet cards like any other card. Set `showCardHolderName: true` so the form collects the cardholder name. The SDK follows the bank redirect for you. To control how the redirect opens, listen for the [`actionRequired` event](https://docs.payrails.com/docs/sdks/web/guides/action-required-event).
* **Payrails API:** collect the card data with [secure fields](https://docs.payrails.com/docs/token-vault/tokenize-payment-instruments/tokenize-cards-with-secure-fields.md) or [client-side encryption](https://docs.payrails.com/docs/token-vault/tokenize-payment-instruments/tokenize-cards-with-client-side-encryption.md), call [lookup payment options](https://docs.payrails.com/docs/orchestration/payment-acceptance/lookup-payment-options.md), then authorize with `card` as the `paymentMethodCode`. The PSP guide lists the 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

- [OmanNet via Checkout.com](https://docs.payrails.com/docs/integrations/payment-methods/omannet/checkout-com.md)
- [Authorize.net](https://docs.payrails.com/docs/integrations/payment-providers/authorize-net.md)
- [NetBanking](https://docs.payrails.com/docs/integrations/payment-methods/netbanking.md)


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