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

Confirmation of funds debit

Last updated 2 months ago

ATTENTION: New Error Response Format In the near future, errors in our system will be classified as expected and unexpected. Depending on the type of error, the format of the JSON response will be changed. Please review the new formats on the page. This change will be applied to all APIs in the AGWS system except '''.

Click to view the old and new JSON error responses. Please take note of this update and ensure your system is ready for these changes, if necessary.

POST

Headers

Name
Value

Content-Type

application/json

X-Signature

Body

Name
Type
Description

agent*

String

Showcase code in the Tarlanpayments system

confirm_code

String

Payment confirmation code

external_id*

String

Payment ID on the showcase side

Response

Name
Type
Description

status

bool

Request processing status

status_code

uint

Error code

message

string

Description of error

result

Object

An object storing payment information

-is_success

String

Payment success flag

-transaction_status_id

String

-external_id

String

Payment ID on the showcase side

-otp_status

bool

otp check success flag

{
    "status": true,
    "status_code": 0,
    "message": "Success",
    "result": {
        "is_success": true,
        "transaction_status_id": "1",
        "external_id": "200001",
        "message": "",
        "otp_status": true
    }
}

Examples of error responses before the changes

{
    "status": false,
    "status_code": 1041,
    "message": "Order not found",
    "result": {}
}
{
    "status": false,
    "status_code": 1014,
    "message": "Invalid signature",
    "result": {}
}

Examples of error responses after the changes

{
    "status": true,
    "status_code": 0,
    "message": "Success",
    "result": {
        "error_code": 1041,
        "message": "Order not found",
        "data": null,
        "additional_data": null
    }
}
{
    "status": false,
    "status_code": 1014,
    "message": "Invalid signature",
    "result": {}
}
curl --location 'https://agwsapi.tarlanpayments.kz/showcase-gateway/api/v1/action/confirm/invoice' \
--header 'Content-Type: application/json' \
--header 'X-Signature: your_signature_here' \
--data '{
    "agent": "test_agent",
    "confirm_code": "104000",
    "external_id": "externa312"
}'

Error Codes
Make a payment
https://agwsapi.tarlanpayments.kz/showcase-gateway/api/v1/action/confirm/invoice
here
Authorization hash
Transaction status