> ## 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. # Thunes > Connect Thunes to Payrails to accept JazzCash, Easypaisa, Konnect and Bank Alfalah, covering your merchant ID, API key and secret key. ![Thunes logo](https://assets.payrails.io/img/logos/thunes/logo-full-bleed.svg) > [!NOTE] > > **Who should use this guide** > > This guide is intended for merchants who: > > * Use **Payrails** as a payment orchestrator > * Use **Thunes** to accept [JazzCash](https://docs.payrails.com/docs/integrations/payment-methods/jazzcash/thunes.md), [Easypaisa](https://docs.payrails.com/docs/integrations/payment-methods/easypaisa/thunes.md), [Konnect](https://docs.payrails.com/docs/integrations/payment-methods/konnect/thunes.md) or [Bank Alfalah](https://docs.payrails.com/docs/integrations/payment-methods/bank-alfalah/thunes.md) > * Have an active Thunes merchant account *** ## Create a Thunes 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. *** ## Step 1: Choose the integration type * Select **Payment**. * Continue to the next step. *** ## Step 2: Choose the provider * Select **Thunes**. * Continue to the next step. ![A screenshot showing Thunes selected as the provider.](https://mintcdn.com/payrails-42074109/gaRJ_PXlJkN8nlyV/images/docs/thunes-image-01.png?fit=max\&auto=format\&n=gaRJ_PXlJkN8nlyV\&q=85\&s=e25b683e9e639d849f05c6c03fa2a029) *** ## Step 3: Configure your Thunes integration > [!TIP] > > **What you'll need from Thunes** > > Before you begin, make sure you have your Thunes merchant ID, API key and secret key. Thunes provides them when it sets up your account. *** ### 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_thunes`. ![A screenshot showing the integration instance name field.](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) *** ### Account details **In Payrails** | Field | Value | | :- | :- | | **Merchant ID** | Your Thunes merchant ID | ![A screenshot showing the Thunes account details fields.](https://mintcdn.com/payrails-42074109/gaRJ_PXlJkN8nlyV/images/docs/thunes-image-02.png?fit=max\&auto=format\&n=gaRJ_PXlJkN8nlyV\&q=85\&s=cb73f880ec03557a8b8c90dd19cedb0b) *** ### Credentials **In Payrails** | Field | Value | | :- | :- | | **API key** | Your Thunes API key. Payrails sends it as the Basic authorization value, so enter it exactly as Thunes provides it for Basic authentication. | | **secret key** | Your Thunes HMAC secret key. Payrails uses it to verify notifications from Thunes. | Payrails sends requests to the Thunes qualification environment in test mode and to the live environment in live mode, so use the credentials for the matching environment. ![A screenshot showing the Thunes credential fields.](https://mintcdn.com/payrails-42074109/gaRJ_PXlJkN8nlyV/images/docs/thunes-image-03.png?fit=max\&auto=format\&n=gaRJ_PXlJkN8nlyV\&q=85\&s=9bddc077431030aae88986873cfa939a) *** ### Payment methods **In Payrails** * Select **Alfa** (Bank Alfalah), **Easypaisa**, **JazzCash**, **Konnect** or any combination. ![A screenshot showing the Thunes payment method selection.](https://mintcdn.com/payrails-42074109/gaRJ_PXlJkN8nlyV/images/docs/thunes-image-04.png?fit=max\&auto=format\&n=gaRJ_PXlJkN8nlyV\&q=85\&s=0ddc878f40985ff5eb339f6c4c35c2a0) *** ### Webhooks or notifications Payrails sends its notification URL to Thunes with every payment, so you don't need to set one up in the Thunes dashboard. Payrails verifies each notification with your secret key. *** ## Request fields for Thunes Send these fields in the [authorize request](https://docs.payrails.com/reference/authorizeaction.md), in addition to the standard authorize fields. **Required** fields must be present for the payment to succeed. Payrails sends **Optional** fields to Thunes when you include them. For more about meta fields, refer to [Meta fields](https://docs.payrails.com/docs/orchestration/meta-fields.md). | Field | Status | Description | | :- | :- | :- | | `amount` | Required | Sent to Thunes as the amount and currency. | | `meta.customer.reference` | Required | Sent as the customer ID. | | `meta.customer.name` | Required | Sent as the customer's first name. | | `meta.customer.email` | Required | Sent as the customer's email. | | `meta.customer.country.code` | Required | Sent as the billing country. | | `meta.order.reference` | Required | Sent as the merchant order ID. | | `meta.customer.lastName` | Optional | Sent as the customer's last name. | Thunes payments are captured straight away, so use instant capture in your workflow. *** ## Enable the integration **In Payrails** * Select **Save account** to enable the integration. * Confirm the integration shows as **Enabled**. Your **Thunes** integration is now ready to process payments. *** ## Next steps 1. Run a test payment in the Thunes qualification environment. 2. Verify that: * Your customer is redirected to the Thunes payment page and back to your site. * The payment status updates correctly in Payrails. 3. Once verified in test mode, repeat the setup in live mode. → Continue to: [Test a payment](https://docs.payrails.com/docs/orchestration/payment-acceptance/test-payments.md) ## Related topics - [Alfa via Thunes](https://docs.payrails.com/docs/integrations/payment-methods/bank-alfalah/thunes.md) - [Konnect via Thunes](https://docs.payrails.com/docs/integrations/payment-methods/konnect/thunes.md) - [EasyPaisa via Thunes](https://docs.payrails.com/docs/integrations/payment-methods/easypaisa/thunes.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.