canonical: https://jentic.com/apis/pay1.de/pay1

# Pay1 De PAYONE Link API

The PAYONE Link API creates and manages payment links for the PAYONE payment platform, so an application can generate a hosted link a customer pays through and track its state. You list the payment links that exist, create a new one, read a single link by its id, and update it. Each link carries the amount and payment details, and the API returns the link's status so a workflow knows where a payment stands.

## For AI agents

Create PAYONE payment links, list them, read a single link by id, and update an existing link. Authenticates each request with an HMAC signature using the payone-hmac-sha256 scheme.

## Scope

Does not handle refunds, settlement reporting, or customer management. Use for creating and managing PAYONE payment links only.

## Capabilities

- List the payment links that have been created
- Create a payment link a customer can pay through
- Read a single payment link and its status by id
- Update an existing payment link

## Use cases

### Agent-Driven Payment Link Creation

An AI agent connected through Jentic creates a PAYONE payment link for an order and returns the URL so a customer can pay, then reads the link later to see whether it has been paid. This lets a checkout or billing flow issue a link on request without a human opening the PAYONE dashboard.

Example prompt: Create a payment link for 49.99 EUR for this order and return the link URL

### Payment Status Tracking

A billing workflow reads a payment link by id to check its status, so it knows whether an invoice has been settled before moving on. It lists the open links to reconcile which orders are still awaiting payment.

Example prompt: List the open payment links and tell me which orders are still unpaid

### Link Maintenance

An operations tool updates an existing payment link when an order changes, adjusting its details before the customer pays. It reads the current link first, then applies the update so the change is deliberate.

Example prompt: Read the payment link for this order, then update its amount to the revised total

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/payment-links` | List all payment links |
| POST | `/v1/payment-links` | Create a payment link |
| GET | `/v1/payment-links/{linkId}` | Get payment link by id |
| PUT | `/v1/payment-links/{linkId}` | Update a payment link |

## Key resources

- **Payment links** — Hosted links a customer pays through, created, read, listed, and updated by id
- **Link status** — The state returned for a payment link, showing where a payment stands

## 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:** 0 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 67 / 100
  - AI-Readiness & Agent Experience: 58 / 100
  - Agent Usability: 94 / 100
  - Security: 0 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/pay1.de/pay1/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 the PAYONE Link API by hand means computing an HMAC signature for each request, keeping the signing secret safe, and tracking each link's status yourself. Through Jentic you install once, import PAYONE Link from the API Directory, store the secret once, and your agent calls it.
- **Permission scoping:** You choose which operations your agent may call, so you can allow reading and listing payment links while leaving creating or updating them out. Because the link id sits in the URL path, a rule can pin the agent to specific links, and every call it makes is logged.
- **Credential handling:** Your PAYONE signing secret is stored once, encrypted, by your own Jentic One instance, and the request signature is computed at execution time. The secret never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a payment link' or 'check a payment link's status', and Jentic returns the matching PAYONE Link operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Mollie API** — European payment platform with payment links and a range of payment methods
- **GoCardless API** — Bank debit platform for collecting recurring and one-off payments

## FAQ

### Is there a PAYONE Link API MCP server?

You don't need an MCP server to give your agent the PAYONE Link API. Jentic connects it directly from the API Directory: import it, store the signing secret once, and your agent can create and read payment links straight away, with no extra server to run and no tool definitions to load into the agent's context.

### Can I limit what my agent is allowed to do with the PAYONE Link API?

Yes. You choose which operations your agent may call, so you can allow reading and listing payment links while leaving creating or updating them out. Because the link id sits in the URL path, a rule can also limit the agent to specific links, and every call it makes is logged.

### What authentication does the PAYONE Link API use?

The PAYONE Link API authenticates each request with an HMAC signature, using the payone-hmac-sha256 scheme defined in its OpenAPI spec. Through Jentic the signing secret is stored encrypted by your own instance and the signature is computed at call time, so the secret never appears in the agent's prompt or logs.

### Can I create a payment link with the PAYONE Link API?

Yes. The API creates a payment link that carries the amount and payment details and returns a URL a customer can pay through. You can then read the link by id to check its status and update it if the order changes.

### What are the rate limits for the PAYONE Link API?

The OpenAPI spec does not specify rate limits for the PAYONE Link API. For current limits and integration details, see the PAYONE documentation at https://docs.payone.com.

### How do I create a PAYONE payment link through Jentic?

Import the PAYONE Link API from the Jentic API Directory, then have your agent issue a request such as 'create a payment link for this order'. Jentic matches the intent to the create-link operation and returns its input schema so the agent builds the correct request, with the signature computed at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.