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

# Konnect

> Accept Konnect wallet payments from customers in Pakistan, and check the PSPs that process Konnect through Payrails.

<picture noZoom>
  ![Konnect logo](https://assets.payrails.io/img/logos/konnect/logo.png)
</picture>

Konnect is a mobile wallet in Pakistan. Customers pay from their Konnect wallet balance and confirm each payment on the Thunes payment page.

Payrails processes Konnect through one payment service provider (PSP): Thunes. Open the Thunes guide below for its setup steps and request examples.

## How a Konnect payment works

Konnect is a redirect payment method:

1. The customer selects Konnect at checkout.
2. Payrails returns a redirect URL from Thunes, and the customer goes to the Thunes payment page.
3. The customer confirms the payment from their Konnect account.
4. Thunes sends the customer back to your `returnInfo` URL.
5. Payrails receives the final result from Thunes and updates the payment.

Each payment is single-use: the customer confirms every payment on its own. Payrails captures Konnect 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

Konnect supports PKR (Pakistani rupee) as its only presentment currency.

Konnect is available to customers based in:

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

  <tbody>
    <tr><td>**Asia Pacific**</td><td>🇵🇰 Pakistan</td></tr>
  </tbody>
</table>

## Integrate Konnect

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

> [card]
>
> Thunes logo
>
> ThunesKonnect via Thunes
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/konnect/thunes.md)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[Thunes](https://docs.payrails.com/docs/integrations/payment-methods/konnect/thunes.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>

Konnect is a one-off payment method: Thunes doesn't save a Konnect instrument for later merchant-initiated transactions (MIT).

## Ways to integrate Konnect

* **Payrails SDK:** the [Web SDK](https://docs.payrails.com/docs/sdks/web.md) shows Konnect when your workflow returns it as a payment option, and redirects the customer to the Thunes 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 `konnect` as the `paymentMethodCode`. The Thunes guide lists the `meta` fields Thunes 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

- [Konnect via Thunes](https://docs.payrails.com/docs/integrations/payment-methods/konnect/thunes.md)
- [Thunes](https://docs.payrails.com/docs/integrations/payment-providers/thunes.md)
- [Lookup payment options](https://docs.payrails.com/reference/lookupaction.md)


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