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.