PAYONE Link API

Name: PAYONE Link API API
Brand: PAYONE Link API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment ProcessingapiKey4 EndpointsREST

For Agents

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

Connect the PAYONE Link API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PAYONE Link 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.

Install Jentic One Beta (Self-Hosted)

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 | sh

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 instance

Jentic 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 PAYONE Link API API.

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

GET STARTED

Start building with PAYONE Link API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for PAYONE Link API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use PAYONE Link API API for, with concrete tasks.

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

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.

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.

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 the Jentic vault, enabling automated invoice payment workflows.

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

4 endpoints — jentic publishes the only available openapi specification for payone link api, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

PAYONE API keys for link creation and retrieval are stored encrypted in the Jentic vault. Agents receive automatic key injection per operation type — raw API keys never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create a payment link for an invoice') and Jentic returns the matching PAYONE Link operation with parameter schemas for amount, currency, and configuration.

Time to first call

Direct PAYONE Link integration: 1-2 days for auth setup and payment link workflow testing. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

PAYONE Link API

Alternate slug for the same PAYONE Link API surface

Both slugs cover identical endpoints. Use either — the link slug is shorter.

Complementary

Stripe API

Full payment processing platform with payment links as one feature

Use Stripe for comprehensive payment processing with subscriptions and invoicing. Use PAYONE Link for focused payment link creation in European markets.

Alternative

Mollie API

European payment processor with payment link capabilities

Use Mollie for European payments with broader payment method coverage. Use PAYONE Link when you specifically need PAYONE merchant account integration for payment links.

FAQs

Specific to using PAYONE Link API API through Jentic.

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 at https://app.jentic.com/sign-up.

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.