canonical: https://jentic.com/apis/dotpay.pl/dotpay

# Dotpay Pl Dotpay API

Jentic publishes the only available OpenAPI specification for Dotpay API, keeping it validated and agent-ready. Dotpay is a Polish payment gateway used to accept domestic payment methods including BLIK, online bank transfers, and card payments. The API exposes a small surface for creating a payment, checking its status, and requesting a refund - three operations that cover the full lifecycle of an online transaction. Authentication is via an Authorization header API key, suitable for server-side integrations and automated reconciliation jobs.

## For AI agents

Create Polish online payments, check payment status, and issue refunds through Dotpay so an agent can run a complete checkout-to-reconciliation flow.

## Scope

Does not handle subscription billing, card vaulting, or fraud scoring beyond the gateway defaults - use for one-off Polish payment processing only.

## Capabilities

- Create a new payment with amount, currency, and description via POST /payment
- Check the current status of a payment by id through GET `/payment/status`
- Request a refund against a completed Dotpay payment via POST /refund
- Drive a Polish-market checkout flow that needs BLIK and bank transfer support
- Reconcile a payment lifecycle by polling status until success, decline, or timeout

## Use cases

### Polish E-Commerce Checkout

Accept payments from Polish shoppers using BLIK, online bank transfer, and card via Dotpay's hosted payment flow. The agent calls POST /payment with amount, currency, and a return URL, redirects the buyer, then polls GET `/payment/status` until the transaction settles. This unlocks the Polish market without building separate BLIK or pay-by-link integrations.

Example prompt: Create a Dotpay payment for 199 PLN via POST /payment with description 'Order #1024' and return the redirect URL the buyer should follow.

### Order Status Reconciliation

After redirecting a buyer to Dotpay, services need to confirm the payment outcome before fulfilling the order. The agent polls GET `/payment/status` with the payment id until the response shows a settled, declined, or expired state, then updates the order record accordingly. This avoids relying solely on browser callbacks that can be lost.

Example prompt: Poll GET `/payment/status` for payment id 'pay_abc123' every 30 seconds for up to 10 minutes, and mark the order as paid once the response status is 'completed'.

### Refund Processing

Issue refunds against settled Dotpay transactions when an order is cancelled or returned. The agent calls POST /refund with the original payment id and refund amount, then optionally polls `/payment/status` to confirm the refund completed. Partial refunds let support agents handle product returns without voiding the entire transaction.

Example prompt: Issue a 50 PLN partial refund for payment id 'pay_abc123' via POST /refund and confirm the refund is accepted.

### AI Agent Checkout Assistance

Through Jentic, an AI agent can handle 'charge a Polish customer 99 PLN via BLIK' by resolving the request to Dotpay's POST /payment operation. Jentic injects the API key from the vault and validates the payload schema. Setup is under an hour from sign-up, versus several days to build the auth, status polling, and refund handling directly.

Example prompt: Use Jentic search for 'create a Dotpay payment', load the /payment operation, and execute it for 99 PLN with a BLIK payment method preference.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/payment` | Create a new payment |
| GET | `/payment/status` | Check payment status |
| POST | `/refund` | Request a refund |

## Key resources

- **Payment** — Create payments and check their status.
- **Refund** — Request refunds against completed payments.

## Why Jentic

- **Setup:** Wiring the Dotpay API by hand means placing your key on the Authorization header and mapping the payment, status, and refund routes before a Polish payment goes through. Through Jentic you install once, import the Dotpay API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Dotpay takes the payment details in the request body rather than a resource-owning path, so scope by operation: limit the agent to the operations it needs, such as creating a payment or checking its status, and leave refunds out of its set. You decide which operations are in that set.
- **Credential handling:** Your Dotpay API key is stored once, encrypted, by your own Jentic One instance and injected at execution time on the Authorization header. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a Dotpay payment', and Jentic returns the POST /payment operation with its input schema so the agent calls the right endpoint without reading the Dotpay docs.

## Related APIs

- **Przelewy24 API** — Przelewy24 is the other major Polish payment gateway covering BLIK and bank transfers; choice often depends on merchant pricing.
- **Stripe API** — Stripe covers cards globally with deeper subscription tooling; Dotpay is narrower but stronger on Polish local methods.
- **Adyen Checkout API** — Adyen offers global multi-method checkout including BLIK; Dotpay is a Poland-focused alternative with a smaller surface.

## FAQ

### Why is there no official OpenAPI spec for Dotpay API?

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

Dotpay uses an API key passed in the Authorization request header. Through Jentic, that key is stored encrypted in the vault and injected at execution time, so it never appears in the agent's context.

### Can I accept BLIK payments with the Dotpay API?

Yes. POST /payment is the entry point for the full set of Dotpay-supported methods including BLIK, online bank transfers, and cards. The buyer is redirected to Dotpay to complete the chosen method, after which you reconcile via GET `/payment/status.`

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

Run pip install jentic, search for 'create a Dotpay payment', load the POST /payment operation, and execute it with amount, currency, and description fields. Jentic returns the input schema so the agent assembles a valid request without reading docs.

### Can I issue partial refunds with Dotpay?

Yes. POST /refund accepts a refund amount, so you can refund less than the original payment by passing a smaller value. Pair with GET `/payment/status` afterwards to confirm the refund landed.

### What are the rate limits for the Dotpay API?

The published spec does not declare explicit limits. Build retry-with-backoff into your client and treat 429 responses as the signal to slow down. For production traffic, contact Dotpay to confirm per-merchant thresholds.

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

Yes. Because you run Jentic One yourself, your own rules decide which Dotpay operations and credentials the agent may use. Since Dotpay takes payment details in the request body rather than a resource-owning path, you scope by operation: allow only what the agent needs, such as creating a payment with POST /payment or checking its state with GET `/payment/status`, and leave POST /refund out of its set. The agent can call nothing you have not granted, and your stored API key is injected only when it runs an operation you allowed.