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

# EFT Pro via PayU

> Set up EFT Pro payments through PayU in Payrails, and see the currency PayU requires and the customer fields it accepts.

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

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

Accept [EFT Pro](https://docs.payrails.com/docs/integrations/payment-methods/eft-pro) payments from customers in South Africa with PayU as the payment service provider (PSP). The customer selects EFT Pro, confirms the transfer from their bank on the PayU payment page 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 EFT Pro payment through PayU:

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

## Request fields for PayU

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 | Must be `ZAR`. Payrails rejects EFT Pro requests to PayU in any other currency. |
| `meta.customer.name`, `meta.customer.lastName` | Optional | Sent to PayU as the customer's first and last name. |
| `meta.customer.email` | Optional | Sent to PayU as the customer email. |
| `meta.customer.phone.number` | Optional | Sent to PayU as the customer's mobile number. |
| `meta.customer.birthDate` | Optional | Sent to PayU as the customer's date of birth. |
| `holderReference` | Optional | Sent to PayU as your user ID for the customer. |
| `returnInfo.cancel` | Optional | Sent to PayU as the page the customer returns to when they cancel the payment. |

## Authorize an EFT Pro payment

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

```json Authorize request theme={null}
{
  "amount": {
    "value": "450.00",
    "currency": "ZAR"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "eftPro",
      "amount": {
        "value": "450.00",
        "currency": "ZAR"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Lerato",
      "lastName": "Mokoena",
      "email": "lerato.mokoena@example.com",
      "phone": {
        "countryCode": "+27",
        "number": "821234567"
      }
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "cancel": "https://example.com/cancel",
    "error": "https://example.com/error"
  }
}
```

After the customer confirms the transfer, PayU 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 PayU handles EFT Pro

* PayU processes EFT Pro as a one-step payment, so Payrails sends it with instant capture.
* PayU notifies Payrails of the final result. When the customer returns, Payrails also fetches the transaction from PayU to confirm it.
* To return funds after a successful payment, refund it.


## Related topics

- [EFT Pro](https://docs.payrails.com/docs/integrations/payment-methods/eft-pro.md)
- [UPI via PayU India](https://docs.payrails.com/docs/integrations/payment-methods/upi/payuindia.md)
- [PayU](https://docs.payrails.com/docs/integrations/payment-providers/payu.md)


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