Bizum
Bizum is a mobile payment solution primarily used in Spain that allows users to send and receive money in real-time through their bank's mobile app. It operates as an instant peer-to-peer (P2P) transfer service, and merchants only need the recipient's phone number to initiate transactions, making it a convenient alternative to traditional bank transfers.
Payment Method Properties
Properties | Value |
---|---|
Markets | ES |
Processing currencies | EUR |
Consumer currencies | EUR |
Settlement currencies | EUR |
Authentication methods | APP_NOTIFICATION , REDIRECT |
Minimum payment amount | 0.50 EUR |
Maximum payment amount | 999.00 EUR |
Recurring payments | No |
Separate captures | No |
Refund | Full - Partial - Multiple |
Refund validity | 365 days |
Chargeback | Yes |
Sandbox availability | PPRO simulated |
Make a Bizum Payment
One-time Bizum payments follow our standardized REDIRECT
or APP_NOTIFICATION
payment flows.
APP_NOTIFICATION
takes precedence overREDIRECT
and should only be provided if that is the intended flow.
To create a Bizum payment, you'll need to provide the following data at minimum when calling our /v1/payment-charges API:
Data Field | Required | Description |
---|---|---|
paymentMethod | Y | BIZUM |
amount.value | Y | The amount to be paid in the smallest units of the currency used. |
amount.currency | Y | EUR |
consumer.name | Y | Full name of the consumer. |
consumer.country | Y | The country where the consumer is shopping. |
authenticationSettings: REDIRECT settings.returnUrl | Y | Add the url where the consumer should be redirected to after they complete the payment. |
authenticationSettings: APP_NOTIFICATION settings | Y | The consumer phone number to be notified for payment confirmation. Validation: ^+[1-9][\d]{4,14}$ |
Request
POST /v1/payment-charges
{
"paymentMethod": "BIZUM",
"amount": {
"value": 1000,
"currency": "EUR"
},
"consumer": {
"name": "John Smith",
"country": "ES"
},
"authenticationSettings": [
{
"type": "REDIRECT",
"settings": {
"returnUrl": "https://www.your-return-page.com/"
}
},
{
"type": "APP_NOTIFICATION",
"settings": {
"instrumentProviderIdentity": "+34700000000"
}
}
]
}
REDIRECT
Response
REDIRECT
Response{
"id": "charge_X0O78tadFHrZCbGhkycPk",
"status": "AUTHENTICATION_PENDING",
// ...
"authenticationMethods": [
{
"type": "REDIRECT",
"details": {
"requestUrl": "https://redirection-target.com",
"requestMethod": "GET"
}
}
]
}
APP_NOTIFICATION
Response
APP_NOTIFICATION
Response{
"id": "charge_X0O78tadFHrZCbGhkycPk",
"status": "AUTHENTICATION_PENDING",
// ...
"authenticationMethods": [],
"authorizations": [
{
"id": "authz_ZK9uvipniCkCXXUjQCnAA",
"amount": 1000,
"status": "AUTHENTICATION_PENDING",
"createdAt": "2025-02-20T13:13:25.065Z",
"updatedAt": "2025-02-20T13:13:25.065Z"
}
}
]
}
Consumer Authentication
Bizum requires consumer authentication before the payment is authorized and captured.
REDIRECT
REDIRECT
Redirect the consumer to the url specified in the requestUrl
field. The consumer will be taken to PPRO's hosted page to provide their phone number. This will trigger a push notification from the consumer's banking app, prompting them to confirm and complete the payment.
APP_NOTIFICATION
APP_NOTIFICATION
A push notification will be immediately sent from the consumer's banking app, prompting them to confirm and complete the payment.
Handling the Payment Result
REDIRECT
REDIRECT
Once the consumer has provided their phone number, they are redirected to the returnUrl
provided in the initial payment charge creation request.
The payment charge will remain in the AUTHENTICATION_PENDING
state until the consumer confirms the payment.
After the consumer is redirected back to your site, check the payment status by making a GET /v1/payment-charges/{paymentChargeId}. Use the Status
that you received to display the payment outcome to the consumer.
Webhooks are also sent to inform you of the payment outcome. If the shopper closes the browser and doesn't return to your website, you can rely on webhooks to receive the payment result.
APP_NOTIFICATION
APP_NOTIFICATION
The payment charge will remain in the AUTHENTICATION_PENDING
state until the consumer confirms the payment.
check the payment status by making a GET /v1/payment-charges/{paymentChargeId}. Use the Status
that you received to display the payment outcome to the consumer.
Webhooks are also sent to inform you of the payment outcome.
Updated 18 days ago