canonical: https://jentic.com/apis/pay1.de/payone-link

# Pay1 De PAYONE Link API

Jentic publishes the only available OpenAPI specification for PAYONE Link API, keeping it validated and agent-ready. The PAYONE Link API enables merchants to create and manage payment links that can be shared with customers for collecting payments without a full checkout integration. It provides 4 endpoints for creating payment links with configurable amounts, currencies, and expiration dates, retrieving individual link details, and listing all payment links with filtering options.

## For AI agents

Create and manage PAYONE payment links for collecting customer payments without a full checkout integration. Retrieve link status and list existing payment links.

## Scope

Does not handle direct card processing, subscriptions, or refunds - use for payment link creation and management only.

## Capabilities

- Create payment links with configurable amounts, currencies, and descriptions
- Set expiration dates and usage limits on generated payment links
- Retrieve individual payment link details including redemption status
- List all payment links with filtering by status and creation date
- Generate shareable URLs for email, SMS, or chat-based payment collection

## Use cases

### Invoice Payment Collection

Create payment links for individual invoices and send them to customers via email or messaging. Each link specifies the exact payment amount, currency, and optional description. When the customer clicks the link, they are directed to a hosted PAYONE payment page to complete the transaction without the merchant needing a full checkout integration.

Example prompt: Create a payment link for EUR 89.99 with description 'Invoice #2024-001' via POST `/v1/payment-links` and return the shareable URL

### Payment Link Status Monitoring

Track payment link redemption status by querying individual links or listing all links with status filters. The API returns whether a link is active, expired, or redeemed, along with creation timestamps and payment details. This enables automated follow-up workflows for unredeemed links.

Example prompt: Retrieve payment link details via GET `/v1/payment-links/{linkId}` and check whether the link status is 'redeemed' or still 'active'

### Batch Payment Link Management

List and manage multiple payment links using the collection endpoint with filtering options. This supports reconciliation workflows where merchants need to review all active links, identify expired unredeemed links for follow-up, or audit payment link creation history.

Example prompt: List all payment links via GET `/v1/payment-links`, filter for status 'active', and return links created more than 7 days ago that remain unredeemed

### AI Agent Payment Link Automation

AI agents create and monitor payment links through Jentic without managing API key authentication directly. Agents search for payment link operations and receive structured schemas with credential injection handled by your Jentic One instance, enabling automated invoice payment workflows.

Example prompt: Search Jentic for 'create a payment link', load the schema for POST `/v1/payment-links`, and execute with amount, currency, and description parameters

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/payment-links` | Create a new payment link |
| GET | `/v1/payment-links` | List all payment links |
| GET | `/v1/payment-links/{linkId}` | Get payment link details |
| DELETE | `/v1/payment-links/{linkId}` | Delete a payment link |

## Key resources

- **Payment Links** — Create, retrieve, and list payment links with configurable amounts and expiration

## Why Jentic

- **Setup:** Wiring PAYONE Link by hand means computing its HMAC-SHA256 request signatures and driving payment link creation and lookup yourself. Through Jentic you install once, import the PAYONE Link API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** PAYONE Link puts the link id in the URL path (`/v1/payment-links/{linkId}`), so a rule can pin your agent to reading one link: it can fetch that link and nothing else. You choose the operations it may call, so creating or deleting payment links is not included unless you add them.
- **Credential handling:** Your PAYONE key is stored once, encrypted, by your own Jentic One instance and used to sign and inject requests at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a payment link for an invoice' or 'look up a payment link', and Jentic returns the matching PAYONE Link operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **PAYONE Link API** — Alternate slug for the same PAYONE Link API surface
- **Stripe API** — Full payment processing platform with payment links as one feature
- **Mollie API** — European payment processor with payment link capabilities

## FAQ

### Why is there no official OpenAPI spec for PAYONE Link API?

PAYONE does not publish an OpenAPI specification for their Link API. Jentic generates and maintains this spec so that AI agents and developers can call PAYONE Link 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 PAYONE Link API use?

The PAYONE Link API uses API key authentication with separate keys for different operations. Keys are passed in request headers. The API uses distinct authentication schemes for creating links versus retrieving them. Through Jentic, all API keys are stored encrypted in the vault and injected per operation.

### Can I set an expiration date on payment links?

Yes. When creating a payment link via POST `/v1/payment-links`, you can specify an expiration date after which the link becomes inactive and can no longer be used for payment. Expired links are still retrievable via GET `/v1/payment-links/{linkId}` for audit purposes.

### What currencies does the PAYONE Link API support?

The PAYONE Link API supports EUR and other currencies configured for your PAYONE merchant account. The currency is specified per payment link at creation time. The payment page displayed to the customer uses the currency specified in the link.

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

Search Jentic for 'create a payment link', load the operation schema for POST `/v1/payment-links`, and execute with amount, currency, and description parameters. Jentic injects the appropriate API key automatically. Install with pip install jentic.

### Can I track whether a payment link has been used?

Yes. Retrieve the link via GET `/v1/payment-links/{linkId}` to check its current status. The response indicates whether the link is active, expired, or has been redeemed. The list endpoint also supports filtering by status to find all redeemed or active links.

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

Yes. Because you run Jentic One yourself, your own rules decide which PAYONE Link operations the agent may call, so you can allow it to look up a single link via GET `/v1/payment-links/{linkId}` while withholding creating links via POST `/v1/payment-links` or deleting them via DELETE `/v1/payment-links/{linkId}.` Since the link id sits in the URL path, a rule can pin the agent to reading one specific link and nothing else. Your PAYONE API key stays stored and injected on your instance at execution time, so the agent never handles the credential directly.