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

# Noon Payments

> Connect Noon Payments to Payrails for cards and Apple Pay, covering the region, business and application IDs, keys and webhook.

<Note>
  **Who should use this guide**

  This guide is intended for merchants who:

  * Use **Payrails** as a payment orchestrator
  * Use **Noon Payments** for card and wallet processing in Saudi Arabia, Egypt or the UAE
  * Have an active Noon Payments account with an application set up
</Note>

***

## Create a Noon Payments integration in Payrails

1. Log in to the **Payrails** portal.
2. Go to **Settings** → **Integrations**.
3. Select **Add instance** to create a new integration configuration.
4. Select the **workspaces** where this integration should be available.

<Note>
  **About workspaces**

  Workspaces determine where this integration is available. They let you isolate provider setups by region or business line, or share the same configuration across multiple workspaces.
</Note>

***

## Step 1: Choose the integration type

* Select **Payment**.
* Continue to the next step.

***

## Step 2: Choose the provider

* Select **Noon Payments**.
* Continue to the next step.

<img src="https://mintcdn.com/payrails-42074109/BFaVDhnkB7FYZ9FX/images/docs/noon-image-01.png?fit=max&auto=format&n=BFaVDhnkB7FYZ9FX&q=85&s=6aae2c6e4658c0cc5e0cbcedbeb4f93d" alt="A screenshot showing Noon Payments selected as the provider." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/noon-image-01.png" />

***

## Step 3: Configure your Noon Payments integration

<Tip>
  **What you'll need from Noon Payments**

  Before you begin, make sure you can log in to the Noon Payments merchant panel. You'll copy your business identifier, application identifier, application key and notification key from it.
</Tip>

***

### Integration instance name

> An integration instance is a specific payment provider setup in Payrails. You can create multiple instances for different regions, currencies, or business needs. Choose a clear, consistent name, as it is used in routing.

**In Payrails**

* Enter an **Instance name** for your integration, for example `merchant_noon`.

<img src="https://mintcdn.com/payrails-42074109/145W1v58K5wnDMNC/images/docs/orchestration/integrations/shared/integration-instance-name.png?fit=max&auto=format&n=145W1v58K5wnDMNC&q=85&s=470be58979509680650b0cbf8b5eecc4" alt="A screenshot showing the integration instance name field." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/orchestration/integrations/shared/integration-instance-name.png" />

***

### Account details

**In Noon Payments**

1. In the Noon Payments merchant panel, go to **Account Settings** and open **Applications**.
2. Select **+ Application**, enter a name, give it the roles your integration needs, and save.
3. Search the list again to find the new application, and copy its business identifier, application identifier and application key.

**In Payrails**

| Field | Value |
| :- | :- |
| **Region** | The region of your Noon Payments account: `KSA`, `EGYPT` or `GLOBAL`. Payrails sends your payments to the Noon Payments API for that region. |
| **Business Identifier** | Your Noon Payments business identifier |
| **Application Identifier** | Your Noon Payments application identifier |

<img src="https://mintcdn.com/payrails-42074109/145W1v58K5wnDMNC/images/docs/noon-image-02.png?fit=max&auto=format&n=145W1v58K5wnDMNC&q=85&s=7efa7473f8331de6116657c019e8a127" alt="A screenshot showing the Noon Payments account details fields." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/noon-image-02.png" />

***

### Credentials

**In Payrails**

| Field | Value |
| :- | :- |
| **Application Key** | Your Noon Payments application key. Payrails uses it with your business and application identifiers to authenticate every request. |
| **Notification Key** | The secret key of the webhook you create in Noon Payments. Payrails uses it to verify notifications from Noon Payments. Refer to [Webhooks or notifications](#webhooks-or-notifications). |

Payrails sends requests to the Noon Payments test environment in test mode and to the live environment in live mode, so use the keys for the matching environment.

<img src="https://mintcdn.com/payrails-42074109/145W1v58K5wnDMNC/images/docs/noon-image-03.png?fit=max&auto=format&n=145W1v58K5wnDMNC&q=85&s=2db4cb698d11c97d304787aa06c1c3af" alt="A screenshot showing the Noon Payments credential fields." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/noon-image-03.png" />

***

### Payment methods

**In Payrails**

* Select **Card**, **Apple Pay** or both.

<img src="https://mintcdn.com/payrails-42074109/145W1v58K5wnDMNC/images/docs/noon-image-04.png?fit=max&auto=format&n=145W1v58K5wnDMNC&q=85&s=c76f429408fefe505077adf6b7071a11" alt="A screenshot showing the Noon Payments payment method selection." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/noon-image-04.png" />

***

### Webhooks or notifications

**In Payrails**

* Copy the **Notification URL** shown under **Account configuration** at the top of the integration form.

**In Noon Payments**

1. In the merchant panel, go to **Payment Settings** → **Webhooks**.
2. Select **+ Webhook** and enter the Payrails notification URL.
3. Open the webhook you created and copy its secret key. If the webhook doesn't show in the list, select your business and search again.
4. Paste the secret key into **Notification Key** in Payrails, and save.

Payrails verifies each notification with your notification key. It also checks the status of card payments with Noon Payments until they reach a final state.

***

## Request fields for Noon Payments

Send these fields in the [authorize request](/reference/authorizeaction) for card payments, in addition to the standard authorize fields. **Required** fields must be present for the payment to succeed. Payrails sends **Optional** fields to Noon Payments when you include them. For more about meta fields, refer to [Meta fields](/docs/orchestration/meta-fields).

| Field | Status | Description |
| :- | :- | :- |
| `amount` | Required | Sent to Noon Payments as the order amount and currency. |
| `meta.order.description` | Required | Payments with a new card. Sent as the order name. |
| `meta.order` | Required | Payments with a saved card and merchant-initiated payments. |
| `meta.maxAmount` | Optional | A string, for example `"500.00"`. When you save the card, sent as the subscription's maximum amount. |
| `meta.tokenizeCc` | Optional | `true` to ask Noon Payments to tokenize the card on this payment when **Enable PAN-Based MIT** is on. |

***

## Configure Noon Payments settings

Some Noon Payments integration settings change how Payrails processes your payments. The portal shows the same description when you hover over each setting.

### Enable Mada CVV Patching

Turn on **Enable Mada CVV Patching** if you collect the CVV again when a customer pays with a saved mada card. Payrails then adds that CVV to the payment it sends to Noon Payments.

### Enable PAN-Based MIT

Turn on **Enable PAN-Based MIT** to process merchant-initiated subscription payments with the card number instead of the Noon Payments card token. Payrails then doesn't ask Noon Payments to tokenize the card on the first payment, and sends the stored card number on each merchant-initiated payment.

***

## Enable the integration

**In Payrails**

* Select **Save account** to enable the integration.
* Confirm the integration shows as **Enabled**.

Your **Noon Payments** integration is now ready to process payments.

***

## Next steps

1. Run a test payment in the Noon Payments test environment.
2. Verify that:
   * The payment appears in the Noon Payments merchant panel.
   * The payment status updates correctly in Payrails.
3. Once verified in test mode, repeat the setup in live mode.

→ Continue to: [Test a payment](/docs/orchestration/payment-acceptance/test-payments)


## Related topics

- [Integrations](/docs/orchestration/integrations.md)


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