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. AGWS

Payment System Callback

The method is designed to notify the project system about the payment status.

Backoff Policy To increase the reliability of receiving a response, Backoff policies are applied when making requests:

  • ntervals between retry attempts: 500 milliseconds

  • Time jitter between retries: 0.5 seconds

  • Maximum interval between retries: 60 seconds

  • Total retry duration: 10 minutes

After completing the payment, the payment system sends a request to the partner project to notify the payment status. The request is made to the URL specified in the callback_url field during the payment process.

If an HTTP status other than 200 is received, the BackOff policies will be applied.

Sending the callback

POSThttps://merchant-website/result

Headers

Name
Value

Content-Type

application/json

X-Signature

Body

Name
Type
Description

agent*

String

Showcase code in Tarlan system

project*

String

Project Code assigned by Tarlan

service_code*

String

Service ID on the showcase side

external_id*

String

Payment ID on the showcase side

Response

Name
Type
Description

status_code

String

Transaction status code

status_message

String

Description of transaction status

username

String

User ID

amount

Float

Amount credited

datetime

String

Time of payment initiation in the storefront system. ISO 8601 Current Timestamp format

project

String

Project Code assigned by Tarlan

fail_reason

Object

-code

Int

Rejection Reason Code

-message

String

Description of the Operation Rejection Reason

service_code

String

Service ID on the showcase side

external_id

String

Payment ID on the showcase side

{
    "project": "Testing",
    "service_code": "70958",
    "external_id": "proident",
    "status_code": "4",
    "status_message": "Transaction was failed",
    "amount": 100.82,
    "datetime": "fugiat sed",
    "username": "enim culpa eiusmod laborum",
    "fail_reason": {
        "code": 6132012,
        "message": "nulla Ut eu dolore"
    }
}

Last updated 18 days ago

Field Containing the

Authorization hash
Failure Reason