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
  • Backoff Policy
  • Sending callback to partner's project
  1. Acquiring
  2. Webhook of the payment system

Payment Status

The method is intended to notify the project system of the payment status.

Backoff Policy

BackOff policy is used to increase the guarantees of receiving a response when fulfilling 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.

Callback by payment system after each transaction

Upon completion of payment, the payment system makes a request to the partner project to transfer the payment status. The request is made to the address specified in the field "callback_url" when initiating the payment.

On receiving an http status other than 200, the transaction will be executed BackOff policy

Sending callback to partner's project

POST callback_url

Headers

Name
Type
Description

Authorization*

String

Bearer Auto-rotation hash (see Signature Creating)

Request Body

Name
Type
Description

created_at*

String

Date of transaction creation

transaction_id*

Integer

Transaction ID on the side of payment system

acquirer_code*

String

Bank ID

project_reference_id*

String

Transaction ID on the side of the project

project_сlient_id*

String

User ID on the side of the project

status_code*

String

Transaction Status

type_code*

String

Concealed payment card

amount*

Float

Transaction amount

description*

String

Description

finished_at*

String

Date of transaction completion

project_id*

Integer

Project ID

merchant_id*

Integer

Merchant ID

additional_data

Object

Optional fields

card_token

String

Card token in the payment system

masked_pan

String

Concealed payment card

bank_code

String

In case of an error in a transaction, the error code uploaded

bank_message

String

Error description

Last updated 5 months ago