openapi: 3.0.0
info:
x-logo:
url: getfile/przelewy24-logo_mini.png
altText: LogoP24
contact:
name: Przelewy24 Support
url: https://www.przelewy24.pl/support
title: Ekspres Przelewy24 REST API Documentation Additional API functionality Additional services Mass Payments Transactions API
version: 1.0.6
description: "\n\n\n# Ekspres Przelewy24\n\nPrzelewy24 provides an authorisation and clearing system and provides payment services as a Domestic Payment Institution. <br><br/>\n<b><b>Ekspres-Przelewy24</b> service allows to quickly and effortlessly send money between accounts from different banks.</b><br/><br/>\nBelow documentation describes the process of information exchange in the course of ordering a transfer via Ekspres Przelewy24 with the use of REST API.<br/><br/>\nIn order to be able to access Ekspres API Przelewy24, first you need to [create an account](https://ekspres.przelewy24.pl/kontakt/index) in Ekspres P24 Administration Panel.\n<br/>\n# Basic notions\nThe following notions will be used for describing the operation of Ekspres Przelewy24:<br/><br/> **WWW system** – access to Ekspres Przelewy24 in the WWW version through the following websites:<ul>\n <li>[https://ekspres.przelewy24.pl](https://ekspres.przelewy24.pl) – production version,</li>\n <li>[https://testekspres.przelewy24.pl](https://testekspres.przelewy24.pl) – sandbox version.</li></ul>\n**API** – access to Ekspres Przelewy24 via REST API. <br/> **Partner** – a person / entity owning the system and submitting transfer orders to Ekspres.<br/> **Client** – a person using Ekspres services (payer or recipient of payment from Ekspres).\n\n# Modes and transfer processing\nEkspres Przelewy24 offers 3 modes of transfer processing:<ul> <li><b>Wallet</b> - transfers are processed using the funds previously paid into the wallet,</li> <li><b>P24</b> i <b>P24mobile</b> - transfers are processed only after the client has made the payment in [przelewy24.pl](https://www.przelewy24.pl),</li> Each of these modes allows the client to monitor the progress of the transfer by providing them with a dedicated URL address (available upon transfer registration).\n\n## Transfer processing in Wallet\n<b>Wallet</b> is characterized by quick processing of transfers to the client. Thanks to the funds accrued in the wallet, it is possible to effect immediate processing of a transfer registered by the Partner.<br/><br/>\n\n<img src=\"getfile/eng_wallet.png\" alt=\"Transfer w trybie Wallet\" class=\"center smallImg\">\n\n\n## Transfer processing in P24 and P24mobile\n<b>P24</b> and <b>P24mobile</b> processes payments based on the funds paid in by the Client through [przelewy24.pl](https://www.przelewy24.pl). Using this mode, the partner registers the transfer in API and, subsequently, sends a payment link to the client (alternatively, the payment link may also be sent automatically via email). Once the transaction is paid by the client in [przelewy24.pl](https://www.przelewy24.pl), the transfer registered by the partner is sent for processing.<br/><br/>\n<b>NOTE: P24mobile is analogous to P24 in that it is designed to operate with a mobile library.</b><br/><br/>\n\n<img src=\"getfile/eng_p24_p24mobile.png\" alt=\"Transfer w trybie P24 i P24mobile\" class=\"center smallImg\">\n\n\n# Codes of responses and erros\n## HTTP response codes\nEkspres Przelewy24 REST API uses response codes in HTTP headers to communicate the result of a query, potential problems and errors. <br/><br/> An inventory of possible response codes and their meanings are explained in the appropriate subchapters describing the specific methods.<br/><br/> <b>Always take note of the response code in order to react adequately to potential problems idempotent replies, etc.</b><br/><br/>\n<b>Possible response codes for all methods:</b>\n\n | Kod | Opis | Znaczenie |\n |--------------|:--------------|:------------|\n | 401 | Authorization Required | No access, check the key and the password, check if the key and the password are active and valid for this method. The code is also used to signal temporary failures. |\n | 403 | Forbidden | No access to a given method. The API key and the password are correct. Contact our staff in order to get access. |\n | 404 | Not Found | Method not found, check the URL address called. |\n | 405 | Method Not Allowed | The method used exists, but under a different http call. Check the calls for this method (GET/POST/etc.).|\n | 415 | Unsupported Media Type | The „Content-Type” value used is not allowed or a required header is missing. Inventory of allowed values available at <a href=\"#section/General-structures-of-queries-and-responses/General-query-format\"><b>General query format</b></a>. |\n | 500 | Internal Server Error | Server error, if the error recurs, contact our staff and provide the whole query processed, as well as your API key. |\n | 503 | Service Unavailable | Service temporarily unavailable due to a failure or planned upgrade. |\n\n\n## Error codes\nError codes appear in the output object of a query that ended with an error and, if it’s possible, indicate its cause. This allows to precisely establish the cause of the error and triggers an automatic reaction / error notification. <br/><br/>\nError codes are divided into the following groups:<ul> <li><b>1xxx</b> – input parameter validation error (the query contains an error),</li> <li><b>2xxx, 3xxx</b> – transfer registration error (the query is correct, but the transfer cannot be processed, e.g. due to insufficient funds),</b> <li><b>9xxx</b> – external services error (API failure caused by unavailability of a related service necessary to process the transfer, e.g. currency exchange),</li> <li><b>10000</b> – internal error (failure of Ekspres Przelewy24 REST API).</li></ul>\n<b>NOTE! When implementing API error service, in order to identify the error, rely solely on the codes, as the “description” parameter may change and constitutes additional information only!</b><br/><br/>\nThe table below presents error codes <b>input parameter validation:</b>\n\n | Error code | Description |\n |--------------|:--------------|\n | 1001 | The value of parameter <b>parameter_name</b> contains illicict characters |\n | 1002 | Parameter <b>parameter_name</b> value must not be empty |\n | 1003 | Passwords are not identical |\n | 1004 | The password must consist of at least 8 characters and contain small and capital letters and digits |\n | 1005 | Incorrect email address |\n | 1006 | Incorrect postal code |\n | 1007 | Incorrect country code |\n | 1008 | Incorrect amount |\n | 1009 | The <b>parameter</b> value submitted is not a correct integer |\n | 1010 | Incorrect currency |\n | 1011 | Incorrect account number |\n | 1012 | Incorrect URL address |\n | 1013 | Transaction type not serviced |\n | 1014 | Incorrect field value |\n | 1015 | Current transfer status prevents this operation, or incorrect transfer object |\n | 1016 | Incorrect date format / incorrect date |\n | 1017 | Incorrect query signature |\n | 1018 | Parameter value too long |\n | 1019 | IBAN number submitted has been blocked |\n\n<br/>The table below presents <b>transfer registration error codes:</b>\n\n | Error code | Description |\n |--------------|:--------------|\n | 2001\t| Bank unavailable |\n | 2002 |\tInsufficient funds in wallet |\n | 2003\t| Limit for a single transfer has been exceeded |\n | 2004\t|\tDaily limit on the amount of transfers paid has been exceeded |\n | 2005\t| Transfer ID not recognised |\n | 2006\t| Refund amount provided exceeds the transfer value available |\n | 2007\t| Access denied |\n | 2008\t| Incorrect transfer ID |\n | 2009\t| Transfer limit exceeded |\n | 2010\t| Transfer already returned in P24 mode |\n | 3000\t| Incorrect ID query |\n | 3001\t| Unknown sessionId in P24 mode |\n\n<br/>The table below presents <b>error codes for external services:</b>\n\n | Error code | Description |\n |--------------|:--------------|\n | 9001 |\tTransfer processing error. Contact the customer service department and provide the query ID |\n | 9002 |\tCurrency exchange error. Please, try again |\n\n<br/>The table below presents the <b>remaining error codes:</b>\n\n | Error code | Description |\n |--------------|:--------------|\n | 10000 |\tInternal error. Please, contact the customer service department and provide the query ID |\n\n\n\n# General structures of queries and responses\n## General query format\n\n API queries may be processed using any library that allows HTTPS protocol-based communication. Allowed Content-Type values:<ul>\n <li><b>application/json</b> – queries sent in JSON format,</li>\n <li><b>application/x-www-form-urlencoded</b> – queries sent as POST (urlencoded).</li></ul>\n\n <b>Required coding to UTF-8.</b><br/>\n\n Sample PHP code with the use of cURL\n ```php\n <?php\n $process = curl_init('https://endpoint/ekspres/v1/balance');\n // Content-Type header required\n curl_setopt(\n $process,\n CURLOPT_HTTPHEADER,\n array('Content-Type: application/json')\n );\n // Basic Auth authentication\n curl_setopt($process, CURLOPT_USERPWD, 'api-key' . \":\" . 'api-pass');\n curl_setopt($process, CURLOPT_RETURNTRANSFER, true);\n $return = json_decode(curl_exec($process));\n echo json_encode($return, JSON_PRETTY_PRINT) . \"n\";\n curl_close($process);\n ```\n\n## General response format\nA correct method call in Ekspres Przelewy24 REST API will generate a response in the form of a JSON object, in the format dependent on the method called.<br/> <p style=\"border:1.5px; border-style:dashed; border-color:#FF0000; padding: 1em;\"> <b>NOTE!</b><br/><br/> All the responses returned by API are <b>UTF-8-coded JSON objects without “slash” sign filters and unicode characters!</b><br/><br/> All the responses are returned using the following method:<br/> json_encode($response, JSON_UNESCAPED_UNICODE | JSON_UNESCAPED_SLASHES)<br/><br/> For more information see [PHP documentation](https://www.php.net/manual/en/json.constants.php). </p><br/>\nIn the case of some errors, e.g. internal error 500 or authorisation error 401, the same http code will be returned without additional information in the body. These are the cases when the system does not have any more information on the error or does not want to make it available (for instance, due to lack of authorisation). <br/><br/>\n\n When most errors are generated, GeneralErrorObject is returned (in addition to the relevant http code) with additional details:<br/>\n\n <b>GeneralErrorObject:</b>\n\n | Field name | Type | Description |\n |--------------|:--------------:|:------------|\n | code | int | General <a href=\"#section/Codes-of-responses-and-erros/Error-codes\"><b>error code</b></a> |\n | description | string | Error details |\n\n <p style=\"color:darkblue; font-size:17px\"><b>Przykład odpowiedzi z obiektem GeneralErrorObject:</b></p>\n\n ```html\n HTTP/1.1 400 Bad Request\n Content-Type: application/json\n\n {\n „error”: {\n „code”: 1011,\n „description”: „Given IBAN value ”iban” is not valid”\n }\n }\n ```\n\n\n# Environments\n## Production environment\nEvery request is differentiated by its own unique request URL. This way Ekspres P24 knows which API-function you want to access. Combined with the base URL for either the production- or test-environment, you will get the complete API-URL.\n\nBase URL production system:<br/> https://secure.przelewy24.pl/express/v1\n\n## Test environment\nDuring implementation of the mechanisms in merchant’s system, it is recommended to use test environment. Test environment allows to reproduce system functionalities without making actual payments. <br><br>\nTest environment endpoint:<br> https://sandbox.przelewy24.pl/express/v1 <br><br>\n**<u>The test version does not effect transfers and requires separate login keys.</u>**\n\n# IP server addresses\nWe recommend script protection against suspicious calls using address filtering for incoming connections. IP server ranges for the P24 servers: <br><br> <font class = \"right\"><b>5.252.202.255 , 5.252.202.254</b></font><br> <font class = \"right\"><b>20.215.81.124</b></font><br> <font class = \"right\"><b>193.178.213.0/24</b></font><br> <font class = \"right\"><b>91.220.177.0/24</b></font><br> <font class = \"right\"><b>20.215.183.48/28</b></font><br> <font class = \"right\"><b>134.112.88.8/29</b></font><br>\n\n\n# API Access\nAuthentication is effected with the Basic Auth mechanism, which uses a REST API key (as a login) and the password assigned to it. Generating the API key is possible upon logging on to one’s account in the <a href=\"#section/Basic-notions\"><b>WWW System</b></a> (left-hand menu, tab “API Users” -> “REST User List”). A single user may possess a few API access keys.\n# Authentication\n<!-- Redoc-Inject: <security-definitions> -->\n"
servers:
- url: https://sandbox.przelewy24.pl
description: Sandbox server (uses test data)
- url: https://secure.przelewy24.pl
description: Production server (uses live data)
tags:
- name: Additional services Mass Payments Transactions
x-displayName: Mass Payments Transactions
description: 'Mass Payment Identification System is an easy way for a payer to make a payment to an individual bank account created. For a payer wishing to make a traditional transfer, an individual bank account is generated to which he makes the payment. <br> <br>
'
paths:
/api/v1.1/transaction/register/simp:
post:
tags:
- Additional services Mass Payments Transactions
summary: Mass payments transaction register
description: Before sending a transaction request, save its data to the Partner's local database. In particular, the session ID and transaction amount information should be saved.<br/> <br/>The request takes analogous values to the request <a href="#tag/Transaction-service-API/paths/~1v1.1~1transaction~1register/post"><b> transaction/register</b></a>, except for two additional parameters used when requesting <a href="#tag/Additional-services-SIMP-Transactions/paths/~1v1~1transaction~1register~1simp/post"><b> transaction/register/simp</b></a> czyli <b>simpCountryCode</b> and <b>simpClientId</b>.
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/TransactionRegistrationSIMPBody'
responses:
'200':
description: Successful operation
content:
application/json:
schema:
$ref: '#/components/schemas/SIMPTransactionRegistrationResponse'
'400':
description: Invalid input data
content:
application/json:
schema:
$ref: '#/components/schemas/SIMPResponse400'
'401':
description: Not authorized
content:
application/json:
schema:
$ref: '#/components/schemas/UnauthorizedResponse'
'409':
description: Conflict
content:
application/json:
schema:
$ref: '#/components/schemas/SIMPConflict'
'500':
description: Undefined error
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorCodeResponse'
security:
- basicAuth: []
/api/v2/transaction/by/sessionId/{sessionId}:
get:
tags:
- Additional services Mass Payments Transactions
summary: Data about transaction via sessionID
description: The method returns transaction information based on the <b>sessionId</b> field. For a single sessionId within a SIMP payment, multiple payments can be made on the IBAN, hence the API can return multiple objects.
parameters:
- in: path
name: sessionId
schema:
type: string
required: true
description: SessionId of the transaction given during transaction registration
responses:
'200':
description: Successful operation
content:
application/json:
schema:
$ref: '#/components/schemas/SIMPGetTransactionBySessionId200'
'400':
description: Invalid input data
content:
application/json:
schema:
$ref: '#/components/schemas/InvalidInputData'
'401':
description: Incorrect Authentication
content:
application/json:
schema:
$ref: '#/components/schemas/UnauthorizedResponse'
'500':
description: Undefined error
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorCodeResponse'
security:
- basicAuth: []
components:
schemas:
SIMPGetTransactionBySessionId200:
properties:
data:
type: array
items:
$ref: '#/components/schemas/SIMPTransactionBySessionIdResponse200'
responseCode:
type: number
default: 0
type: object
InvalidInputData:
properties:
error:
type: string
default: Invalid input data
example: Invalid input data
code:
type: number
default: 400
example: 400
UnauthorizedResponse:
properties:
error:
type: string
default: Incorrect authentication
example: Incorrect authentication
code:
type: number
default: 401
example: 401
AdditionalProperties:
properties:
shipping:
type: object
description: Additional shipping information
properties:
type:
type: integer
description: Type of shipment:<br> 0 - courier<br>1 - delivery point<br>2 - parcel locker<br> 3 - package in a shop
enum:
- 0
- 1
- 2
- 3
address:
type: string
description: 'Shipment address: street and number'
zip:
type: string
description: Shipment zip code
city:
type: string
description: Shipment city
country:
type: string
description: Shipment country
required:
- type
- address
- zip
- city
- country
PSU:
type: object
description: 'Payment Service User<br> <b><font color = "#DB2053">IMPORTANT!:</font></b><br> Object required when using methods <b><a href="#tag/BLIK-API/paths/~1api~1v1~1paymentMethod~1blik~1chargeByCode/post">blikChargeByCode</a></b> or <b><a href="#tag/BLIK-API/paths/~1api~1v1~1paymentMethod~1blik~1chargeByAlias/post">blikChargeByAlias</a></b>.
'
properties:
IP:
type: string
description: IPv4 or IPv6
userAgent:
type: string
maxLength: 255
description: UserAgent is a string identifying the browser and operating system.
SIMPConflict:
properties:
error:
type: string
example: Conflict
code:
type: number
example: 409
SIMPTransactionRegistrationResponse:
properties:
data:
properties:
token:
type: string
description: Token
iban:
type: string
description: IBAN
example: PL59105000996912000444444341
companyName:
type: string
description: Company name
type: object
responseCode:
type: string
default: '0'
SIMPResponse400:
properties:
error:
type: string
example: Invalid simpClientId
code:
type: number
example: 400
cardData:
type: object
description: <b><font color = "#DB2053">IN PREPARATION!</font></b> An object containing card data
discriminator:
propertyName: transactionType
mapping:
recurring: '#/components/schemas/recurring'
standard: '#/components/schemas/other2'
initial: '#/components/schemas/other'
1click: '#/components/schemas/other2'
properties:
means:
type: object
properties:
card:
type: object
properties:
pan:
type: string
description: Payment card number (PAN - personal account number)
expYear:
type: integer
description: The year in which the card expires
expMonth:
type: integer
description: The month in which the card expires
clientName:
type: string
description: Name and surname of the card holder
securityCode:
type: string
description: CVV/CVC code
required:
- pan
- expYear
- expMonth
- clientName
referenceNumber:
type: object
properties:
id:
type: string
description: Reference number (token assigned by P24)
securityCode:
type: string
description: Security code
required:
- id
schemeToken:
type: object
properties:
pan:
type: string
description: Token number
expYear:
type: integer
description: The year in which the card expires
expMonth:
type: integer
description: The month in which the card expires
securityCode:
type: string
description: Cryptogram
eci:
type: string
description: The Electronic Commerce Indicator
type:
type: string
description: Typ tokenu
enum:
- visaToken
- mcToken
- visaMobile
- applepay
- googlepay
required:
- pan
- expYear
- expMonth
- type
xPayPayload:
type: object
properties:
payload:
type: string
description: Base64 encrypted payment payload
type:
type: string
description: Payment type
enum:
- applepay
- googlepay
required:
- payload
- type
transactionType:
type: string
description: 'Transaction type:<br> - <b>standard</b> - standard transaction<br> - <b>initial</b> - 1click or recurring initialization transaction. Launched in SCA mode<br> - <b>1click</b> - transaction with a saved card in the presence of the customer<br> - <b>recurring</b> - recurring transaction<br>
'
required:
- means
- transactionType
TransactionRegistrationSIMPBody:
type: object
properties:
merchantId:
name: merchantId
in: formData
description: Merchant identification number
type: integer
posId:
name: posId
in: formData
description: Shop identification number (defaults to merchant ID)
type: integer
sessionId:
name: sessionId
in: formData
description: Unique identifier from merchant's system
type: string
maxLength: 100
amount:
name: amount
in: formData
description: Transaction amount expressed in lowest currency unit, e.g. 1.23 PLN = 123
type: integer
currency:
name: currency
in: formData
description: Currency compatible with ISO, e.g. PLN
type: string
maxLength: 3
default: PLN
description:
name: description
in: formData
description: Transaction description
type: string
maxLength: 1024
email:
name: email
in: formData
description: Customer's e-mail
type: string
maxLength: 50
client:
name: client
in: formData
description: Customer's first name and surname
type: string
maxLength: 40
address:
name: address
in: formData
description: Customer's address
type: string
maxLength: 80
zip:
name: zip
in: formData
description: Customer's postal code
type: string
maxLength: 10
city:
name: city
in: formData
description: Customer's city
type: string
maxLength: 50
country:
name: country
in: formData
description: Country codes compatible with ISO, e.g. PL, DE, etc.
type: string
maxLength: 2
default: PL
phone:
name: phone
in: formData
description: 'Customer''s telephone in the following format: 481321132123'
type: string
maxLength: 12
language:
name: language
in: formData
description: 'One of following language codes according to ISO 639-1: bg, cs, de, en, es, fr, hr, hu, it, nl, pl, pt, se, sk, ro'
type: string
maxLength: 2
default: pl
method:
name: method
in: formData
description: Payment method ID. List of payment methods provided in the panel or available through API
type: integer
urlReturn:
name: urlReturn
in: formData
description: URL address to which customer will be redirected when transaction is complete
type: string
maxLength: 250
urlStatus:
name: urlStatus
in: formData
description: URL address to which transaction status will be send
type: string
maxLength: 250
timeLimit:
name: timeLimit
in: formData
description: Time limit for transaction process, 0 - no limit, max. 99 (in minutes)
type: integer
channel:
name: channel
description: ' 1 - card + ApplePay + GooglePay, 2 - transfer, 4 - traditional transfer, 8 - N/A, 16 - all 24/7 – makes available all payment methods, 32 - use pre-payment, 64 – only pay-by-link methods, 128 – instalment payment forms, 256 – wallets, 4096 - card, 8192 - blik, 16384 - all methods except blik
<p>To activate the specific channels, their values should be summed up.
<p>Example:
transfer and traditional transfer: channel=6'
type: integer
enum:
- 1
- 2
- 4
- 8
- 16
- 32
- 64
- 128
- 256
- 4096
- 8192
- 16384
waitForResult:
type: boolean
description: Parameter determines wheter a user should wait for result of the transaction in the transaction service and be redirected back to the shop upon receiving confirmation or be redirected back to the shop immediately after payment. <a href="#section/Use-cases"><b>Read more</b></a>
regulationAccept:
type: boolean
description: 'Acceptance of Przelewy24 regulations: <br/>false – display consent on p24 website (default),<br/>true – consent granted, do not display.<br/>In case the „true” parameter is sent, the consent – worded as follows – must be displayed on the Partner’s website: „I hereby state that I have read the [regulations](https://www.przelewy24.pl/regulamin) and [information obligation](https://www.przelewy24.pl/obowiazekinformacyjny) of ”Przelewy24”. <br/>Under words <i>regulations</i> and <i>information obligation</i> there must be hyperlinks redirecting to websites with these documents. The checkbox must not be ticked by default.'
default: false
shipping:
name: shipping
in: formData
description: Delivery cost
type: integer
transferLabel:
name: transferLabel
in: formData
description: Description forwarded to transfer's description (not in every payment methods). A parameter can contain values only in a range [a-z A-Z 0-9 ęółśążźćńĘÓŁŚĄŻŹĆŃ . / :- ]
type: string
maxLength: 20
mobileLib:
name: mobileLib
description: The parameter is necessary while using SDK libraries. The value passed in <b>mobileLib</b> parameter is always 1 and value passed in <b>sdkVersion</b> determines which version of library should be used.
type: integer
enum:
- 1
sdkVersion:
name: sdkVersion
in: formData
description: Version of mobile library. Determines if transaction is mobile.
type: string
maxLength: 10
sign:
name: sign
in: formData
type: string
maxLength: 100
description: <br>Checksum of parameters:<br> {<font color = "brown">"sessionId":</font>"str",<font color = "brown">"merchantId":</font>int,<font color = "brown">"amount":</font>int,<font color = "brown">"currency":</font>"str",<font color = "brown">"crc":</font>"str"} <br><br>calculated with the use of sha384<br><br> <b><font color = "#DB2053">IMPORTANT!:</font></b><br> in case json_encode function is used, the following attributes should be added <br> "JSON_UNESCAPED_UNICODE | JSON_UNESCAPED_SLASHES"
encoding:
name: encoding
in: formData
description: 'Coding system for characters sent: ISO-8859-2, UTF-8, Windows-1250'
type: string
maxLength: 15
methodRefId:
name: methodRefId
in: formData
description: Special parameter for some payment flows e.g. BLIK and Card one-click.
type: string
maxLength: 250
cardData:
type: object
allOf:
- $ref: '#/components/schemas/cardData'
cart:
description: cart
items:
$ref: '#/components/schemas/CartParameters'
additional:
type: object
description: Set of additional information about the transaction or the payer
allOf:
- $ref: '#/components/schemas/AdditionalProperties'
simpCountryCode:
type: string
maxLength: 2
description: Country code according to ISO 3166 to create an IBAN number. Currently, the only one supported is PL.
simpClientId:
type: string
maxLength: 8
description: Gives the possibility to assign an individual ID to the customer. After completing this parameter, the IBAN number in its last 8 digits, contains the specified ID (e.g. 59 1050 XXXX XXXX 1234 5678 for simpClientId = 12345678).
required:
- merchantId
- posId
- sessionId
- amount
- currency
- description
- email
- country
- language
- urlReturn
- ttl
- sign
- simpCountryCode
CartParameters:
description: Cart Parameters
type: object
required:
- sellerId
- sellerCategory
properties:
sellerId:
type: string
description: Shop ID on the part of Partner
sellerCategory:
type: string
description: Shop category
name:
type: string
description:
# --- truncated at 32 KB (35 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/przelewy24/refs/heads/main/openapi/przelewy24-additional-services-mass-payments-transactions-api-openapi.yml