Przelewy24 · Schema
TransactionObject
PaymentsPayment GatewayBank TransferBLIKCard PaymentsE-CommercePolandPolishMulti-CurrencyFintech
Properties
| Name | Type | Description |
|---|---|---|
| settledAmount | integer | Amount without commision |
| ordrId | integer | Unique id of transaction |
| sessionId | string | Id of transaction used by merchant |
| status | integer | Status of transaction: 0 – not paid, 1 – paid, 2 – paid and verified, 3 – payment returned |
| date | string | Creation date of transaction. Format: “YYYY-MM-DD HH:MM:SS” |
| dateOfTransaction | string | Transaction registration date |
| dateOfVerification | string | Date of verification |
| clientEmail | string | Client's email |
| accountChecksum | string | Customer’s hashed bank account number |
| paymentMethod | integer | Payment method ID |
| description | string | Transaction description |
| clientName | string | Customer’s first name and surname |
| clientAddress | string | Customer's address |
| clientCity | string | Customer's city |
| clientZip | string | Customer's zip code |
| statement | string | Batch number in which the transaction was paid |
| fee | integer |
JSON Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "TransactionObject",
"properties": {
"settledAmount": {
"type": "integer",
"description": "Amount without commision"
},
"ordrId": {
"type": "integer",
"description": "Unique id of transaction"
},
"sessionId": {
"type": "string",
"description": "Id of transaction used by merchant"
},
"status": {
"type": "integer",
"description": "Status of transaction: 0 \u2013 not paid, 1 \u2013 paid, 2 \u2013 paid and verified, 3 \u2013 payment returned"
},
"date": {
"type": "string",
"description": "Creation date of transaction. Format: \u201cYYYY-MM-DD HH:MM:SS\u201d"
},
"dateOfTransaction": {
"type": "string",
"description": "Transaction registration date"
},
"dateOfVerification": {
"type": "string",
"description": "Date of verification"
},
"clientEmail": {
"type": "string",
"description": "Client's email"
},
"accountChecksum": {
"type": "string",
"description": "Customer\u2019s hashed bank account number"
},
"paymentMethod": {
"type": "integer",
"description": "Payment method ID"
},
"description": {
"type": "string",
"description": "Transaction description"
},
"clientName": {
"type": "string",
"description": "Customer\u2019s first name and surname"
},
"clientAddress": {
"type": "string",
"description": "Customer's address"
},
"clientCity": {
"type": "string",
"description": "Customer's city"
},
"clientZip": {
"type": "string",
"description": "Customer's zip code"
},
"statement": {
"type": "string",
"description": "Batch number in which the transaction was paid"
},
"fee": {
"type": "integer",
"descirption": "Commision"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/TransactionObject"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.