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

# Benefit via Checkout.com

> Accept Benefit debit card payments from customers in Bahrain through Checkout.com, and see how Payrails sends the reference.

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

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

Accept [Benefit](https://docs.payrails.com/docs/integrations/payment-methods/benefit) payments with Checkout.com as the payment service provider (PSP).

## 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 Benefit payment through Checkout.com:

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

## Request fields for Checkout.com

Benefit needs no method-specific fields beyond the standard [authorize fields](https://docs.payrails.com/reference/authorizeaction.md), including the `returnInfo` URLs for the redirect. **Required** fields must be present for the payment to succeed. Payrails sends **Optional** fields to the PSP when you include them.

| Field | Status | Description |
| - | - | - |
| `merchantReference` | Optional | Sent to Checkout.com as the payment reference, with every character that isn't a letter or a digit removed. |
| `meta.customer.name`, `meta.customer.lastName` | Optional | Sent to Checkout.com as the customer name. |
| `meta.customer.email` | Optional | Sent to Checkout.com as the customer email. |
| `meta.customer.phone.countryCode`, `meta.customer.phone.number` | Optional | Sent to Checkout.com as the customer phone. |
| `meta.customer.country.code` | Optional | Sent to Checkout.com as the customer country. |

## Authorize a Benefit payment

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

```json Authorize request theme={null}
{
  "amount": {
    "value": "10.000",
    "currency": "BHD"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "benefit",
      "amount": {
        "value": "10.000",
        "currency": "BHD"
      }
    }
  ],
  "meta": {
    "customer": {
      "email": "maryam.alkhalifa@example.com",
      "name": "Maryam",
      "lastName": "Al-Khalifa"
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}
```

After the customer confirms the payment, they return 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 Checkout.com handles Benefit

* Payrails creates the Benefit payment through the Checkout.com Payment Setup API. Checkout.com needs no payment token for Benefit.
* Benefit rejects references that contain spaces, dashes, or underscores. Payrails strips every character that isn't a letter or a digit from the reference before it calls Checkout.com, so `order-1234_A` becomes `order1234A`.
* If Checkout.com doesn't return a redirect for a pending Benefit payment, Payrails fails the payment, because the customer can't complete it.
* Each Benefit payment is a new customer-initiated payment.


## Related topics

- [Benefit](https://docs.payrails.com/docs/integrations/payment-methods/benefit.md)
- [Przelewy24 via Checkout.com](https://docs.payrails.com/docs/integrations/payment-methods/przelewy24/checkout-com.md)
- [Bancontact via Checkout.com](https://docs.payrails.com/docs/integrations/payment-methods/bancontact/checkout-com.md)


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