Tarlanpayments
Eng
Eng
  • Acquiring
    • General information
      • Structure of payment processing
      • Kinds of operations
      • 3D-Secure
      • PCI DSS
    • Types of transactions
    • Structure of system responses
    • Error code
    • Transaction statuses
    • Signature Creation
    • Additional parameters
    • Interaction with the payment method
      • Initiating funds receipts
      • Initiating pay out
      • Card link
      • Initiating funds using Apple Pay
      • Initiating funds using Google Pay
      • Iframe
    • Payments without form of payment
      • One click
    • Smart Pay
      • Google pay
    • Supplementary methods
      • Removal of a linked user card
      • Verification of transaction status
      • Receiving a list of cards
      • Refund
      • Upper fee calculation
    • Webhook of the payment system
      • Payment Status
      • Payment ready to be made
    • Tilda Publishing
    • Edit summary
  • AGWS
    • Account Status Codes Guide
    • Error Codes
    • Reason for operation rejection
    • Transaction Lifetime
    • Transaction Status Guide
    • Creating a Signature
    • Check account status
    • Make a payment
    • Checking the refill status
    • Checking the remaining balance on the account
    • Confirmation of funds debit
    • Creating a payment link
    • Showcase Flow
    • Service Provider Flow
    • Payment System Callback
    • Payment Processing Scheme
  • Receiving a fiscal receipt
  • Calculation of the upper commission
Powered by GitBook
On this page
  1. Acquiring
  2. Webhook of the payment system

Payment ready to be made

The method is designed to confirm payment of an order on the project side.

The system sends a request to "confirm_url" of the project and awaits for a response with requisite parameters: id, status, message, is_payble.

The method will be processed if the value parameter "confirm_url" is uploaded when initiating a payment.

Backoff Policy

To increase the guarantees of receiving a response, BackOff policy is used when fulfiling requests:

  • InitialInterval = 500 * time.Millisecond, intervals between repeated requests

  • RandomizationFactor = 0.5, Spread of the request on time between retries

  • MaxInterval = 60 * time.Second, Maximum time between retries

  • MaxElapsedTime = 10 * time.Minute, the time during which the attempts will be made.

GET https://merchant-website/confirm

Query Parameters

Name
Type
Description

type*

string

Type of transaction

project_reference_id*

string

Order number on the project side

Headers

Name
Type
Description

Authorization

String

Bearer Auto-rotation hash (see Signature Creating)

{
    "id": "121abc", // Идентификатор транзакции на стороне проекта 
    "status": "success", // Статус заказа на стороне проекта
    "message": "order desciption", // Текстовое сопровождение ответа
    "is_payble" : true // Разрешение на проведение платежа
}

The system decides whether to effect a payment depending on the value parameter "is_payble":

  • true - The project authorizes the payment

  • false – The project declines the payment

Last updated 5 months ago