-
Multi Bank Virtual POS
Multi Bank Virtual POS
Pre-Authorization Capture Transaction General Description
The pre-authorization capture transaction allows you to collect the amount you previously blocked on a card via a pre-authorization transaction. For this transaction, you need to send the order number (orderId) of the blocked payment, encrypted in the required manner. If the amount (amount) is not sent, the full blocked amount is collected.
Tami Test/Prod Portal Information
Before going live with your integration, you can use the Tami Test Portal to test without creating any real money movement.
Test Portal address: https://sandbox-portal.tami.com.tr
If you would like to log in to the test portal to view your transactions and perform cancellations/refunds when needed, a dedicated test portal user must be defined for you. You can reach our support team for this at TeknikDestek@tami.com.tr.
Prod Portal address: https://portal.tami.com.tr
For your production environment credentials, you can register via this address or contact our ecommerce support team.
Tami Test / Prod API Users
Two different environments are used when integrating with Tami’s APIs: Sandbox (Test) and Prod (Production).
- Test (Sandbox) Environment
This lets you test your integration without creating any real money movement. Your requests are sent to the test endpoints and can be tracked via the Tami Test Portal above.
Below are the credentials you can use to send a test request via the API in the sandbox environment:
| Field | Value |
|---|---|
| Merchant Number | 77006950 |
| Terminal Number | 84006953 |
| Secret Key | 0edad05a-7ea7-40f1-a80c-d600121ca51b |
- Prod (Production) Environment
This is the environment where live transactions take place and real payments are collected.
For your production environment credentials, you can register via https://portal.tami.com.tr or contact our e-commerce support team.
Generating the PG Auth Token
For requests sent to Virtual POS services, the PG-Auth-Token field must be included in the header.
The PG-Auth-Token is generated in the following format:
MerchantNumber:TerminalNumber:Hash
The Hash value is generated by concatenating your Merchant Number, Terminal Number, and Secret Key (in that order), hashing the result with the SHA-256 algorithm, and converting the result to Base64 format.
Below is a sample Java code block demonstrating this calculation:
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}\n
You can generate the PG-Auth-Token header value by combining the Hash value you generated with your Merchant Number and Terminal Number in the format above.
Pre-Authorization Capture Transaction API Information
The endpoint information to be used for the pre-authorization capture transaction is below:
| Environment | Endpoint |
|---|---|
| Test (Sandbox) | https://sandbox-paymentapi.tami.com.tr/api/v0/payment/post-auth |
| Production (Prod) | https://paymentapi.tami.com.tr/api/v0/payment/post-auth |
You must send your requests using the POST method to the endpoint appropriate for the environment you are working in (test/production).
How the Pre-Authorization Capture Request Is Sent
For pre-authorization capture transactions, the values in the body of the request sent are not expected to be transmitted in plain form; instead, a single signed and encrypted value is expected. This value is sent in the signedRequest field.
The response returned by Tami is likewise signed and encrypted, and is delivered in the signedResponse field. Detailed information on how to decode the signedResponse value is provided in the headings below.
In addition, the following information must also be sent in the header:
- PG-Auth-Token: How this is calculated is explained above under “Generating the PG Auth Token.”
- CorrelationId: A variable value that must be unique for each request.
- PG-Api-Version: Must be sent as v4.
Parameters to Be Signed and Encrypted, with Descriptions
For the pre-authorization capture transaction, the values in the request body are not sent in plain form; the encrypted value is sent in the signedRequest field.
The signedRequest value is obtained by encrypting a request constructed from the fields listed in the table below. If the field marked as mandatory (M) is missing or sent incorrectly, the transaction will result in an error.
The fields to be included in signedRequest, along with their rules, are specified in the table below. Abbreviations: (O) Optional, (M) Mandatory.
| Field | Format | Length | O/M | Description |
|---|---|---|---|---|
| orderId | String | (2-36) | M | The order number information of the pre-authorized transaction to be finalized (captured). |
| amount | Decimal | O | Indicates how much of the pre-authorized transaction is to be finalized. If not sent, the full amount of the transaction is used by default. The decimal separator must be a period (.). |
Generating the Request Token (signedRequest)
For security purposes, information in requests sent by merchants is not sent in plain form. Instead, the request body is expected to contain the signedRequest value, which is generated by signing and encrypting a request built according to the fields requested by Tami.
For a detailed explanation of the signedRequest generation steps and code samples, please see the Generating the Request Token (signedRequest) page.
API Request Example
{\n \"signedRequest\": \"eyJjdHkiOiJKV1QiLCJlbmMiOiJBMjU4R0NNIiwiYWxnIjoiZGlyIn0..6LsVOkTBQXnDVguawbuf.1xkjlc-YllBTO_P2uHaxqlcadXHvDy1YUOsMgaykMg-x3TsS-KkGe0ThlBMjkgqFzj6To8caQH1nc3wulhA0eljAk6ys4wrupHyXprcUu0TflMduUtySt1kso9jbsjg...\"\n}
The signedRequest value above has been shortened for example/test purposes. A real request contains a much longer JWE (encrypted token) value.
API Response Example
Response for a successful transaction:
{\n \"signedResponse\": \"eyJraWQiOiI5MzQ5ZTA5MRe5MDQ1Y3J1b1mHqXoIjp7InE4Y4Y4VoYjZ5YWVKiOiIxInZ0IiwiYWxnIjoiZGly...\"\n}
Response Parameters and Descriptions
When the transaction is successful, the response delivered by Tami contains only the signedResponse field. All other fields listed in the table below (success, systemTime, correlationId, orderId, amount, etc.) are not present in plain form in this case; all of them are carried in encrypted form inside the signedResponse field. You can only access these fields once the signedResponse value has been decoded. The decoding steps are described in the next heading.
When the transaction is unsuccessful, signedResponse is not returned at all; in this case success, systemTime, correlationId, errorCode, errorMessage, and errorGroup fields are returned directly in plain form.
| Parameter Name | Format | Where It Appears | Description |
|---|---|---|---|
| success | String | Inside signedResponse (plain if transaction unsuccessful) | Reports the outcome of the transaction. If true, the transaction was successful; if false, the transaction was unsuccessful. |
| systemTime | dateTime | Inside signedResponse (plain if transaction unsuccessful) | Indicates the date and time the response was generated by Tami. |
| correlationId | String | Inside signedResponse (plain if transaction unsuccessful) | Transaction number |
| transactionDate | dateTime | Inside signedResponse | Indicates the date and time the transaction took place. |
| orderId | String | Inside signedResponse | Order number |
| amount | Number | Inside signedResponse | Transaction amount |
| currency | String | Inside signedResponse | Transaction currency |
| errorCode | String | Plain (only when success:false) | Error code |
| errorMessage | String | Plain (only when success:false) | Error message |
| bankAuthCode | String | Inside signedResponse | Bank authorization code |
| bankReferenceNumber | String | Inside signedResponse | Retrieval reference number (RetRef) for the transaction |
| errorGroup | String | Plain (only when success:false) | Indicates the group of the relevant error. Merchants can manage their own rules by making use of the error code and error groups. |
Decoding the Response Token (signedResponse)
The steps required to decode the value delivered in the signedResponse field in order to access the parameters above will be provided in this section.
For a detailed explanation of the decoding steps and code samples, please see the Decoding the Response Token (signedResponse) page.
Code Examples
Below are links to code samples written in various programming languages. Through the link for your preferred programming language, you can examine in detail code written with pre-defined example values.
These samples contain code covering the relevant transaction type, and since they are written in different languages, it is also possible to observe various approaches and practices. This gives you the opportunity to work with clearer and more authentic examples suited to your preferred programming language.
- For C# Code Samples, click here.
- For VB.Net Code Samples, click here.
- For Java Code Samples, click here.
- For PHP Code Samples, click here.
- For NodeJS Code Samples, click here.
Please note that these samples are written with pre-defined values, and the necessary adaptation and security measures may need to be taken for their use in real projects.
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.
