Skip to content

Payment methods · Redirects

Accept BLIK payments from Polish customers through Neogated

Customers are redirected to Neogated and approve the payment in their mobile banking app. Offer BLIK on the Hosted Payment Page, through Embedded Fields or with the Direct API.

PLN and PURCHASE only. Requests in other currencies are rejected, and refund, capture and void are not supported.

1 Your checkout Customer selects BLIK
2 Altitude Pay Initiates the payment with Neogated
3 Neogated and the bank app Customer approves in the mobile banking app
4 Your return URL Customer returns · verify the final status
Altitude Pay Your systems Third-party provider

BLIK Payment Method

BLIK is a Polish instant payment system that enables customers to make payments using their mobile banking app. Through Neogated integration, merchants can offer BLIK as a payment option to Polish customers.

Customers are redirected to complete their payment via their bank's mobile app. There are multiple ways to initiate this redirect:


Hosted Payment Page (HPP)

In this flow, the Payments Platform presents BLIK as an available payment method. Once selected, the customer is redirected to Neogated to complete the transaction by approving it in their mobile banking app.

Flow Diagram

sequenceDiagram
    participant Customer
    participant Merchant Frontend
    participant Payments Platform
    participant Neogated
    participant Bank App

    Customer->>Merchant Frontend: Start checkout
    Merchant Frontend->>Payments Platform: Create HPP session
    Payments Platform-->>Merchant Frontend: Session link
    Merchant Frontend->>Customer: Redirect to HPP
    Customer->>Payments Platform: View HPP and select BLIK
    Payments Platform->>Neogated: Initiate BLIK payment
    Neogated-->>Payments Platform: Redirect URL
    Customer->>Neogated: Access checkout page
    Neogated->>Bank App: Push notification
    Customer->>Bank App: Approve payment
    Bank App->>Neogated: Confirmation
    Neogated->>Payments Platform: Callback (COMPLETED/FAILED)
    Payments Platform->>Merchant Frontend: Notify result

Embedded Fields (EF)

In this flow, the merchant embeds a BLIK payment button directly into their checkout page using a JavaScript integration. The Payments Platform loads the Neogated script which renders the BLIK payment option. Once clicked, the customer is redirected to Neogated to complete the payment.

Flow Diagram

sequenceDiagram
    participant Customer
    participant Merchant Frontend
    participant Payments Platform
    participant Neogated
    participant Bank App

    Customer->>Merchant Frontend: Start checkout
    Merchant Frontend->>Payments Platform: Load Embedded Fields session
    Payments Platform-->>Merchant Frontend: Session with neogated.js
    Merchant Frontend->>Customer: Show BLIK payment button
    Customer->>Merchant Frontend: Click BLIK
    Merchant Frontend->>Payments Platform: Submit payment (neogated-blik)
    Payments Platform->>Neogated: POST /api/v1/deposit
    Neogated-->>Payments Platform: Redirect URL
    Payments Platform-->>Merchant Frontend: Redirect URL
    Merchant Frontend->>Customer: Redirect to Neogated
    Customer->>Neogated: Access BLIK checkout
    Neogated->>Bank App: Push notification
    Customer->>Bank App: Approve in mobile app
    Bank App->>Neogated: Confirmation
    Neogated->>Payments Platform: Callback (status)
    Payments Platform->>Merchant Frontend: Notify result

Direct API Integration

In the direct API flow, BLIK is already selected on your platform. The customer is immediately redirected to Neogated to complete the payment without an intermediate selection screen.

This method provides more control over the user experience.

Flow Diagram

sequenceDiagram
    participant Customer
    participant Merchant Frontend
    participant Payments Platform
    participant Neogated
    participant Bank App

    Customer->>Merchant Frontend: Start checkout (BLIK selected)
    Merchant Frontend->>Payments Platform: Create payment with neogated-blik
    Payments Platform->>Neogated: POST /api/v1/deposit
    Neogated-->>Payments Platform: Redirect URL + Transaction ID
    Payments Platform-->>Merchant Frontend: Redirect URL
    Merchant Frontend->>Customer: Redirect to Neogated
    Customer->>Neogated: Access BLIK checkout
    Neogated->>Bank App: Push notification
    Customer->>Bank App: Approve in mobile app
    Bank App->>Neogated: Confirmation
    Neogated->>Payments Platform: Callback (status)
    Payments Platform->>Merchant Frontend: Notify result

Supported Transactions

Transaction Type Supported Description
PURCHASE Yes One-time purchase with redirect to BLIK authentication
REFUND No Not supported
CAPTURE No Not applicable (purchase-only flow)
VOID No Not supported

Supported Currency

Currency Code Description
Polish Zloty PLN Only PLN is supported for BLIK payments

Note: BLIK only supports PLN currency. Requests with other currencies will be rejected.


Transaction Statuses

Neogated sends callback notifications with the following statuses:

Callback Status Internal Status Description Final State
COMPLETED APPROVED Payment successfully completed Yes
FAILED DECLINED Payment failed Yes
REJECTED DECLINED Payment rejected by bank or customer Yes
CANCELED DECLINED Payment canceled by customer Yes
PROCESSING PENDING Payment is being processed No

Redirect Handling

After the customer completes (or abandons) the BLIK payment on Neogated's checkout page, they are redirected back to the Payments Platform. The platform then checks the transaction status and redirects the customer to the appropriate merchant URL:

Transaction Status Redirect Destination
APPROVED Merchant's return_url
DECLINED / CANCELED Merchant's return_url
PENDING Waits for callback resolution, then redirects to return_url

Note: If the transaction is still PENDING when the customer is redirected back, the platform will wait briefly for the callback to arrive before redirecting the customer to the return_url. The merchant should verify the final transaction status via the Transaction Status API regardless of the redirect outcome.


Flow Comparison

Feature Hosted Payment Page Embedded Fields Direct API Integration
Who shows payment methods? Payments Platform Payments Platform (via JS) Merchant platform
Payment method selection step? Yes Yes (embedded in merchant page) No (selected beforehand)
Redirect to Neogated After selection After selection Immediately after initiation
Flexibility in UX Moderate (managed selection screen) High (embedded in merchant checkout) High (fully controlled UX)
Integration effort Lower Moderate Higher