AlliancePay
🇬🇧 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
  1. Dictionary

Instructions for reconciliation by registers

Використання даних з реєстрів для звірки успішних операції.

PreviousLimitsNextFields Description in Registers

Last updated 2 months ago

Stages of reconciliation

  • Based on the data obtained from the registers, you can collect data on the specified parameters from your system.

  • Search by key parameters (e.g., operationId or rrn) to find the relevant records. You can also use parameters from merchantComment for more flexible reconciliation.

  • Verify the statuses and dates of processing to confirm the correctness of the transaction data.

  • Document any discrepancies and contact support for resolution.

Work with merchantComment

A new merchantComment parameter has been added to the payment API, which will also be included in the registers.

This option can make it easier for you to identify the transaction later in reconciliations in the registers.

Requirements for the parameter merchantComment.

  • Type: string

  • Maximum length: 255 characters

  • Validation rules: [a-zA-Z0-9 ,.;:@#$%'-=+1,256$]

Example: "merchantComment": "1712822901491QtPAxAWOrrg,1258728c1,alb" where, 1712822901491QtPAxAWOrrg - operationId of the original operation, 1258728c1 - senderCustomerId, alb - any other value you need to simplify the identification of the operation in the register, , - separator.

You can pass the senderCustomerId and/or recipientCustomerId, operationId of the original transaction when making a refund, and other parameters necessary for your work to this parameter.

The data passed in the merchantComment parameter will be automatically exported to the daily registers.

This update is intended to provide more flexibility and convenience in working with the registers. If you have any questions or need additional information, please feel free to contact the relevant technical chats.

PURCHASE Requrest Step 1
A2C
C2A transaction Request - Step 1
REFUND