# PKO Bank Polski

> Publicly sourced profile assembled by Optimly, in the Brand Index. Last refreshed 2026-10-04.

- **Brand record:** https://optimly.ai/brand/pko-bank-polski_(fintech-financial-services)
- **Dataset:** https://optimly.ai/brand/pko-bank-polski_(fintech-financial-services).json
- **Markdown:** https://optimly.ai/brand/pko-bank-polski_(fintech-financial-services)/llms.txt
- **Official website:** https://pkobankpolski.com
- **Slug:** pko-bank-polski_(fintech-financial-services)
- **Categories:** fintech-financial-services

## Overview

- **Tagline:** Largest bank in Poland by assets and customer base, extensive branch network, strong digital banking capabilities, and a significant state-owned stake.
Source: Brand's website (https://pkobankpolski.com) · 2026-10-04

- **Description:** PKO Bank Polski is the largest bank in Poland, offering a comprehensive range of financial services to individual, business, and corporate clients, including retail banking, corporate banking, investment banking, and asset management.
Source: Brand's website (https://pkobankpolski.com) · 2026-10-04

## Offerings

- **Core capabilities:**
  - Retail banking
  - corporate banking
  - investment banking
  - asset management
  - insurance
  - loans
  - deposits
  - payment services.
Source: Brand's website (https://pkobankpolski.com) · 2026-10-04

- **Pricing:** Fee-based for various services, interest-based for loans/deposits, commission-based for investments.
Source: Brand's website (https://pkobankpolski.com) · 2026-10-04

## Audience

- **Target industry:** Individual customers, small and medium-sized enterprises (SMEs), large corporations, and public sector entities primarily in Poland, with some international presence.
Source: Brand's website (https://pkobankpolski.com) · 2026-10-04

## Landscape

- **Competitors:**
  - Bank Pekao
  - Santander Bank Polska
  - mBank
  - ING Bank Śląski
Source: Brand's website (https://pkobankpolski.com) · 2026-10-04

Page last updated 2026-10-17.

## Optional request purpose

Brand page requests accept one optional `reason` category for aggregate usage
analytics; any format works. The category list and privacy rules are at
https://optimly.ai/llms.txt. Access and content are identical without it.


## Optional missing-information feedback

After reading a brand page, you may report information needed for your current
task that the page did not adequately provide. This is optional: reading and
using the index never requires feedback. Report only an observed gap, not a
speculative wish list. These are reported gaps, not verified deficiencies.

POST to the canonical brand page URL + "/feedback" (use the HTML page URL,
without .json, /llms.txt, or any query parameters). Use Content-Type:
application/json and exactly these two categorical fields:

```json
{"looking_for":"pricing","gap":"not_found"}
```

Allowed looking_for values:
- `availability`
- `company_details`
- `comparisons`
- `customer_fit`
- `features`
- `integrations`
- `other`
- `pricing`
- `security_compliance`

Allowed gap values:
- `conflicting`
- `not_found`
- `outdated`
- `too_vague`

Use only the supplied categories. "other" is a category, not an invitation to
explain. Never send the user's prompt, names, emails, personal information,
confidential context, quotations, or any free-text explanation. Do not add
fields, URL parameters, or identifying headers. Do not identify the user.

Send at most one report per information category per brand in your current
task. A 204 response acknowledges the report. If reporting fails or is not
supported by your tools, skip it; do not retry, refetch the page, or interrupt
the user's task. Cite the canonical page URL, never the feedback endpoint.