AlliancePay
🇬🇧 English
🇺🇦 Українська🇬🇧 English
🇬🇧 English
🇺🇦 Українська🇬🇧 English
  • E Commerce platform AlliancePay v2.32.0
  • Authentication
  • Data Encryption
  • Authorization
  • Using an authorization token
  • Key Management Overview
    • PURCHASE Collection Example
    • A2C Collection Example
  • Payment methods H2H
    • PURCHASE
      • PURCHASE Request - Step 1
      • PURCHASE Request - Step 2
    • A2C
    • C2A
      • C2A Transaction Request - Step 1
      • C2A Transaction Request - Step 2
    • ApplePay decrypted
      • PURCHASE
        • Payment Processing Request - Step 1
        • Payment Processing Request - Step 2 (3DS)
      • C2A
        • C2A request Step 1
        • C2A request Step 2 (3DS)
    • ApplePay encrypted
      • Request aPay support on the page
      • Request to receive aPay merchant data
      • Merchant validation request
      • Session Establishment Request in aPay
      • Payment Processing Request
    • GooglePay™ decrypted
      • PURCHASE
        • Payment Processing Request - Step 1
        • Payment Processing Request - Step 2 (3DS)
      • C2A
        • C2A request Step 1
        • C2A request Step 2 (3DS)
    • GooglePay™ encrypted
      • Google Pay™ Documentation
      • Google Pay™ Support Request on the Page
      • Google Pay™ Merchant Data Retrieval Request
      • Payment request
    • REFUND
    • TOKEN
      • PURCHASE
        • Token payment request Step 1
        • 3DS token payment request Step 2
      • C2A
        • Token payment request Step 1
        • 3DS token payment request Step 2
      • Token Creation
      • Retrieve Token by CustomerId
      • Retrieve Token Data
      • Update Token Status
      • Token Statuses
    • Account Verification
      • Card Verification Request Step 1
      • Card verification request Step 2
    • Getting data
      • By OPERATION_ID
      • By merchantRequestId
    • Getting a balance
    • Callback
  • Payment methods HPP
    • PURCHASE
      • Creating an order
      • Receiving order data
    • REFUND
    • Callback
    • Order statuses
  • Dictionary
    • Transaction status
    • Test cases
    • Error codes
    • Value actionCode, responseCode
    • Limits
    • Instructions for reconciliation by registers
      • Fields Description in Registers
    • Whitelist IP addresses and URLs
  • History of changes
Powered by GitBook
On this page
  • Callback Submission
  • IP Address Requirements
  • URL Address Requirements
  1. Dictionary

Whitelist IP addresses and URLs

Using WhiteListing

PreviousFields Description in RegistersNextHistory of changes

Last updated 1 month ago

To ensure security and enable interaction with API requests, you must provide a list of IP addresses and URLs to be added to the WhiteList.

Callback Submission

  • A URL address will be used for sending callbacks related to operations.

  • When creating requests, the notificationUrl parameter must contain the URL to which the will be sent.

  • The URL address can be dynamic.

IP Address Requirements

  • The IP address must follow the IPv4 protocol.

  • The provided IP address format must be '192.168.1.1'.

URL Address Requirements

  • Must support HTTPS (e.g., https://docs.merchant.alb.ua/).

  • The server must be available 24/7 to receive notifications.

  • Must correctly process requests in JSON format.

Callback