QR (TRY)¶

Important

For the QR method, the amount received in callbacks should be considered and accepted as final. The amount sent in the original request is not final, as the credited amount may be adjusted.

Initial request¶

The request contains certain fields:¶

Field	Description
`merchant`	unique merchant identifier;
`order`	transaction number in the merchant system;
`amount`	transaction amount in the currency, separator character is a point “.”;
`currency`	transaction currency, must be TRY;
`first_name`	customer’s first name. Maximum length is 30 characters (Only Latin and Turkish letters are allowed);
`last_name`	customer’s last name (Only Latin and Turkish letters are allowed);
`user_id`	customer identifier in the merchant’s system (optional field);
`payment_url`	url address of the site in whose favor the payment is made.

The fields process_url, success_url, fail_url (where the client will be redirected after the payment will be redirected to after the payment is made) do not have to be passed. These data are automatically taken from merchant settings in your personal cabinet.

GET /payment/form

https://<provided url>
/payment/form

Example:

application/json

{
  "merchant": "M1VJDHSI6DYXS",
  "order": "0001",
  "amount": "16",
  "currency": "TRY",
  "first_name": "IVAN",
  "last_name": "IVANOV",
  "user_id": "492235",
  "payment_url": "https://test.com"
}

Customer redirection after making a payment¶

Warning

Direction of the buyer to success_url or fail_url is only informational and CAN NOT confirm the success or rejection of payment!

After making a payment, the customer is redirected to success_url or fail_url.

The response contains the fields:¶

Field	Description
`order_no`	transaction number in the merchant system (the same as in the `order` request);
`amount`	transaction amount in the currency, separator character is a point “.”;
`currency_code`	transaction currency (in which the invoice was formed);
`co_inv_id`	unique transaction number;
`co_inv_st`	transaction status in the payment system (Success or Canceled).

Example of the response in case of successful payment acceptance for processing:

application/json

{
  "order_no": "0001",
  "amount": "16",
  "currency_code": "TRY",
  "co_inv_id": "1111111",
  "co_inv_st": "success"
}

Example of the response in case of payment cancellation:

application/json

{
  "order_no": "0001",
  "amount": "16",
  "currency_code": "TRY",
  "co_inv_id": "1111111",
  "co_inv_st": "canceled"
}

Final Status (Callback)¶

The callback mechanism is used to notify the merchant that the transaction has received a final status (for example, from “Pending” to “Success”).

It is described in detail in the Callbacks section.