Install Jentic One Beta

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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpay1.de%2Fpayone-link" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpay1.de%2Fpayone-link" | 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.

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

GET STARTED

Start building with PAYONE Link API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use PAYONE Link 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 your Jentic One instance, 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 Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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

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

Pay1 De PAYONE Link API

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

Browse all Pay1 De APIs

Agent-ready OpenAPI document · curated by JenticPaymentsPayment ProcessingapiKey4 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Use for: I need to create a payment link for a customer, I want to check the status of an existing payment link, Retrieve all active payment links for my account, Get the details of a specific payment link by ID

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

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.

Jentic One on Github View OpenAPI Document