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

# NetBanking via Pine Labs

> Set up NetBanking payments through Pine Labs in Payrails, and see how the Pine Labs payment page and refunds work.

<picture noZoom>
  ![NetBanking logo](https://assets.payrails.io/img/logos/netbanking/logo.svg)
</picture>

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

Accept [NetBanking](https://docs.payrails.com/docs/integrations/payment-methods/netbanking) payments from customers in India with Pine Labs as the payment service provider (PSP). The customer goes to a Pine Labs payment page, confirms the payment in their internet banking and returns to your site.

## Supported workflows

<table>
  <thead>
    <tr><th>Workflow</th><th>Supported</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>

## Before you begin

Complete these steps before you send your first NetBanking payment through Pine Labs:

1. Set up a Pine Labs integration in your workspace. Follow the [Pine Labs integration setup guide](https://docs.payrails.com/docs/integrations/payment-providers/pine-labs.md) if you don't have one yet. The Payrails Portal lists it as **PineLabs**.
2. Ask Pine Labs to enable NetBanking on your Pine Labs merchant account.
3. In the Payrails Portal, go to **Settings → Integrations**, open your **PineLabs** integration, select **NetBanking** under **Payment methods**, and save.
4. Add NetBanking as a [payment option](https://docs.payrails.com/docs/integrations/payment-methods/set-up-payment-methods.md) in your workflow.

## Request fields for Pine Labs

Send these fields in the authorize request, in addition to the standard [authorize fields](https://docs.payrails.com/reference/authorizeaction.md). **Required** fields must be present for the payment to succeed. Payrails sends **Optional** fields to the PSP when you include them.

| Field | Status | Description |
| - | - | - |
| `amount.currency` | Required | Send `INR`. Payrails sends the amount to Pine Labs in minor units, without a currency. |
| `meta.customer.email` | Optional | Sent to Pine Labs as the customer email. |
| `meta.customer.name`, `meta.customer.lastName` | Optional | Sent to Pine Labs as the customer's first and last name. |
| `meta.customer.phone` | Optional | Sent to Pine Labs as the customer's mobile number. |
| `meta.customer.reference` | Optional | Sent to Pine Labs as your customer ID. |
| `meta.order.billingAddress` | Optional | Sent to Pine Labs as the billing address. |
| `meta.order.deliveryAddress` | Optional | Sent to Pine Labs as the shipping address, including the recipient's name and phone. |

## Authorize a NetBanking payment

Call [authorize a payment](https://docs.payrails.com/reference/authorizeaction.md) with `netBanking` as the `paymentMethodCode`. The response includes the redirect to the Pine Labs payment page.

```json Authorize request theme={null}
{
  "amount": {
    "value": "500.00",
    "currency": "INR"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "netBanking",
      "amount": {
        "value": "500.00",
        "currency": "INR"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Aarav",
      "lastName": "Sharma",
      "email": "aarav.sharma@example.com",
      "reference": "customer-1234",
      "phone": {
        "countryCode": "91",
        "number": "9876543210"
      }
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}
```

After the customer approves the payment, Pine Labs returns them to your `success` or `error` URL. Confirm the result through [webhook notifications](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status before you fulfill the order.

## How Pine Labs handles NetBanking

* Pine Labs accepts only instant capture. Payrails captures NetBanking payments immediately.
* The customer chooses their bank from the list on the Pine Labs payment page.
* Pine Labs serves its payment pages to customers with an Indian IP address.
* When the customer returns, Payrails checks the signature on the Pine Labs response before it updates the payment.
* Payrails sends full and partial refunds to Pine Labs against the original transaction.


## Related topics

- [NetBanking](https://docs.payrails.com/docs/integrations/payment-methods/netbanking.md)
- [NetBanking via dLocal](https://docs.payrails.com/docs/integrations/payment-methods/netbanking/dlocal.md)
- [Pine Labs](https://docs.payrails.com/docs/integrations/payment-providers/pine-labs.md)


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