• Tami E-commerce Solutions Tami E-commerce Solutions

    Tami E-commerce Solutions

    Let your business grow comfortably with our e-commerce solutions

Grow your business easily with our payment solutions

Choose the model that best suits you from our solutions and easily step into the world of E-commerce.

  • Take advantage of campaigns and installments in all banks

  • Gain ease of financial management

  • Easily get payments via website, social media and other channels

Take advantage of campaigns and installments in all banks

Gain ease of financial management

Easily get payments via website, social media and other channels

E-commerce Payment System Solutions

Multibank vPOS

Tami multi-bank virtual POS is a secure payment solution created to get payments with all credit and debit cards in online sales.

Multibank vPOS
Card Storage

With Masterpass, which is integrated into the Tami Hosted Payment Page, cardholders' credit, debit and prepaid cards are recorded, allowing them to shop more easily and quickly without re-entering their information in their next transactions on Tami merchants.

Card Storage
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.

Pay by Link
Open Source Plug-ins

Tami merchants that create their e-commerce sites on WooCommerce, OpenCart, PrestaShop, MagentoCommerce infrastructures can start getting payments instantly with the free of charge payment plugins provided by Tami.

Open Source Plug-ins
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.

Hosted Payment Page
Marketplace Solution

It is a payment and money distribution solution that Tami offers to merchants that want to become a marketplace. It includes services that automate sub-sellers' commission amounts and money transfers. Merchants with Tami's marketplace payment solution access financial reporting showing all money flows from a single screen, monitor the sales of sub-sellers and manage their sales effectively.

Marketplace Solution

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