Bizum Redirect

Bizum is a widely adopted instant mobile payment solution in Spain, created by local banks working together. Customers pay directly from their bank account with only a phone number. They get instant confirmation without exposing card details.

The Global API supports Bizum Redirect in two flows:

• Single-step flow – authorize and capture the payment in one request using INSTANT_TRANSFER.
• Two-step flow – validate the customer's Bizum account in one step using INSTANT_TRANSFER_PREAUTH. Then capture the payment later (within 30 days), when you are ready to fulfill the order.

Important: Bizum does not support transaction cancellations in the two-step flow. An authorization does not "hold" funds. If the customer's balance drops before you perform the Capture, the transaction fails due to insufficient funds.

This guide covers the full instructions for both flows, including request examples, redirect handling, callback processing, and capture logic.

Requirements

Before you integrate Bizum, you need to:

• Generate an access token through the Authentication endpoint.
• Configure a public HTTPS callback_url that receives status updates after customers leave the Bizum interface.

Bizum is only available in Spain (EUR). Contact your Account Manager to enable this payment method for your seller account.

Maximum amount: Bizum transactions are capped at €15,000. The customer's bank can enforce a lower limit, so a transaction below €15,000 may still be refused.

Use case specifics

Market-specific requirements apply to every Getnet solution you integrate. Bizum is only available in Spain and only for EUR currency. To learn about the specific requirements of Spain, review the resources below before you go live:

• Currency codes
• Document types
• Local taxes and regulations

You can also use test cards to simulate specific scenarios.

Test Bizum payments

When you test Bizum payments in the sandbox environment, use the following credentials and amounts to simulate different scenarios.

Test phone number

Use the following phone number for testing Bizum transactions in the sandbox environment:

This phone number lets you complete the Bizum payment flow in the test environment without an actual Bizum account.

Test amounts

Different transaction amounts simulate different payment outcomes in the sandbox environment. Use the table below to test various scenarios:

Note: These test scenarios are only available in the sandbox environment. Production transactions process normally, based on the customer's actual Bizum account status and balance.

Shared characteristics

The table below summarizes the shared behavior and requirements for both Bizum payment flows.

Available features

Use the matrix below to confirm the scenarios currently supported for Bizum.

To enable Bizum, you must work with your Account Manager. They validate eligibility and activate the payment method.

Single-step flow (immediate capture)

Use this flow when you can fulfill the order immediately. Funds move in the same request that creates the payment.

The diagram below provides an overview of the single-step flow:

1. Create the payment request

Call the Create – Authorize endpoint with the attributes below.

The table outlines the minimum fields required to create a Bizum single-step payment.

The following sample request shows how to initialize a Bizum single-step payment.

2. Redirect the customer

3. Handle the callback

4. Verify the status (optional)

For long-running transactions, periodically check the Get Transaction endpoint or rely on Webhooks for final confirmation.

Two-step flow (validation + capture)

Important: Bizum does not support transaction cancellations in the two-step flow. An authorization does not "hold" funds. If the customer's balance drops before you perform the Capture, the transaction fails due to insufficient funds.

Choose this flow when you need to validate the customer's Bizum account first and capture the payment after fulfillment. This flow validates the account in one step and lets you capture the payment within 30 days.

The diagram below provides an overview of the two-step flow:

1. Validate the payment

The next table lists the key attributes needed for the validation request.

Here is an example request that validates a Bizum payment.

2. Redirect the customer

3. Capture the validated payment

If the capture succeeds, you receive a response like this:

4. Confirm settlement

• Payment method: Always specify the correct payment_method value (INSTANT_TRANSFER or INSTANT_TRANSFER_PREAUTH) that you used in the original transaction.

For detailed information about the refund process, full and partial refunds, timing considerations, and best practices, see the Refund a Payment guide.

Webhooks

To receive asynchronous status updates for Bizum Redirect transactions, register webhook events through the Webhooks API. Bizum webhook events work differently from card payment webhooks. You must register the specific events below to cover all transaction lifecycle transitions.

Redirect template example

• Ds_MerchantParameters — use the value from additional_data.merchant_data
• DS_SignatureVersion — use the value from additional_data.signature_version
• DS_Signature — use the value from additional_data.signature

Important: Always use the URL from the API response, because it differs between testing and production environments. The URL shown in the example below (https://sis-t.redsys.es:25443/sis/realizarPago) is for the testing environment only. See the Redirect template example for a complete implementation.

Here is a complete HTML template that you can use:

• Replace XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX in Ds_Signature with the value from additional_data.signature.
• Replace T25V2 in Ds_SignatureVersion with the value from additional_data.signature_version.
• Replace XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX in Ds_MerchantParameters with the value from additional_data.merchant_data.
• Replace the action URL with the value from additional_data._links[0].href.

After the form submits automatically, the customer goes to the Bizum checkout page, where they complete the payment. The checkout page looks similar to this:

Decode merchant_data