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

# Bizum

> Accept Bizum mobile payments in Spain, where customers pay with the phone number linked to their bank and approve each payment in their banking app.

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

Bizum is a mobile payment method in Spain, backed by Spanish banks. Customers pay with the phone number linked to their bank account and approve each payment in their banking app. Payrails processes Bizum through Checkout.com and Redsys.

## How a Bizum payment works

Bizum is a notification-driven payment method. The customer stays on your checkout, with no redirect:

1. The customer selects Bizum at checkout, and you send their phone number in the authorize request.
2. Payrails creates the payment at your PSP, and the payment stays pending.
3. The customer approves the payment in their banking app.
4. The PSP sends the final result to Payrails as a webhook notification, and Payrails updates the payment.

Each payment is single-use: the customer approves every payment on its own. With instant capture, a successful payment is final. Redsys also supports manual capture, where the customer approves the payment first and you capture it later. To return funds, [refund the payment](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md).

## Supported currencies and countries

Bizum supports EUR (euro) as its only presentment currency.

Bizum is available to customers based in:

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

  <tbody>
    <tr><td>**Europe**</td><td>🇪🇸 Spain</td></tr>
  </tbody>
</table>

## Integrate Bizum

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

> [card]
>
> Checkout.com logo
>
> Checkout.comBizum via Checkout.com
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/bizum/checkout-com.md)

> [card]
>
> Redsys logo
>
> RedsysBizum via Redsys
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/bizum/redsys.md)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[Checkout.com](https://docs.payrails.com/docs/integrations/payment-methods/bizum/checkout-com.md)</th><th>[Redsys](https://docs.payrails.com/docs/integrations/payment-methods/bizum/redsys.md)</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</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><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><td>✔</td></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</td><td>✖</td><td>✖</td></tr>
    <tr><td>[Refund / Reverse](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md)</td><td>✔</td><td>✔</td></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</td><td>✖</td><td>✖</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](https://docs.payrails.com/docs/resources/payments/authorization-flags.md)</td><td>✖</td><td>✖</td></tr>
  </tbody>
</table>

## Ways to integrate Bizum

* **Payrails SDK:** the [Web SDK](https://docs.payrails.com/docs/sdks/web.md) shows Bizum when your workflow returns it as a payment option.
* **Payrails API:** call [lookup payment options](https://docs.payrails.com/docs/orchestration/payment-acceptance/lookup-payment-options.md), then authorize with `bizum` as the `paymentMethodCode`. The PSP guide lists the `meta` fields that PSP 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.


## Related topics

- [Bizum via Redsys](https://docs.payrails.com/docs/integrations/payment-methods/bizum/redsys.md)
- [Bizum via Checkout.com](https://docs.payrails.com/docs/integrations/payment-methods/bizum/checkout-com.md)
- [Redsys](https://docs.payrails.com/docs/integrations/payment-providers/redsys.md)


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