Przelewy24 Recursion (doPayment) API
In order to register a recurring transaction, it is necessary to send transaction registration request first to /transaction/register endpoint. . For the transaction to be performed, the `“cardData”` object must be added in the transaction registration request. ```json { "cardData": { "means": { "card": { "pan": "1234123412341234", "expYear": "2027", "expMonth": "01", "clientName": "Name and surname", "securityCode": "123" } }, "transcationType": "recurring", "traceID": "" } } ``` Description of the specific parameters of the object: - the `"card"` object contains card data such as: - `"pan"` - 16-digit card number - `"expYear"` - card expiry year - `"expMonth"` - card expiry month - `"securityCode"` – CVV/CVC code - `"transactionType"` - takes the “recurring” value - `"traceID"` - initiating transaction reference number (required for recurring, if the followinghave been provided: card, schemeToken) Provided that all the parameters in the transaction registration request are correct, a token required for `transaction/doPayment` request is returned in response.
Przelewy24 Recursion (doPayment) API is one of 13 APIs that Przelewy24 publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Recursion (doPayment). The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and rate-limit docs.
This API exposes 1 operation across 1 path, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.6.
Requests are made against 2 base URLs: https://sandbox.przelewy24.pl, https://secure.przelewy24.pl.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Przelewy24 Recursion (doPayment) API declares
1 security scheme
for authenticating requests.
It accepts HTTP basic authentication (basicAuth).
basicAuth— This is the default authentication method. User login is API REST key the password assigned to it.
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.
In order to register a recurring transaction, it is necessary to send transaction registration request first to /transaction/register endpoint. . For the transaction to be perform…
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are UnauthorizedResponse (2 properties), InvalidInputData (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Przelewy24 12
Other APIs Przelewy24 publishes across the network.
This is an independent, third-party profile of Przelewy24 Recursion (doPayment) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.