Przelewy24 Pl Przelewy24 API
Official vendor OpenAPI document · agent-readyPaymentsPayment ProcessingapiKey3 EndpointsREST
For Agents
Programmatically register transaction, verify transaction. Covers 3 operations with apiKey authentication.
Use for: I need to register transaction, I want to verify transaction, Search for transaction, I need to access Przelewy24 API programmatically
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
Polish payment gateway REST API for online transactions and payment processing. The API exposes 3 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Przelewy24 API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Przelewy24 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.
1
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%2Fprzelewy24.pl%2Fprzelewy24" | sh2
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%2Fprzelewy24.pl%2Fprzelewy24" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Przelewy24 API.
Register transaction
Verify transaction
Get transaction
Use Cases
Patterns agents use Przelewy24 API for, with concrete tasks.
★ Payments Operations
Use the Przelewy24 API to perform payments operations programmatically. The API provides 3 endpoints covering core functionality including register transaction, verify transaction, get transaction.
Call POST /transaction/register to register transaction
Automated Transactions Management
Automate transactions operations by combining multiple Przelewy24 API endpoints. Agents can verify transaction and then get transaction in a single workflow.
Call POST /transaction/verify to verify transaction, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Przelewy24 API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'register transaction', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
3 endpoints — polish payment gateway rest api for online transactions and payment processing.
METHOD
PATH
DESCRIPTION
POST
/transaction/register
Register transaction
POST
/transaction/verify
Verify transaction
GET
/transaction/{transactionId}
Get transaction
POST
/transaction/register
Register transaction
POST
/transaction/verify
Verify transaction
GET
/transaction/{transactionId}
Get transaction
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Przelewy24 API by hand means setting the key in the Authorization header, signing transaction requests, and matching register against verify calls yourself. Through Jentic you install once, import Przelewy24 from the API Directory, store the key once, and your agent calls it.
Permission scoping
Przelewy24 puts the transaction id in the URL path for lookups (/transaction/{transactionId}), so a rule can pin your agent to reading a specific transaction. You choose the operations it may call, so state changes like registering or verifying a transaction are not included unless you add them.
Credential isolation
Your Przelewy24 API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'register a transaction' or 'check a transaction's status', and Jentic returns the matching Przelewy24 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
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
FAQs
Specific to using Przelewy24 API through Jentic.
What authentication does the Przelewy24 API use?
The Przelewy24 API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I register transaction with the Przelewy24 API?
Yes. Use the POST /transaction/register endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Przelewy24 API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I register transaction through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'register transaction'. Jentic returns the matching Przelewy24 API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Przelewy24 API have?
The Przelewy24 API exposes 3 endpoints covering transactions operations.
Can I limit what my agent is allowed to do with the Przelewy24 API?
Yes. Jentic One is self-hosted by you, so your own rules decide which Przelewy24 operations and credentials the agent may use. Because Przelewy24 carries the transaction id in the URL path for lookups (GET /transaction/{transactionId}), you can pin the agent to reading a single transaction while withholding the state-changing calls. You choose the operations it may reach, so registering (POST /transaction/register) and verifying (POST /transaction/verify) a transaction stay off limits unless you explicitly add them.
GET STARTED