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
  1. APM Checkout (Blik)
  2. Overview

Testing

For each Merchant account, the Merchant will be issued login credentials and URL for the Merchant Back Office on a TEST server. All necessary API documentation and connection information will be located there (or sent via email). The TEST server has the following features to assist in integration:

Good to know: All the methods shown below are to emulate test results

  • 777000 to 777999 – emulate success;

  • 000000 to 77699 – emulate fail/retry;

  • 778000 to 999999– emulate fail/retry.

Emulating different scenarios works only in Test/Sandbox environment. For Production/Live environment, real BLIK code must be used.

Usage Instructions

You can use the OTP provided above for testing purposes in your development and staging environments. These OTP will allow you to simulate various payment scenarios without processing real transactions.

By using these testing OTP, you can ensure that your BLIK integration works correctly before going live with real transactions.

PreviousProcess FlowNextErrors

Last updated 1 month ago