canonical: https://jentic.com/apis/paylands.com/paylands

# Paylands Bizum Payment API

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.

## For AI agents

Create payment orders and process Bizum mobile payments for Spanish e-commerce transactions through the Paylands gateway.

## Scope

Does not handle card payments, refunds, subscriptions, or multi-currency transactions - use for Bizum mobile payment initiation in Spain only.

## Capabilities

- 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

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'create a Bizum payment order', load the operation schema, and execute it for a 15.00 EUR transaction

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/payment` | Create a new Bizum payment order |
| POST | `/payment/bizum/{token}` | Confirm a Bizum payment transaction |

## Key resources

- **Payment Orders** — Create payment initiation requests with amount, currency, and Bizum method
- **Bizum Confirmation** — Confirm Bizum transactions using the token from payment creation

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 59 / 100
  - AI-Readiness & Agent Experience: 51 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 69 / 100
- **View full report:** https://jentic.com/apis/paylands.com/paylands/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Paylands by hand means handling its bearer auth, choosing the right sandbox or production host, and driving Bizum payment initiation yourself. Through Jentic you install once, import the Paylands Bizum Payment API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Paylands carries the payment details in the request body, so scope your agent to the operations it needs, such as creating a Bizum payment. You choose the operations it may call, so no operation runs beyond the set you allow.
- **Credential handling:** Your Paylands bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a Bizum payment' in Spain, and Jentic returns the matching Paylands operation with its input schema including amount, currency, and payment method so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe API** — Global payment processor supporting cards, wallets, and local payment methods including Bizum
- **Adyen Checkout API** — Enterprise payment platform with broad alternative payment method coverage across Europe
- **Mollie API** — European payment gateway with iDEAL, SEPA, and card support

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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 your Jentic One instance 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.

### Can I limit what my agent is allowed to do with the Paylands Bizum Payment API?

Yes. Because you run Jentic One yourself, your own rules decide which Paylands operations the agent may call and which credentials it may use. This API exposes just two operations, creating a Bizum payment order via POST /payment and confirming a transaction via POST `/payment/bizum/{token}`, so you can allow only the ones the agent needs, such as creating a payment while withholding confirmation. Any operation outside the set you approve simply does not run.