• API MARKET

    Find everything you need for Tami Virtual POS integration in API Market

    Find API

E-commerce Solutions

  • Multi Bank Virtual POS
    Multi Bank Virtual POS
  • Card Storage
    Card Storage
  • Pay by Link
    Pay by Link
  • Open Source Plug-ins
    Open Source Plug-ins
  • Hosted Payment Page
    Hosted Payment Page
  • Marketplace Solution
    Marketplace Solution
Multi Bank Virtual POS
Multi Bank Virtual POS
Card Storage
Card Storage
Pay by Link
Pay by Link
Open Source Plug-ins
Open Source Plug-ins
Hosted Payment Page
Hosted Payment Page
Marketplace Solution
Marketplace Solution
Discover

Find the API that You Need

  • Sales

    It includes APIs required for all your sales transactions. You can find your sales transactions such as “Advance Sales”, “Installation Sales”, “Award Inquiry” and “Pre-Authorization”.

    See API's
  • Inquiry

    This is the service where Tami member merchants can query the first 6 or 8 digits of the card information and learn the information of the card.

    See API's
  • Reverse / Refund

    The payment made through TAMI can be canceled on the same day (before the end of the day). In order to cancel, the order number (orderId) of the payment must be sent. Sending the amount and reason is not mandatory. If the cancellation is successful, the canceled amount will be returned from the service.

    See API's
  • Closure

    In the pre-authorized transaction performed through Tami, the limit up to the provision amount is blocked on the card. With the closing process, this amount is collected from the card.

    See API's
  • Security Hash

    A security hash is required for all transaction types related to Virtual POS integration. This documentation explains how to create and use a security hash.

    See API's
  • Hosted Payment Page

    It is a secure payment solution offered to Tami merchants that cannot host the payment page in their own infrastructure or do not want to bear the cost of an SSL certificate. Integrated into the common payment page, Tami merchants can get payments securely with credit and debit cards, while also increasing their sales conversion rate with one-click payment methods such as Masterpass.

    See API's
  • Pay by Link

    It is a virtual POS solution to get payments without any integration. Tami merchants can create payment links for the products they sell and share them on all digital platforms to get payments with all credit cards.

    See API's
Easy to Integrate, Easy to Develop.
  • Technical Documents and Guidelines
  • Integration via API Rest
  • Sandbox
  • Error Codes
  • Frequently Asked Questions

Frequently Asked Questions

Which fields should I pass in the header when sending requests to services?
Key Value
correlationId Correlation{{randomNumber}}
PG-Auth-Token {{merchantNumber}}:{{terminalNumber}}:{{hash}}
PG-Api-Version V2

In the header section, correlationId and PG-Auth-Token parameters are expected to be transmitted. correlationId must be transmitted as a string unique value for each transaction. PG-Auth-Token parameter consists of merchantNumber, terminalNumber and hash information of the merchant as stated in the table. For hash information, merchantNumber, terminalNumber and secretKey information of the merchant is obtained by hashing with sha256 and converting it to string.

Response

{
    "errorCode": 4015,
    "errorMessage": " The Security Hash field must be transmitted. Check and try again",
    "success": false,
    "systemTime": "2024-03-30T12:08:40.526596076",
    "correlationId": "correlation9975",
    "SecurityHash": "qSHq2JE7cmxqYx+2x4FSBaR6q2fqRhUFlA9uVmuinL4="
}

The error received is the error received when the SecurityHash value expected to be sent in the request is not sent. In the request, the "securityHash" parameter is expected to be calculated and transmitted according to the desired values. We recommend that you check these fields and try the operation again and If the error continues, we kindly ask you to send us the fields that make up the SecurityHash value and the hash value you created.

Response

    "errorCode": 4003,
    "errorMessage": " Inconsistent hash value sent in header",
    "success": false,
    "systemTime": "2024-03-30T12:08:40.526596076",
    "correlationId": "correlation9975",
    "SecurityHash": "qSHq2JE7cmxqYx+2x4FSBaR6q2fqRhUFlA9uVmuinL4="
}

"PG-Auth-Token" parameter should be passed in the header in all sales, cancellation/refund, pre-authorization, pre-authorization closure, 3D sales and 3D sales completion requests.

This information consists of "merchantNumber:TerminalNumber:Hash" information of the merchant. The hash information is expected to be calculated according to the requested values and added to the PG-Auth-Token parameter.

Read More

We are here for all your questions and support requests.

Ask a Question Ask a Question
Protection of Personal Data Cookie Policy