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.
You can access the Sandbox Test Portal at https://sandbox-portal.tami.com.tr. When you log in to the test portal using a test user account, you can view the transactions performed by the merchant associated with that user. These transactions can also be cancelled or refunded. To obtain the test user credentials, please contact TeknikDestek@tami.com.tr.
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.
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.
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.
| 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. |
| 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. |
| bankAuthCode | String | Bank Confirmation Code |
| bankReferenceNumber | String | Retref number for the transaction |
| errorGroup | String | Shows the group of the relevant error. Businesses can manage their own rules using error codes and error groups. |
You can use the documentation here to calculate the securityHash field in service requests and incoming service responses.
You can access the list of error codees on this page.
You can access the list of test cards on this page.