Point Inquiry General Description

This is the request type that queries the available points on the card.

Points cannot be redeemed on debit cards with Reward Group Maximum, Bonus, Axess and CardFinans. Accordingly, points redemption should not be shown for the debit cards indicated on your checkout page. Credit cards with these reward groups do not have such a restriction.

Test/Prod Envirenement API User Information

For Virtual POS transactions, merchants can use the merchant information given in the table below for the controls they want to perform in the test environment.

For Virtual POS transactions to be realized from the prod environment via Tami, the merchant number is obtained by making an application.

You can access the Sandbox test portal at https://sandbox-portal.tami.com.tr. When you log in to the test portal with the users provided below, the transactions made by the workplace connected to this user can be viewed. Transactions can be canceled/refunded.

User Phone Number	User Password	Sms / Email Otp	Workplace Number	Terminal Number	Secret Key
5346484700	147850	147852	77006950	84006953	0edad05a-7ea7-40f1-a80c-d600121ca51b
5346484709	147850	147852	77006951	84006954	c8581bb6-a4b2-4925-8c94-529fc651399e
5346484803	147850	147852	77006952	84006955	ff7d4895-0c32-4f48-86ab-fb9ecca9f3d7
5346484807	147850	147852	77006953	84006956	33124ff0-0b19-4cf9-b002-13a35eae865b
5346484800	147850	147852	77006954	84006957	7daf9631-e136-4164-9ddb-dd1c02df851d
5346484808	147850	147852	77006956	84006959	fe6f3fff-0434-4932-a27d-bb3dac9de49d

Hash Calculation

The request sent for many transaction types should include the PG-Auth-Token in the header information. The PG-Auth-Token consists of the values "MerchantNumber:TerminalNumber:Hash".

When calculating the hash here, the merchantNumber, terminalNumber, and secretKey information belonging to the merchant are hashed with sha256 and converted to a string.

public class SHA256Example {\n public static String sha256(Long merchantNumber, Long terminalNumber, String secretKey) {\n String text = merchantNumber.toString() + terminalNumber.toString() + secretKey;\n try {\n MessageDigest digest = MessageDigest.getInstance(\"SHA-256\");\n byte[] hash = digest.digest(text.getBytes(StandardCharsets.UTF_8));\n String sha256Hex = DatatypeConverter.printBase64Binary(hash);\n return sha256Hex;\n } catch (NoSuchAlgorithmException e) {\n e.printStackTrace();\n return null;\n }\n }\n}

TAMİ Test Portal Information

You can access the Tami test portal at https://sandbox-portal.tami.com.tr. From this address, you can view the portal screen with the users specified above.

For your production environment information you can become a member at https://portal.tami.com.tr or You can apply to the e-commerce support unit.

Point Inquiry API Information

In test environment, the "https://sandbox-paymentapi.tami.com.tr/vas/bonusQuery" URL will be used.

In production environment, the "https://paymentapi.tami.com.tr/vas/bonusQuery" URL will be used.

API Request Example

{\n \"ipAddress\" : \"1.1.111.111\",\n \"emailAddress\" : \"cem@cem.com\",\n \"cardNumber\" : \"4546711234567894\",\n \"expireMonth\" : 12,\n \"expireYear\" : 26,\n \"cvv\" : \"\",\n \"currencyCode\" : 949 ,\n \"amount\" : 10,\n \"securityHash\" : \"748dnskwo404040lel==\"\n}

Request Parameters and Descriptions

Field	Format	(O)ptional/(C)onditional/(M)andatory	Description
ipAddress	String	M	IP address of the recipient.
emailAddress	String	M	Email information of the member business
cardNumber	Number	M	Credit Card Number
expireMonth	Number	M	Expiry date and month information of the card to be inquired about.
expireYear	Number	M	Expiry date and year information of the card to be inquired about.
cvv	Number	O	Security code information of the card from which payment will be taken.
currencyCode	Number	M	Currency Type
amount	Number	M	Amount
securityHash	String	M	It is the value expected to be calculated and transmitted according to the fields specified in the document. If it is missing or incorrect, the transaction is not routed to the bank, an error is given.

API Response Example

{\n \"approved\": true,\n \"orderId\": \"SISTC7BA89DA0BE1476F81AD3A476EF10C80\",\n \"returnCode\": \"00\",\n \"errorMessage\": \"\",\n \"retRefNum\": \"401609748852\",\n \"provisionDate\": \"20240116 17:05:15\",\n \"rewardList\": [\n {\n \"type\": \"CARD\",\n \"amount\": 0.022,\n \"name\": \"BNS\"\n }\n ],\n \"securityHash\": \"74hsjw84746eekro747463ye==\"\n}

Response Parameters and Descriptions

Field	Format	Description
approved	String	Field indicating Transaction Approval status
orderId	String	order number
returnCode	Number	error code
errorMessage	Number	error message
retRefNum	Number	Referance Number
provisionDate	DateTime	Provision Date
type	Char	Card Type
amount	Number	Amount of Points Used
name	Char	Available Point Type
securityHash	String	The value to be used to determine that the result of the operation came from the correct source. The documentation specifies how it should be calculated.

Security Hash Calculation

You can use the documentation here to calculate the securityHash field in service requests and incoming service responses.

Error Codes

You can access the list of error codees on this page.

Test Cards

You can access the list of test cards on this page.

Closure >> Pre Authorization Closure Inquiry >> BIN Inquiry

Multi Bank Virtual POS