Get GDPR clauses
GET/v1/payments/dataprocessing/notices
Retrieves GDPR clauses
Request
Header Parameters
The User-Agent request header contains a characteristic string that allows the network protocol peers to identify the application type, operating system, software vendor or software version of the requesting software user agent.
The Accept request HTTP header advertises which content types, expressed as MIME types, the client is able to understand. Can be set to */*.
Locale in which the response should be returned (one of pl-PL, en-GB or uk-UA). When given locale is not supported then clause will be returned in the en-GB locale.
Responses
- 200
- 400
- 401
- 404
- 500
- 503
Success
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
The title of GDPR clause
The full GDPR content
Locale in which the content is
[
{
"title": "mElements S.A. with its registered office in Warsaw, 00-850 at ul. Prosta 18 is the controller of your personal data.",
"content": "The personal data provided by the Buyer will be used by mElements S.A. to execute the payment transaction.<br> The agreement for the provision of the „Paynow\" Payment Integrator service constitutes the legal basis for the processing of personal data by mElements S.A.<br> Personal data may be made available to the following entities: <ul class=\"data-processing-list\" style=\"list-style-type:lower-alpha\"> <li>institutions authorised to process data under the supervision conducted over mElements S.A. among other by the Polish Financial Supervision Authority (KNF), the Office of Competition and Consumer Protection (UOKiK);</li> <li>entities entrusted by us with data processing when providing services for our benefit.</li></ul> Personal data will be stored for a period not longer than 5 years after the termination of the agreement by one of the parties (in the event of a court dispute). After the expiry of the above periods, mElements will anonymise personal data.<br> The Buyer has the right to access and rectify, transfer, delete, limit or object to the processing of his/her personal data. The Buyer also has the right to lodge a complaint with the supervisory body for the protection of personal data in the manner indicated on the website <a class=\"data-processing-link\" href=\"https://www.uodo.gov.pl\" target=\"_blank\">uodo.gov.pl</a> . Provision of data is voluntary, but necessary for the execution of payment, and failure to provide data may result in the rejection of the payment.<br> More information on the rules governing the processing of your personal data by mElements can be found in the <a class=\"data-processing-link\" href=\"https://static.paynow.pl/docs/privacy_policy_melements_en.pdf\" target=\"_blank\">Privacy Policy</a><br> The function of the Personal Data Protection Officer is performed by an employee of mElements S.A., who can be contacted at: <a class=\"data-processing-link\" href=\"mailto:iod@melements.pl\" target=\"_blank\">iod@melements.pl</a>",
"locale": "en-GB"
}
]
Bad request
- application/json
- Schema
- Example (from schema)
- Example
Schema
Array [
]
Error status code
errors
object[]
required
Error type
Possible values: [CONFLICT, FORBIDDEN, NOT_FOUND, RATE_LIMIT_REACHED, SYSTEM_TEMPORARILY_UNAVAILABLE, UNAUTHORIZED, VALIDATION_ERROR, VERIFICATION_FAILED, PAYMENT_METHOD_NOT_AVAILABLE, PAYMENT_AMOUNT_TOO_SMALL, PAYMENT_AMOUNT_TOO_LARGE, IDEMPOTENCY_KEY_MISSING, SIGNATURE_MISSING]
Error description
{
"statusCode": 0,
"errors": [
{
"errorType": "CONFLICT",
"message": "string"
}
]
}
{
"statusCode": 400,
"errors": [
{
"errorType": "VALIDATION_ERROR",
"message": "Missing field XXX"
},
{
"errorType": "VALIDATION_ERROR",
"message": "Invalid format of field YYY"
}
]
}
Unauthorized, invalid or missing credentials
- application/json
- Schema
- Example (from schema)
- Example
Schema
Array [
- UnauthorizedErrorDetails
]
Error status code
errors
object[]
required
oneOf
Error details
Error type
Possible values: [UNAUTHORIZED]
Error description
{
"statusCode": 0,
"errors": [
{}
]
}
{
"statusCode": 401,
"errors": [
{
"errorType": "UNAUTHORIZED",
"message": "Unauthorized, invalid or missing credentials"
}
]
}
Not found
- application/json
- Schema
- Example (from schema)
- Example
Schema
Array [
]
Error status code
errors
object[]
required
Error type
Possible values: [NOT_FOUND]
Error description
{
"statusCode": 0,
"errors": [
{
"errorType": "NOT_FOUND",
"message": "string"
}
]
}
{
"statusCode": 404,
"errors": [
{
"errorType": "NOT_FOUND",
"message": "Resource not found"
}
]
}
Internal server error
- application/json
- Schema
- Example (from schema)
- Example
Schema
Array [
]
Error status code
errors
object[]
required
Error type
Possible values: [INTERNAL_SERVER_ERROR]
Error description
{
"statusCode": 0,
"errors": [
{
"errorType": "INTERNAL_SERVER_ERROR",
"message": "string"
}
]
}
{
"statusCode": 500,
"errors": [
{
"errorType": "INTERNAL_SERVER_ERROR",
"message": "Internal server error"
}
]
}
Service is temporarily unavailable
- application/json
- Schema
- Example (from schema)
- Example
Schema
Array [
]
Error status code
errors
object[]
required
Error type
Possible values: [SYSTEM_TEMPORARILY_UNAVAILABLE]
Error description
{
"statusCode": 0,
"errors": [
{
"errorType": "SYSTEM_TEMPORARILY_UNAVAILABLE",
"message": "string"
}
]
}
{
"statusCode": 503,
"errors": [
{
"errorType": "SYSTEM_TEMPORARILY_UNAVAILABLE",
"message": "Service is temporarily unavailable"
}
]
}