Documentation
  • Welcome!
  • Card (server to server)
    • Overview
      • Authentication
      • Process Flow
      • API Endpoints
      • Testing
    • API Commands
      • 700 – Start Credit Card charge (3DS Enabled)
      • 701 – Request Capture Authorization
      • 702 – Request Cancel Authorization
      • 708 – Check transaction details
      • 709 – Check transaction status
      • 720 – Credit Request
      • 756 – Manual Rebill Request
      • 760 – Request Refund
    • Notifications
      • Notifications
      • 850 – Transaction state Notification
      • 860 – Refund Notification
      • 880 – Dispute Notification
    • Transaction Status Codes
    • 3D Secure Integration
  • APM Checkout (Blik)
    • Overview
      • Process Flow
      • Testing
    • Errors
      • Error object
      • Errors type list
      • Decline errors code list
    • Create a checkout session
    • Retrieve a Checkout Session
    • Webhoook Event Notification
    • Pay a Checkout Session
  • Refund a Checkout Session
  • Retrieve checkout session refund
  • Wallet API
    • Introduction
      • Authentication
      • Metadata
    • Errors
      • Error object
      • Errors type list
      • Decline errors code list
    • Payout
      • Create a payout
      • Retrieve a payout
  • Wallet payment page
    • Payment Page
Powered by GitBook
On this page
  • How It Works
  • Process Flow
  • Testing
  • Errors
  • Create a Checkout Session
  • Retrieve a Checkout Session
  • Webhook Event Notification
  • Pay a Checkout Session
  1. APM Checkout (Blik)

Overview

The APM Checkout (BLIK) integration allows customers to complete transactions using the BLIK payment method. This integration supports server-to-server (S2S) payments for Alternative Payment Methods (APMs) that involve a redirect flow. In this process, transaction details are securely exchanged between servers, and customers are redirected to a BLIK payment page to finalize the transaction, ensuring secure and efficient payment handling.

How It Works

When customers select BLIK at checkout, the merchant creates a session with Converge Gate, providing necessary transaction details and customer information. Converge Gate generates a session ID and a redirect URL, which the customer uses to proceed with the payment.

  1. Customer Pays with APM:

  • The customer initiates the payment by selecting APM (BLIK) as their payment method during the checkout process.

  1. Merchant Creates a Session:

  • The merchant sends the transaction details and customer information to Converge Gate to create a checkout session.

  1. Returns ID and Redirect URL:

  • Converge Gate processes the session creation request and returns a unique session ID along with a redirect URL.

  1. Redirects to URL:

  • The customer is redirected to the provided URL (managed by APM) to proceed with the payment.

  1. Receives Result from Bank via APM:

  • The APM communicates with the bank to process the transaction and receives the result, indicating whether the payment was successful or not.

  1. Returns to the success_url:

  • Based on the transaction result, the customer is redirected back to the merchant's success URL if the payment was successful.

  1. Retrieves Session ID & Updates Status:

  • The merchant retrieves the session ID from Converge Gate to check the transaction status and updates their records accordingly.

Process Flow

Testing

Errors

Create a Checkout Session

Retrieve a Checkout Session

Webhook Event Notification

Pay a Checkout Session

Previous3D Secure IntegrationNextProcess Flow

Last updated 2 months ago

Process Flow
Testing
Errors
Create a checkout session
Retrieve a Checkout Session
Webhoook Event Notification
Pay a Checkout Session