Dotpay API

Name: Dotpay API API
Brand: Dotpay API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment ProcessingapiKey3 EndpointsREST

For Agents

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

Quickstart

Get started with Dotpay API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a Dotpay payment"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Dotpay API API.

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

GET STARTED

Start building with Dotpay API API

Explore with Jentic

View OpenAPI Document

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

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.

Use Cases

Patterns agents use Dotpay API API for, with concrete tasks.

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

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.

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.

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.

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

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

METHOD

PATH

DESCRIPTION

POST

/payment

Create a new payment

GET

/payment/status

Check payment status

POST

/refund

Request a refund

POST

/payment

Create a new payment

GET

/payment/status

Check payment status

POST

/refund

Request a refund

Why though Jentic?

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

Credential isolation

Dotpay API keys are stored encrypted in the Jentic vault and injected as the Authorization header at execution time. Agents receive a scoped reference rather than the raw key.

Intent-based discovery

Agents search by intent (e.g. 'create a Dotpay payment') and Jentic returns the POST /payment operation with its input schema, so the agent calls the right endpoint without reading Dotpay docs.

Time to first call

Direct Dotpay integration: 1-2 days for auth, payment creation, status polling, and refund handling. Through Jentic: under an hour from sign-up to first successful payment.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Przelewy24 API

Przelewy24 is the other major Polish payment gateway covering BLIK and bank transfers; choice often depends on merchant pricing.

Choose Przelewy24 when the merchant already has a Przelewy24 contract or when wider bank coverage is required. Choose Dotpay when the merchant is on Dotpay or wants the simpler API surface.

Alternative

Stripe API

Stripe covers cards globally with deeper subscription tooling; Dotpay is narrower but stronger on Polish local methods.

Choose Stripe when the merchant needs international card acceptance or subscriptions. Choose Dotpay when BLIK or Polish bank transfers are the priority.

Alternative

Adyen Checkout API

Adyen offers global multi-method checkout including BLIK; Dotpay is a Poland-focused alternative with a smaller surface.

Choose Adyen for multi-region rollouts that include Poland. Choose Dotpay for a Polish-only deployment with lighter integration overhead.

FAQs

Specific to using Dotpay API API through Jentic.

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

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.