Paylands Bizum Payment API
★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingbearer2 EndpointsREST
For Agents
Create payment orders and process Bizum mobile payments for Spanish e-commerce transactions through the Paylands gateway.
Use for: I need to create a Bizum payment order, I want to confirm a pending Bizum transaction, Check whether a Bizum payment was completed successfully, Initiate a mobile payment for a Spanish customer
Not supported: Does not handle card payments, refunds, subscriptions, or multi-currency transactions — use for Bizum mobile payment initiation in Spain only.
Jentic publishes the only available OpenAPI specification for Paylands Bizum Payment API, keeping it validated and agent-ready. The Paylands Bizum Payment API enables merchants to create payment orders using Bizum, a popular mobile payment method in Spain. It provides two endpoints for initiating payment orders and confirming Bizum transactions via token-based authorization, supporting sandbox and production environments.
Install Jentic One Beta
Connect the Paylands Bizum Payment API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Paylands Bizum Payment API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Paylands Bizum Payment API.
Create payment orders with Bizum as the payment method for Spanish consumers
Confirm Bizum payment transactions using secure token-based authorization
Test payment flows in a dedicated sandbox environment before going live
Initiate mobile-first payment collection for Spanish e-commerce checkouts
Use Cases
Patterns agents use Paylands Bizum Payment API for, with concrete tasks.
★ E-Commerce Bizum Checkout
Accept Bizum payments from Spanish consumers at checkout. The API creates a payment order and returns a token that the customer uses to authorize the transaction via their banking app. Bizum is the most popular peer-to-peer and merchant payment method in Spain with over 25 million users, making it essential for Spanish e-commerce conversion.
Create a payment order for 29.99 EUR using Bizum payment method via POST /payment and retrieve the transaction token
Payment Confirmation Flow
After a customer authorizes a Bizum payment in their banking app, confirm the transaction status through the API. The confirmation endpoint validates the token and returns the final payment state, enabling merchants to update order status and trigger fulfillment automatically upon successful payment.
Confirm the Bizum payment transaction using POST /payment/bizum/{token} with the token received from the initial payment order
AI Agent Bizum Payment via Jentic
AI agents use Jentic to initiate Bizum payments without managing API keys or implementing the two-step payment and confirmation flow manually. Jentic stores the bearer token securely and provides the operation schemas so agents can create payment orders and confirm transactions in sequence.
Search Jentic for 'create a Bizum payment order', load the operation schema, and execute it for a 15.00 EUR transaction
Key Endpoints
2 endpoints — jentic publishes the only available openapi specification for paylands bizum payment api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/payment
Create a new Bizum payment order
POST
/payment/bizum/{token}
Confirm a Bizum payment transaction
POST
/payment
Create a new Bizum payment order
POST
/payment/bizum/{token}
Confirm a Bizum payment transaction
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Paylands API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive authenticated requests — the raw Bearer token never enters the agent's context window.
Intent-based discovery
Agents search by intent (e.g., 'create a Bizum payment') and Jentic returns the matching Paylands operation with its input schema including amount, currency, and payment method fields.
Time to first call
Direct Paylands integration: 1-2 days for auth setup and two-step flow implementation. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe API
Global payment processor supporting cards, wallets, and local payment methods including Bizum
Choose Stripe when you need multi-country payment support beyond Spain or require features like subscriptions, invoicing, and fraud detection.
FAQs
Specific to using Paylands Bizum Payment API through Jentic.
Why is there no official OpenAPI spec for Paylands Bizum Payment API?
Paylands does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Paylands Bizum Payment API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Paylands Bizum Payment API use?
The Paylands API uses Bearer token authentication. You include your API key as a Bearer token in the Authorization header with every request. Through Jentic, the API key is stored in the MAXsystem vault and injected into requests automatically — agents never handle the raw key.
Can I test Bizum payments without real transactions?
Yes. Paylands provides a sandbox environment at api.paylands.com/v1/sandbox. All endpoints work identically to production but process test transactions. Switch to the production URL api.paylands.com/v1 when ready to accept real payments.
What are the rate limits for the Paylands API?
Paylands applies rate limits based on your merchant agreement. The sandbox environment has more relaxed limits for testing. Monitor for 429 responses in production and implement backoff. Jentic handles retry logic when executing Paylands operations.
How do I create a Bizum payment through Jentic?
Search Jentic for 'create a Bizum payment order' to find the POST /payment operation. Jentic returns the input schema showing required fields like amount, currency (EUR), and payment method (bizum). Execute through Jentic and receive the transaction token for customer authorization. Install with pip install jentic.
GET STARTED