Introduction

Intended Audience

This overview document is written for technical people with a background in payments services; and implementing online payment functionality to the e-commerce sites and/or internal. ERP systems using Paratika.

How to Contact Customer Support

For problems with transaction processing or your connection to the server, please contact Customer Support via phone 02123190625 or destek@paratika.com.tr email.

What is Paratika?

Paratika is an online payment solution developed by Payten Turkey. It offers a secure, easy and convenient checkout experience for both, customers and merchants. While Customers (Card Holders) enjoy the secure e-wallet and flexible payment features on check out pages; the Merchants are handling the payment without touching the credit card data so they remain PCI DSS compliant; and therefore eliminate the risks around fraud & secure storage of financially sensitive data.

Security

Paratika is built on a robust and secure communication protocol. Paratika API is a set of instructions submitted with standard HTTPS Post requests. At the server end, we use a certificate delivered by Verisign. The SSL encryption guarantees that it is our servers you are communicating with and that your data is transmitted in encrypted form. There is no need for a client SSL certificate. When we receive a request, we check the level of encryption. Directly TLSv1.1 version and next version is supported.

Supported Languages

The API supports all platforms & languages that can implement HTTP Post methods.

Response Parsing

Paratika responses by default will be in form of JSON format. You can use any JSON parsing tool or framework to process Paratika responses.

Test Environment

An API test environment is available and all API action types given in this document can be tested using by Paratika API Test URL. All API requests should be sent to this URL address using HTTP POST method.

Integration Environment

An API integration environment is available and all API action types given in this document can be tested using by Paratika API Test URL. All API requests should be sent to this URL address using HTTP POST method.

Request & Response

Paratika API Requests

A request to the Paratika API is made a by sending a POST HTTP request to Paratika API Endpoint URL. Each HTTP POST request send to the API URI should have a set of parameter-value pairs encoded in it, depending of the type of request being sent.

Paratika API Responses

The Paratika API response supports JSON data format. Each response, regardless of the success of the action, will return the RESPONSECODE and RESPONSEMSG parameters. Depending on the successfulness of the action the RESPONSECODE and RESPONSEMSG can have the specific value pairs. If an error has occurred and the API call is considered to be failed (RESPONSE is not equal to 00) the ERROR and ERRORCODE parameters will be present in the response.

Pagination

TO BE PROVIDED

Authentication

You authenticate to the API by providing your user information (secure credentials) in the request. You can manage your API user information from your account or by requesting related change from support team. Every API user have its own e-mail and password information. Your user e-mail and password pair carries many privileges, so be sure to keep them secret!

All API requests must be made over HTTPS. Calls made over plain HTTP will fail. You must authenticate properly for all requests.

How to integrate?

Hosted Page (HP)

This model requires the merchants to use Paratika's payment page hosted in Asseco environment. It is based on one way communication of the ‘transaction result’ to the Merchant system occurring at Step 4. HPP model simply assumes that the Merchant site has received the transmitted information and updated its own records accordingly. It has the following steps:

Step 1:

The Merchant Web Site makes a sale request by specifying the integration model as HPP. Order/Billing/Shipping details can also be passed at this stage to be displayed on Paratika payment page for Customer’s information only.

Step 2:

The payment request is processed, a session token is created and sent back to the merchant site. Merchant Web Site receives the token and redirects Customer’s Browser to Paratika Payment Pages with the given session token.

Step 3:

If there is any saved card detail for the Customer, his/her e-wallet is displayed for quick payment. If not, new card entry screen is displayed. Customer clicks on ‘pay’ button after entering/selecting the card to be used in payment. Paratika processes the payment accordingly.

Step 4:

Paratika redirects the Customer Browser to Merchant Web Site and also returns the transaction result.

Please note that Step 4 is a browser based HTTP re-direction and it all happens in customer's environment in which Asseco has no control over. There might be cases like where the customer may close the browser screen or internet connection may cuts off during this re-direction etc. Therefore merchants using this model should not completely rely on redirection process to obtain information about the payment result. They should use additional api calls to check the status of the payment. These details are available in API Model Integration document.

Direct POST - MOTO

This integration model is based on the scenario that the Payment Page is being hosted by Merchants but its form action is Direct Post to Paratika so that any financially sensitive data will be collected still at the convenience of a merchant hosted page but to be fully compatible with PCI DSS. This will overcome the shortage of the API integration model for the merchants willing 100% compliance with PCI DSS without any additional effort on their side. Please see the flow below for details.

Step 1:

The Merchant Core System makes a Session Token request in order to get a valid key value for defining the session.

Step 2:

This session token request is processed; a session token is created and sent back to the merchant system in the API response.

Step 3:

Merchant system serves the payment page using the given secure session token.

Extra Point Step:

In Direct Post model merchant need to do a query points with SESSIONTOKEN, CARDPAN,CARDEXPIRY parameters. According to QUERYPOINTS response sample form points input should be set as sale by points samples. And to send the payment to related payment system, merchant needs to send payment system name as paymentSystem input parameter at sample form. Payment system name can be get via QUERYPAYMENTSYSTEMS with SESSIONTOKEN and BIN.

Step 4:

Cardholder interacts with the page and clicks on Confirm button. Merchant system submits all information received via this page to Paratika system.

Step 5:

Paratika processes the payment details via an invisible interim page.

Step 6:

Paratika forwards the payment to the relevant VPOS, receives the result and redirect the cardholder back to merchant return url. The merchant is expected to listen and parse the payment result within the posted form.

Direct Post (MOTO) Test Form

<!DOCTYPE html> <html> <head> <title>Sample POST Form</title> <meta charset="utf-8"> <script> function hideCardPANData() { if (document .getElementById('isPayWithCardToken').checked) { document.getElementById('cardPANData').style.display = 'none'; document .getElementById('cardTokenContainer').style.display = 'block'; } else { document .getElementById('cardTokenContainer').style.display = 'none'; document.getElementById('cardPANData').style.display = 'block'; } } </script> <style type="text/css"> form { display: table; } p { display: table-row; } label { display: table-cell; } input { display: table-cell; } </style> </head> <body onload="hideCardPANData();"> <form action="https://entegrasyon.paratika.com.tr/merchant/post/sale/[SECURE_SESSION_TOKEN]" method="post"> <div> <label for="isPayWithCardToken">Pay with Card Token</label> <input type="checkbox" onclick="hideCardPANData();" name="isPayWithCardToken" id="isPayWithCardToken" autocomplete="off" maxlength="32" /> </div> <div class="container"> <div id="cardPANData"> <p> <label for="cardOwner">Card Owner Name</label> <input type="text" name="cardOwner" id="cardOwner" autocomplete="off" maxlength="32" /> </p> <p> <label for="pan">Card Number (PAN) </label> <input type="text" id="pan" name="pan" autocomplete="off" maxlength="19" /> </p> <p> <label for="expiryMonth">Expiration Date</label> <select name="expiryMonth" id="expiryMonth"> <option value="01">January</option> <option value="02">February</option> <option value="03">March</option> <option value="04">April</option> <option value="05">May</option> <option value="06">June</option> <option value="07">July</option> <option value="08">August</option> <option value="09">September</option> <option value="10">October</option> <option value="11">November</option> <option value="12">December</option> </select> <select name="expiryYear" id="expiryYear"> <option value="2016">2016</option> <option value="2017">2017</option> <option value="2018">2018</option> <option value="2019">2019</option> <option value="2020">2020</option> <option value="2021">2021</option> <option value="2022">2022</option> <option value="2023">2023</option> <option value="2024">2024</option> <option value="2025">2025</option> <option value="2026">2026</option> <option value="2027">2027</option> <option value="2028">2028</option> <option value="2029">2029</option> <option value="2030">2030</option> <option value="2031">2031</option> <option value="2032">2032</option> <option value="2033">2033</option> <option value="2034">2034</option> </select> </p> <p> <label for="cvv">Security Code (CVV)</label> <input type="input" name="cvv" id="cvv" autocomplete="off" maxlength="4" /> </p> <p> <label for="saveCard">Save Card</label> <input type="checkbox" name="saveCard" id="saveCard" value="YES" /> </p> <p> <label for="cardName">Card Name</label> <input type="text" name="cardName" id="cardName" /> </p> <p> <label for="installmentCount">Installment Count</label> <input type="text" name="installmentCount" id="installmentCount" /> </p> <input type="hidden" value="" name="points" id="points" /> <input type="hidden" value="" name="paymentSystem" id="paymentSystem" /> </div> <div id="cardTokenContainer"> <p> <label for="cardToken">>Card Token</label> <input type="text" name="cardToken" id="cardToken" autocomplete="off" maxlength="64" /> </p> <p> <label for="installmentCount">Installment Count</label> <input type="text" name="installmentCount" id="installmentCount" /> </p> </div> <input type="submit" value="Submit" /> </form> <script type="text/javascript" src="https://PF_HOST/paratika/static/external/whitewolf-v3.js"></script> <script type="text/javascript"> whitewolf.run(h.online-metrix.net, ORG_ID, SESSIONTOKEN); </script> <noscript> <iframe style="width: 100px; height: 100px; border: 0; position: absolute; top: -5000px;" src="https://h.online-metrix.net/tags?org_id=ORG_ID&session_id=UNIQUE_SESSION_ID&pageid=PAGEID"> </iframe> </noscript> </body> </html>

Direct POST - 3D Secure

This integration model is based on the scenario that the Payment Page is being hosted by Merchants but its form action is Direct Post to Paratika so that any financially sensitive data will be collected still at the convenience of a merchant hosted page but to be fully compatible with PCI DSS. This will overcome the shortage of the API integration model for the merchants willing 100% compliance with PCI DSS without any additional effort on their side. Please see the flow below for details.

Step 1:

The Merchant Core System makes a Session Token request in order to get a valid key value for defining the session.

Step 2:

The payment session request is processed; a session token is created and sent back to the merchant system in the API response.

Step 3:

Merchant system serves the payment & wallet page using the given secure session token.

Extra Point Step:

In Direct Post model merchant need to do a query points with SESSIONTOKEN, CARDPAN,CARDEXPIRY parameters. According to QUERYPOINTS response sample form points input should be set as sale by points samples. And to send the payment to related payment system, merchant needs to send payment system name as paymentSystem input parameter at sample form. Payment system name can be get via QUERYPAYMENTSYSTEMS with SESSIONTOKEN and BIN.

Step 4:

Cardholder interacts with the page and clicks on Confirm button. Merchant system submits all information received via this page to Paratika system.

Step 5:

Paratika processes the payment details (and optionally starts 3D authentication process on behalf of the merchant) via an invisible interim page.

Step 6:

Paratika performs MOTO sale (or optionally directs the cardholder to 3D authentication servers).

Step 7:

ACS server serves the 3D authentication page where the cardholder enters a dynamic code sent to his/her mobile phone.

Step 8:

ACS server authenticates the user and returns back to Paratika invisible interim page. * Depending on authentication response, the transaction sent to bank either with full 3D details (if 3D authentication is done successfully) or as MOTO payment (if 3D authentication has failed).

Step 9:

Paratika make return the response to merchant return url

Direct POST (3D Secure) Test Form

<!DOCTYPE html> <html> <head> <title>Sample POST Form</title> <meta charset="utf-8"> <script> function hideCardPANData() { if (document .getElementById('isPayWithCardToken').checked) { document.getElementById('cardPANData').style.display = 'none'; document .getElementById('cardTokenContainer').style.display = 'block'; } else { document .getElementById('cardTokenContainer').style.display = 'none'; document.getElementById('cardPANData').style.display = 'block'; } } </script> <style type="text/css"> form { display: table; } p { display: table-row; } label { display: table-cell; } input { display: table-cell; } </style> </head> <body onload="hideCardPANData();"> <form action="https://entegrasyon.paratika.com.tr/paratika/api/v2/post/sale3d/[SECURE_SESSION_TOKEN]" method="post"> <div> <label for="isPayWithCardToken">Pay with Card Token</label> <input type="checkbox" onclick="hideCardPANData();" name="isPayWithCardToken" id="isPayWithCardToken" autocomplete="off" maxlength="32" /> </div> <div class="container"> <div id="cardPANData"> <p> <label for="cardOwner">Card Owner Name</label> <input type="text" name="cardOwner" id="cardOwner" autocomplete="off" maxlength="32" /> </p> <p> <label for="pan">Card Number (PAN)</label> <input type="text" id="pan" name="pan" autocomplete="off" maxlength="19" /> </p> <p> <label for="expiryMonth">Expiration Date</label> <select name="expiryMonth" id="expiryMonth"> <option value="01">January</option> <option value="02">February</option> <option value="03">March</option> <option value="04">April</option> <option value="05">May</option> <option value="06">June</option> <option value="07">July</option> <option value="08">August</option> <option value="09">September</option> <option value="10">October</option> <option value="11">November</option> <option value="12">December</option> </select> <select name="expiryYear" id="expiryYear"> <option value="2016">2016</option> <option value="2017">2017</option> <option value="2018">2018</option> <option value="2019">2019</option> <option value="2020">2020</option> <option value="2021">2021</option> <option value="2022">2022</option> <option value="2023">2023</option> <option value="2024">2024</option> <option value="2025">2025</option> <option value="2026">2026</option> <option value="2027">2027</option> <option value="2028">2028</option> <option value="2029">2029</option> <option value="2030">2030</option> <option value="2031">2031</option> <option value="2032">2032</option> <option value="2033">2033</option> <option value="2034">2034</option> </select> </p> <p> <label for="cvv">Security Code (CVV)</label> <input type="input" name="cvv" id="cvv" autocomplete="off" maxlength="4" /> </p> <p> <label for="saveCard">Save Card</label> <input type="checkbox" name="saveCard" id="saveCard" value="YES" /> </p> <p> <label for="cardName">Card Name</label> <input type="text" name="cardName" id="cardName" /> </p> <p> <label for="installmentCount">Installment Count</label> <input type="text" name="installmentCount" id="installmentCount" /> </p> <input type="hidden" value="" name="points" id="points" /> <input type="hidden" value="" name="paymentSystem" id="paymentSystem" /> </div> </div> <div id="cardTokenContainer"> <p> <label for="cardToken">Card Token</label> <input type="text" name="cardToken" id="cardToken" autocomplete="off" maxlength="64" /> </p> <p> <label for="installmentCount">Installment Count</label> <input type="text" name="installmentCount" id="installmentCount" /> </p> </div> <input type="submit" value="Submit" /> </form> <script type="text/javascript" src="https://PF_HOST/paratika/static/external/whitewolf-v3.js"></script> <script type="text/javascript"> whitewolf.run(h.online-metrix.net, ORG_ID, SESSIONTOKEN); </script> <noscript> <iframe style="width: 100px; height: 100px; border: 0; position: absolute; top: -5000px;" src="https://h.online-metrix.net/tags?org_id=ORG_ID&session_id=UNIQUE_SESSION_ID&pageid=PAGEID"> </iframe> </noscript> </body> </html>

Cardless Direct POST - 3D Secure

• Maximum Mobil

Cardless DIRECT POST (3D Secure) Test Form

<!DOCTYPE html> <html> <head> <title>Sample Cardless POST Form</title> <meta charset="utf-8"> </head> <body> <form action="https://entegrasyon.paratika.com.tr/paratika/api/v2/post/sale3d/[SECURE_SESSION_TOKEN]" method="post"> <input type="text" name="installmentCount" id="installmentCount" /> <input type="hidden" value="" name="cardlessPaymentSystem" id="cardlessPaymentSystem" /> <input type="submit" value="Submit" /> </form> <script type="text/javascript" src="https://PF_HOST/paratika/static/external/whitewolf-v3.js"></script> <script type="text/javascript"> whitewolf.run(h.online-metrix.net, ORG_ID, SESSIONTOKEN); </script> <noscript> <iframe style="width: 100px; height: 100px; border: 0; position: absolute; top: -5000px;" src="https://h.online-metrix.net/tags?org_id=ORG_ID&session_id=UNIQUE_SESSION_ID&pageid=PAGEID"> </iframe> </noscript> </body> </html>

Direct Post 3D Authentication

This integration model is based on the scenario that the process of 3D authentication is finished seperately from the Sale / Preauth API Call. Merchant offers a page where Card Holder enters his/her card data and submits them. This is where the process of 3D authentication starts. Depending on the response given from the authentication process, merchant issues authorization via API.

Step 1:

The Merchant Core System makes a Session Token request in order to get a valid key value for defining the session.

Step 2:

The payment session request is processed; a session token is created and sent back to the merchant system in the API response.

Step 3:

Merchant system serves the payment & wallet page using the given secure session token.

Step 4:

Cardholder interacts with the page and clicks on Submit button. Merchant system submits all information received via this page to MSU system.

Step 5:

MSU receives POST request from the merchant's page and directs it to the 3D ACS (Access Control Server) in order to continue with the 3D authentication flow.

Step 6:

ACS serves the 3D Security Page where the Card Holder must enter the correct (dynamic) code sent to his/her mobile phone in order to authenticate.

Step 7:

MSU handles the response of the 3D Authentication of success or failure.

Step 8:

The final response of the 3D Authentication process is forwarded to the merchant's page. The merchant is expected to listen and parse the result within the posted form later on issues authorization via API (Sale / Preauth).

3D Authentication Direct Post Test Form

3D Authentication with Card Data Form

			
<form action="test/paratika/api/v2/post/auth3d/[SECURE_SESSION_TOKEN]" method="post">
	<input type="text" name="cardOwner" placeholder="Card Owner" maxlength="32" />
	<input type="text" name="pan" placeholder="PAN" maxlength="19" />
	<select name="expiryMonth">
		<option value="01">January</option>
		<option value="02">February</option>
	</select> 
	<select name="expiryYear">
		<option value="2019">2019</option>
		<option value="2020">2020</option>
		<option value="2021">2021</option>
	</select>
	<input type="password" name="cvv" placeholder="CVV" maxlength="4" />
	<input type="checkbox" name="saveCard" />
	<input type="text" name="cardName" placeholder="Card Name"/>
	<input type="text" name="cardCutoffDay" placeholder="Card Cutoff Day"/>
	<input type="text" name="installmentCount" placeholder="Installment Count"/>
	<input type="hidden" name="points" />
	<input type="submit" value="Submit" />
</form>
			
		

3D Authentication with Card Token Form

			
<form action="test/paratika/api/v2/post/auth3d/[SECURE_SESSION_TOKEN]" method="POST">
	<input name="pan" type="text" size="20" />
	<input name="cardOwner" type="text" size="20" />
	<input name="expiryMonth" type="text" size="2"/>
	<input name="expiryYear" type="text" size="4"/>
	<input name="cvv" type="text" size="4"/>
	<input name="cardCutoffDay" type="text" size="2"/>
	<input name="callbackUrl" value="[merchant-return-url-handler]" />
	<input type="submit" value="Complete Payment"/>
</form>

or if the payment will be done with an existing tokenized card
			
<form action="test/paratika/api/v2/post/auth3d/[SECURE_SESSION_TOKEN]" method="POST">
	<input name="cardToken" type="text"  placeholder="Card Token"size="20" />
	<input name="cvv" type="text" placeholder="CVV" size="4" />
	<input type="submit" value="Complete Payment"/>
</form>
			
		

API & HPP URLs

API URL: https://entegrasyon.paratika.com.tr/paratika/api/v2
Hosted Payment Page URL (HPP): https://entegrasyon.paratika.com.tr/payment/[SECURE_SESSION_TOKEN]
DirectPost 3D URL: https://entegrasyon.paratika.com.tr/paratika/api/v2/post/sale3d/[SECURE_SESSION_TOKEN]
DirectPost Non3D URL: https://entegrasyon.paratika.com.tr/merchant/post/sale/[SECURE_SESSION_TOKEN]

Error Handling

If a request results in an error the ERROR and ERRORCODE parameters will be present in the response. Generally, there are two types of errors that can occur: core errors and payment gateway originating errors.

Core Errors

Core errors occur mostly because of invalid parameter values. These errors have the following code format: ERR100xx

Payment Gateway (vPOS) Errors

The Paratika API uses a set of error codes for errors that originate from the payment gateway that is being used. This error set is derived from the ISO-8583 field 39 response values. The code format for these errors is ERR200xx.

Additional error related response parameters

There are two additional API response parameters that may help you indicate the cause of the error that has occurred in the case where the error originates from the payment gateway. These are PGTRANERRORCODE and PGTRANERRORTEXT . These two parameters are especially useful when you get an error from the payment gateway that is still not mapped in our error set. In this case the PGTRANERRORCODE and PGTRANERRORTEXT can help you determine the cause of the error.

Error response examples

Here are API response examples for multiple cases when an error has occurred.

Notifications

Paratika has a built-in mechanism that is used to notify the respective merchant of events related to financial transactions.
More specifically, Paratika sends notification messages to a merchant about specific events when:

• An approved transaction is performed

How It Works?

A merchant should create a listener endpoint and the URL pointing to this endpoint should be added to this merchant's profile. Paratika then sends notifications to the merchant when a particular event occurs which is mentioned in the list above.
When one such time event occurs, Paratika then sends a secure FORM POST to the URL containing the respective parameters shown in the right.

Metadata

Paratika Domain contains some important ojects and shares them with integrated clients.

Transaction

Each financial request refers a transaction in Paratika domain. All settlement is done via transaction records.

A transaction has a type that can have one of these status any time. Please see the definitions given right handside.

Other Usage Features

You can find other usages of Paratika API below

Pay By Link

Providing an URL Link to the Payment Page is an alternative way of inviting card holders via remote channels like SMS, Mobile App Notificatins, Push Messages, e-Mails etc to make a payment. In this model, merchants need to create a payment page link and send it to their customers. When customers click on the link, they will be directed to the payment page where it already has all the neccessary payment information such as payment amount, shopping basket content etc. Then the customer will enter the card information and complete the payment.

In order to create a payment page link, merchants are required to send a SESSIONTOKEN request to Paratika API by supplying all the relevant parameters. Paratika will process this request, generate a session token information and return it to the merchant. This token is then used to generate the payment page link in order to do a sale or preauth transaction and it's sent to the cardholder (customer). The customer is expected to click on the link and complete the transaction before the link expires. When the clicked link has expired, the cardholder will be directed to the "Finalised Session" page. There is also another page called "Invalid Session" page which is served when the provided payment page link does not include a valid session token value. The expiry duration of the payment page link is set by the merchants using SESSIONTOKEN parameter which has a default value of 7 Days.

The response of successfully completed transactions is posted to the URL address specified in RETURNURL parameter of the SESSIONTOKEN request.

Step 1:

Merchant creates a new session token via Paratika API SESSIONTOKEN request.

Step 2:

Merchant generates payment page link with that session token (E.g. https://test.paratika.com.tr/merchant/payment/[SESSIONTOKEN])

Step 3:

Link will be sent via SMS, e-mail, mobile app notification etc. to customer

Step 4:

Customer goes to the payment page via that link and finish the sale action.

Step 5:

Response of sale action will be returned to the URL which was mentioned on RETURNURL parameter's value as a POST request.

Test Cards

Here you can find Test Cards for different Banks
For all Nestpay banks, "a" should be used as 3D Secure password.

Financial Transaction

The available transaction types in Paratika system are listed and explained below:

Sale

A Sale transaction is a credit card transaction that immediately charges a customer's credit card.

Request parameters:

ACTION:

SALE, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTPAYMENTID:

string, conditional Max length: 128 Unique Payment ID given by Merchant.

CUSTOMER:

string, conditional Max length: 128 The Merchant System ID for customer. It must be unique within a Merchant.

AMOUNT:

decimal, conditional Max length: 30 Amount of payment / transaction. Please note that, this amount is tax included, Paratika doesn't consider any other tax calculation.

CURRENCY:

string, conditional Max length: 3 ISO Alpha transaction currency code like TRY, EUR, USD, GBP. Please check https://en.wikipedia.org/wiki/ISO_4217#Position_of_ISO_4217_code_in_amounts for details. See all possible values (33)

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

CUSTOMEREMAIL:

string, conditional Max length: 64 Customer e-mail. This information should be passed correctly if the customer information services are used.

CUSTOMERNAME:

string, conditional Max length: 128 Name of the Customer. This information should be passed correctly if the customer information services are used.

CUSTOMERPHONE:

string, conditional Max length: 64 Customer phone / mobile number. This information should be passed correctly if the customer information services are used.

CUSTOMERIP:

string, optional Max length: 39 Customer IP Address

CUSTOMERUSERAGENT:

string, optional Max length: 512 Customer User Agent

CUSTOMERBIRTHDAY:

date, optional Max length: 16 Format: [dd-MM-yyyy] Customer Birthday.

TCKN:

string, optional Max length: 16 Customer Identity Number.

AUTH3DTOKEN:

string, optional Max length: 16 description

CARDTOKEN:

string, conditional Max length: 64 Secure alphanumeric value replacing card number & expiry date. Required when none of the other card information are provided.

CARDPANTYPE:

string, optional Max length: 32 The Card Pan Type parameter is used to determine the type of card we will use in the transaction See all possible values (1)

CARDPAN:

string, conditional Max length: 26 PAN (Primary account number), card number. Please check https://en.wikipedia.org/wiki/Bank_card_number for details.

CARDEXPIRY:

string, conditional Max length: 7 Expiry date of the card. Format should be [mm.yy].

NAMEONCARD:

string, conditional Max length: 64 Name on the card.

CARDCVV:

string, optional Max length: 4 Security number of the card, CVV value.

SAVECARD:

string, optional Max length: 3 If this has 'yes' value all cards are saved automatically on the payment page. Save Card parameter cannot be used for API integration model.

CARDSAVENAME:

string, optional Max length: 64 Given name for the saved card.

INSTALLMENTS:

integer, optional Max length: 2 Default value: '1' Number of installments. Specified number should exist in the payment system as defined.

POINTS:

string, optional Max length: 500

Sale by points can be used via points argument of sale action. This parameter gets its argument as a json format and parse it according to payment system.

AKBANK SALE BY POINTS SAMPLE

• POINTS must be json String, you can use POINTS argument in SALE method like below
• POINTS : [{"name":"XCBCHIPPARA", "value":"10"}]
• MULTIPLE POINTS USAGE: [{"name":"XCBCHIPPARA", "value":"10"},{"name":"PCBCHIPPARA", "value":"10"},{"name":"CCBCHIPPARA", "value":"10"}]

ISBANK SALE BY POINTS SAMPLE

• POINTS must be JSOn String, you can use POINTS argument in SALE method like below
• POINTS : [{"name":"MAXIPUAN","value":"1"}]

FINANSBANK SALE BY POINTS SAMPLE

• You can use points if and only if PARAPUAN equal to AMOUNT
• POINTS must be JSOn String, you can use POINTS argument in SALE method like below
POINTS : [{"name":"PARAPUAN","value":"10"}]

TEB BANK SALE BY POINTS SAMPLE

• You can use points if and only if KULLANBONUS equal to AMOUNT
• POINTS must be JSOn String, you can use POINTS argument in SALE method like below
POINTS : [{"name":"KULLANBONUS","value":"10"}]

HALKBANK SALE BY POINTS SAMPLE

• POINTS must be json String, you can use POINTS argument in SALE method like below
• POINTS : [{"name":"ODUL", "value":"10"}]

AKTIFBANK SALE BY POINTS SAMPLE

• POINTS must be json String, you can use POINTS argument in SALE method like below
• POINTS : [{"name":"KULLANPUAN","value":"10"}]

GARANTI BANK SALE BY POINTS SAMPLE

• POINTS must be json String, you can use POINTS argument in SALE method like below
• POINTS : [{"name":"FBB","value":"5160.02"},{"name":"BNS","value":"91462.68"}]

YAPI KREDI BANK SALE BY POINTS SAMPLE

• POINTS must be json String, you can use POINTS argument in SALE method like below
• POINTS : [{"name":"PUAN","value":"10.00"}]

HSBC BANK SALE BY POINTS SAMPLE

• POINTS must be json String, you can use POINTS argument in SALE method like below
• POINTS : [{"name":"ODUL","value":"10.00"}]

VAKIFBANK SALE BY POINTS SAMPLE

• POINTS must be JSOn String, you can use POINTS argument in SALE method like below
• POINTS : [{"name":"PUAN","value":"283567.72"}]

SEKERBANK SALE BY POINTS SAMPLE

• POINTS must be JSON String, you can use POINTS argument in SALE method like below
• POINTS : [{"name":"KULLANBONUS","value":"10"}]

DENIZBANK SALE BY POINTS SAMPLE

• POINTS must be JSON String, you can use POINTS argument in SALE method like below
• POINTS : [{"name":"BONUSAMOUNT","value":"10.00"}]

ZIRAATBANK SALE BY POINTS SAMPLE

• POINTS must be JSON String, you can use POINTS argument in SALE method like below
• POINTS : [{"name":"PUANSORGU","value":"PUANSORGU"},{"name":"KULLANPUAN","value":"10"}]

BILLTOADDRESSLINE:

string, optional Max length: 255 Bill To Address Line

BILLTOCITY:

string, optional Max length: 32 Bill To City

BILLTOPOSTALCODE:

string, optional Max length: 16 Bill To Postal Code

BILLTOCOUNTRY:

string, optional Max length: 32 Bill To Country
An alpha-3 code in ISO 3166-1 standard should be sent.

SHIPTOADDRESSLINE:

string, optional Max length: 255 Ship To Address Line

SHIPTOCITY:

string, optional Max length: 32 Ship To City

SHIPTOPOSTALCODE:

string, optional Max length: 16 Ship To Postal Code

SHIPTOCOUNTRY:

string, optional Max length: 32 Ship To Country
An alpha-3 code in ISO 3166-1 standard should be sent.

FASTSHIPPING:

string, optional Max length: 3 This param indicates that the shipping option is selected as fast, urgent, quick etc. If fast shipment is the option, then the merchant should send this parameter with "yes" value. See all possible values (2)

EXTRA:

string, optional Max length: 1024 Extra Parameter is a custom parameter that is used to pass additional parameters to session token. This parameter is expected to be in JSON(URL-ENCODED) format. If they are mispelled, they will be ignored! Supported parameters are: CardHolderAgreementMode(value: NONE/SHOW/SHOWCHECKED/SHOWCHECKEDDISABLED), AlwaysSaveCard(value: true/false), BuyerType (value: L for logged in customer; A for anonymous, F for the first shopping with memebership. OR it can be 0, 1, 2 for those cases), IsbankBolumKodu(string), IframeDomainUrl indicates from which URL address payment will be proceesed., PREAUTH=YES parameter indicates that payment will be processed as pre-authorization even if is started as sale., IGNORECUSTOMERCOMMISSION(values : YES/NO).
EXTRA: {"AlwaysSaveCard": "true", "BuyerType": "L", "IsbankBolumKodu": 12, "CardHolderAgreementMode": "SHOWCHECKED", "IGNORECUSTOMERCOMMISSION" : "YES"}

Other bank parameters

• MAXIMUMMOBIL - include Maximum Mobil payment system name like below to have Maximum Mobil tab on Default HPP
  {"MaximumMobilPaymentSystem":"PaymentSystemName"}
• GIROGATE payment methods. If one of payment methods is sent as "Yes", authentication will be done using GiroGate payment methods. Possible values: YES/NO.
  • SOFORT: {"SOFORT": "YES"}
  • SAFETYPAY: {"SAFETYPAY": "YES"}
  • QIWI: {"QIWI": "YES"}
  • GIROPAY: {"GIROPAY": "YES"}
  • IDEAL: {"IDEAL": "YES"}
  • FINNISHONLINEBANKING: {"FINNISHONLINEBANKING": "YES"}
  • BANCONTACT: {"BANCONTACT": "YES"}
  • ALIPAY: {"ALIPAY": "YES"}
  • MULTIBANCO: {"MULTIBANCO": "YES"}
  • TRUSTPAY: {"TRUSTPAY": "YES"}
  • EPS: {"EPS": "YES"}
  • MYBANK: {"MYBANK": "YES"}
  • P24: {"P24": "YES"}
  • BOLETO: {"BOLETO": "YES"}
  • ELO: {"ELO": "YES"}
  • SEPA: {"SEPA": "YES"}
  • UPOP: {"UPOP": "YES"}
• ISBANK - include in extra like below to send agriculture template info to Isbank when doing imece card operations.
  {"IMCKOD":"imckod", "FDONEM":"fdonem"}
• SEKERBANK - can also take these extra parameters:
  {"HASATKARTSATIS", "VADEKODU", "VADEADEDI", "URUNKODU", "PLASIYERNO", "FATURANO"}

• ISBANK_LOAN - The following fields must be used for Kuveytturk shopping credit and all fields are required. ISBANK_LOAN parameter must be sent "YES".
  {"ISBANK_LOAN":"YES", "ISBANK_LOAN.maximum_term":"5"}
• KUVEYTTURK_LOAN - The following fields must be used for Kuveytturk shopping credit and all fields are required. KUVEYTTURK_LOAN parameter must be sent "YES".
  {"KUVEYTTURK_LOAN":"YES", "KUVEYTTURK_LOAN.softDescriptor":"Finansman islem bilgisi", "KUVEYTTURK_LOAN.commissionAmount":"0", "KUVEYTTURK_LOAN.orderItemCount":"1", "KUVEYTTURK_LOAN.categoryCode":"1101", "KUVEYTTURK_LOAN.unitPrice":"100", "KUVEYTTURK_LOAN.count":"1", "KUVEYTTURK_LOAN.channel":"WM"}
• NKOLAY_LOAN - The following fields must be used for NKolay shopping credit and all fields are required. NKolay parameter must be sent "YES".
  {"NKOLAY_LOAN":"YES", "NKolay.identityNumber":"11920171664", "NKolay.products": {"NKolay.name": "phone","NKolay.categoryId": 1,"NKolay.categoryName": "Cep Telefonu", "NKolay.quantity": 1,"NKolay.totalPrice": 8000.0}
• FIBABANKA_LOAN - The following fields must be used for Fibabanka shopping credit and all fields are required. FIBABANKA_LOAN parameter must be sent "YES".
  {"FIBABANKA_LOAN":"YES", "FIBABANKA_LOAN.productType":"5"}

SHIPTOPHONE:

string, optional Max length: 32 Phone number of shipment information

BILLTOPHONE:

string, optional Max length: 32 Phone number of billment information

BUYERTYPE:

string, optional Max length: 1 Default value: 'A' Member/Anonymous user flag See all possible values ()

SELLERID:

string, optional Max length: 1024 Unique value per seller.

COMMISSIONAMOUNT:

string, optional Max length: 512 description

DISCOUNTAMOUNT:

decimal, optional Max length: 30 The amount to be discounted from ORDERITEMS total amount. When provided, the AMOUNT field should be equal to the subtraction of ORDERITEMS total amount with DISCOUNTAMOUNT. (AMOUNT = ORDERITEMS - DISCOUNTAMOUNT)

FORGROUP:

string, optional Max length: 3 Default value: 'YES' Specifies the for group featured usages. Available values are 'yes' and 'no'.

TOTALSELLERCOMMISSIONAMOUNT:

decimal, optional Max length: 30 description

NOTIFICATIONURL:

string, optional Max length: 255 description

SELLERPAYMENTAMOUNT:

string, optional Max length: 512 description

THREATMETRIXSESSIONID:

string, optional Max length: 128 description

TMXSESSIONQUERYINPUT:

string, optional Max length: 100000 Session query input that can be retrieved from Threat Metrix. A request needs to be sent at https://h-api.online-metrix.net/api/session-query, with those parameters: org_id (provided by Paratika), api_key (provided by Paratika), session_id (unique identifier, stored in the session, can be retrieved from QUERYSESSION), service_type (value should be 'session-policy'), event_type (value should be 'payment'), policy (provided by Paratika). e.g. https://h-api.online-metrix.net/api/session-query?org_id=[org_id]&api_key=[api_key]&session_id=[session_id]&service_type=session-policy&event_type=payment&policy=[policy]

CUSTOMERTYPE:

string, optional Max length: 32 description See all possible values (5)

CAMPAIGNS:

string, optional Max length: 1024 It represents the campaigns which is provided encoded JSON object. Example: [{"campaignCode": "taks3","campaignName": "2","campaignExtra": "ArtiTaksit"}] - while sending the request it must be encoded

MERCHANTNOTE:

string, optional Max length: 50 If the merchant has a note regarding payment, it should be written to this parameter.

Preauth

A PreAuth transaction is a credit card transaction that reserves funds on a customer's credit card. PreAuth transaction does not charge the card until you perform a PostAuth transaction. Please note that Pre-Authorizations reserve funds for varying periods, depending on the issuing credit card company's policy. The period may be as little as three days or as long as several months. For your protection it is recommended that you confirm delivery of the product/service as soon as possible after pre-authorization.

Request parameters:

ACTION:

PREAUTH, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTPAYMENTID:

string, conditional Max length: 128 Unique Payment ID given by Merchant.

CUSTOMER:

string, conditional Max length: 128 The Merchant System ID for customer. It must be unique within a Merchant.

AMOUNT:

decimal, conditional Max length: 30 Amount of payment / transaction. Please note that, this amount is tax included, Paratika doesn't consider any other tax calculation.

CURRENCY:

string, conditional Max length: 3 ISO Alpha transaction currency code like TRY, EUR, USD, GBP. Please check https://en.wikipedia.org/wiki/ISO_4217#Position_of_ISO_4217_code_in_amounts for details. See all possible values (33)

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

CARDTOKEN:

string, conditional Max length: 64 Secure alphanumeric value replacing card number & expiry date. Required when none of the other card information are provided.

CARDPANTYPE:

string, optional Max length: 32 The Card Pan Type parameter is used to determine the type of card we will use in the transaction See all possible values (1)

CARDPAN:

string, conditional Max length: 26 PAN (Primary account number), card number. Please check https://en.wikipedia.org/wiki/Bank_card_number for details.

CARDEXPIRY:

string, conditional Max length: 7 Expiry date of the card. Format should be [mm.yy].

NAMEONCARD:

string, conditional Max length: 64 Name on the card.

CUSTOMEREMAIL:

string, conditional Max length: 64 Customer e-mail. This information should be passed correctly if the customer information services are used.

CUSTOMERNAME:

string, conditional Max length: 128 Name of the Customer. This information should be passed correctly if the customer information services are used.

CUSTOMERPHONE:

string, conditional Max length: 64 Customer phone / mobile number. This information should be passed correctly if the customer information services are used.

CUSTOMERIP:

string, optional Max length: 39 Customer IP Address

CUSTOMERUSERAGENT:

string, optional Max length: 512 Customer User Agent

CUSTOMERBIRTHDAY:

date, optional Max length: 16 Format: [dd-MM-yyyy] Customer Birthday.

TCKN:

string, optional Max length: 16 Customer Identity Number.

AUTH3DTOKEN:

string, optional Max length: 16 description

INSTALLMENTS:

integer, optional Max length: 2 Default value: '1' Number of installments. Specified number should exist in the payment system as defined.

CARDCVV:

string, optional Max length: 4 Security number of the card, CVV value.

SAVECARD:

string, optional Max length: 3 If this has 'yes' value all cards are saved automatically on the payment page. Save Card parameter cannot be used for API integration model.

CARDSAVENAME:

string, optional Max length: 64 Given name for the saved card.

BILLTOADDRESSLINE:

string, optional Max length: 255 Bill To Address Line

BILLTOCITY:

string, optional Max length: 32 Bill To City

BILLTOPOSTALCODE:

string, optional Max length: 16 Bill To Postal Code

BILLTOCOUNTRY:

string, optional Max length: 32 Bill To Country
An alpha-3 code in ISO 3166-1 standard should be sent.

SHIPTOADDRESSLINE:

string, optional Max length: 255 Ship To Address Line

SHIPTOCITY:

string, optional Max length: 32 Ship To City

SHIPTOPOSTALCODE:

string, optional Max length: 16 Ship To Postal Code

SHIPTOCOUNTRY:

string, optional Max length: 32 Ship To Country
An alpha-3 code in ISO 3166-1 standard should be sent.

FASTSHIPPING:

string, optional Max length: 3 This param indicates that the shipping option is selected as fast, urgent, quick etc. If fast shipment is the option, then the merchant should send this parameter with "yes" value. See all possible values (2)

EXTRA:

string, optional Max length: 1024 Extra Parameter is a custom parameter that is used to pass additional parameters to session token. This parameter is expected to be in JSON(URL-ENCODED) format. If they are mispelled, they will be ignored! Supported parameters are: CardHolderAgreementMode(value: NONE/SHOW/SHOWCHECKED/SHOWCHECKEDDISABLED), AlwaysSaveCard(value: true/false), BuyerType (value: L for logged in customer; A for anonymous, F for the first shopping with memebership. OR it can be 0, 1, 2 for those cases), IsbankBolumKodu(string), IframeDomainUrl indicates from which URL address payment will be proceesed., PREAUTH=YES parameter indicates that payment will be processed as pre-authorization even if is started as sale., IGNORECUSTOMERCOMMISSION(values : YES/NO).
EXTRA: {"AlwaysSaveCard": "true", "BuyerType": "L", "IsbankBolumKodu": 12, "CardHolderAgreementMode": "SHOWCHECKED", "IGNORECUSTOMERCOMMISSION" : "YES"}

Other bank parameters

• MAXIMUMMOBIL - include Maximum Mobil payment system name like below to have Maximum Mobil tab on Default HPP
  {"MaximumMobilPaymentSystem":"PaymentSystemName"}
• GIROGATE payment methods. If one of payment methods is sent as "Yes", authentication will be done using GiroGate payment methods. Possible values: YES/NO.
  • SOFORT: {"SOFORT": "YES"}
  • SAFETYPAY: {"SAFETYPAY": "YES"}
  • QIWI: {"QIWI": "YES"}
  • GIROPAY: {"GIROPAY": "YES"}
  • IDEAL: {"IDEAL": "YES"}
  • FINNISHONLINEBANKING: {"FINNISHONLINEBANKING": "YES"}
  • BANCONTACT: {"BANCONTACT": "YES"}
  • ALIPAY: {"ALIPAY": "YES"}
  • MULTIBANCO: {"MULTIBANCO": "YES"}
  • TRUSTPAY: {"TRUSTPAY": "YES"}
  • EPS: {"EPS": "YES"}
  • MYBANK: {"MYBANK": "YES"}
  • P24: {"P24": "YES"}
  • BOLETO: {"BOLETO": "YES"}
  • ELO: {"ELO": "YES"}
  • SEPA: {"SEPA": "YES"}
  • UPOP: {"UPOP": "YES"}
• ISBANK - include in extra like below to send agriculture template info to Isbank when doing imece card operations.
  {"IMCKOD":"imckod", "FDONEM":"fdonem"}
• SEKERBANK - can also take these extra parameters:
  {"HASATKARTSATIS", "VADEKODU", "VADEADEDI", "URUNKODU", "PLASIYERNO", "FATURANO"}

• ISBANK_LOAN - The following fields must be used for Kuveytturk shopping credit and all fields are required. ISBANK_LOAN parameter must be sent "YES".
  {"ISBANK_LOAN":"YES", "ISBANK_LOAN.maximum_term":"5"}
• KUVEYTTURK_LOAN - The following fields must be used for Kuveytturk shopping credit and all fields are required. KUVEYTTURK_LOAN parameter must be sent "YES".
  {"KUVEYTTURK_LOAN":"YES", "KUVEYTTURK_LOAN.softDescriptor":"Finansman islem bilgisi", "KUVEYTTURK_LOAN.commissionAmount":"0", "KUVEYTTURK_LOAN.orderItemCount":"1", "KUVEYTTURK_LOAN.categoryCode":"1101", "KUVEYTTURK_LOAN.unitPrice":"100", "KUVEYTTURK_LOAN.count":"1", "KUVEYTTURK_LOAN.channel":"WM"}
• NKOLAY_LOAN - The following fields must be used for NKolay shopping credit and all fields are required. NKolay parameter must be sent "YES".
  {"NKOLAY_LOAN":"YES", "NKolay.identityNumber":"11920171664", "NKolay.products": {"NKolay.name": "phone","NKolay.categoryId": 1,"NKolay.categoryName": "Cep Telefonu", "NKolay.quantity": 1,"NKolay.totalPrice": 8000.0}
• FIBABANKA_LOAN - The following fields must be used for Fibabanka shopping credit and all fields are required. FIBABANKA_LOAN parameter must be sent "YES".
  {"FIBABANKA_LOAN":"YES", "FIBABANKA_LOAN.productType":"5"}

SHIPTOPHONE:

string, optional Max length: 32 Phone number of shipment information

BILLTOPHONE:

string, optional Max length: 32 Phone number of billment information

BUYERTYPE:

string, optional Max length: 1 Default value: 'A' Member/Anonymous user flag See all possible values ()

SELLERID:

string, optional Max length: 1024 Unique value per seller.

COMMISSIONAMOUNT:

string, optional Max length: 512 description

SELLERPAYMENTAMOUNT:

string, optional Max length: 512 description

DISCOUNTAMOUNT:

decimal, optional Max length: 30 The amount to be discounted from ORDERITEMS total amount. When provided, the AMOUNT field should be equal to the subtraction of ORDERITEMS total amount with DISCOUNTAMOUNT. (AMOUNT = ORDERITEMS - DISCOUNTAMOUNT)

FORGROUP:

string, optional Max length: 3 Default value: 'YES' Specifies the for group featured usages. Available values are 'yes' and 'no'.

NOTIFICATIONURL:

string, optional Max length: 255 description

THREATMETRIXSESSIONID:

string, optional Max length: 128 description

TMXSESSIONQUERYINPUT:

string, optional Max length: 100000 Session query input that can be retrieved from Threat Metrix. A request needs to be sent at https://h-api.online-metrix.net/api/session-query, with those parameters: org_id (provided by Paratika), api_key (provided by Paratika), session_id (unique identifier, stored in the session, can be retrieved from QUERYSESSION), service_type (value should be 'session-policy'), event_type (value should be 'payment'), policy (provided by Paratika). e.g. https://h-api.online-metrix.net/api/session-query?org_id=[org_id]&api_key=[api_key]&session_id=[session_id]&service_type=session-policy&event_type=payment&policy=[policy]

CUSTOMERTYPE:

string, optional Max length: 32 description See all possible values (5)

MERCHANTNOTE:

string, optional Max length: 50 If the merchant has a note regarding payment, it should be written to this parameter.

Postauth

PostAuth is a credit card transaction that captures the funds on the customer’s card for a specified amount reserved earlier using PreAuth transaction. If you enter a larger total in the PostAuth transaction than what was specified for the PreAuth transaction, the PostAuth transaction may be declined. If you enter a smaller amount than was pre-authorized, an adjustment is made to the authorization to capture only the smaller amount of funds on the customer’s card for the transaction. PostAuth transactions must be completed within certain amount of time after the the pre-authorization is obtained. This time period varies between 3 days and 75 days depending on the card issuer’s policy.

Request parameters:

ACTION:

POSTAUTH, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

PGTRANID:

string, conditional Max length: 64 Transaction ID given by payment gateway.

MERCHANTPAYMENTID:

string, conditional Max length: 128 Unique Payment ID given by Merchant.

AMOUNT:

decimal, optional Max length: 30 Default value: '0' Amount of payment / transaction. Please note that, this amount is tax included, Paratika doesn't consider any other tax calculation.

ORDERITEMS:

string, optional Max length: 100000 Order items as array in JSON Format. Order items should be URL encoded. Please see the request samples for valid JSON data format.

Void

A void transaction cancels any transaction, apart from itself. Void cannot be voided. You will get success response for void transactions only if they are not included in the end-of-day settlement process taking place at the issuer’s side. This is the process runs at the end of business day to settle all transactions. This is when the actual funds are transferred from the cardholder’s credit card to merchant’s bank account. So, for example; if you would like to void a sale or postauth transaction that is already processed as part of the end-of-day settlement, then you will get a failed error code for the void request. In this case, you will need to use refund as alternative to void action.

Request parameters:

ACTION:

VOID, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

PGTRANID:

string, conditional Max length: 64 Transaction ID given by payment gateway.

MERCHANTPAYMENTID:

string, conditional Max length: 128 Unique Payment ID given by Merchant.

EXTRA:

string, optional Max length: 1024 Extra Parameter is a custom parameter that is used to pass additional parameters to session token. This parameter is expected to be in JSON(URL-ENCODED) format. If they are mispelled, they will be ignored! Supported parameters are: CardHolderAgreementMode(value: NONE/SHOW/SHOWCHECKED/SHOWCHECKEDDISABLED), AlwaysSaveCard(value: true/false), BuyerType (value: L for logged in customer; A for anonymous, F for the first shopping with memebership. OR it can be 0, 1, 2 for those cases), IsbankBolumKodu(string), IframeDomainUrl indicates from which URL address payment will be proceesed., PREAUTH=YES parameter indicates that payment will be processed as pre-authorization even if is started as sale., IGNORECUSTOMERCOMMISSION(values : YES/NO).
EXTRA: {"AlwaysSaveCard": "true", "BuyerType": "L", "IsbankBolumKodu": 12, "CardHolderAgreementMode": "SHOWCHECKED", "IGNORECUSTOMERCOMMISSION" : "YES"}

Other bank parameters

• MAXIMUMMOBIL - include Maximum Mobil payment system name like below to have Maximum Mobil tab on Default HPP
  {"MaximumMobilPaymentSystem":"PaymentSystemName"}
• GIROGATE payment methods. If one of payment methods is sent as "Yes", authentication will be done using GiroGate payment methods. Possible values: YES/NO.
  • SOFORT: {"SOFORT": "YES"}
  • SAFETYPAY: {"SAFETYPAY": "YES"}
  • QIWI: {"QIWI": "YES"}
  • GIROPAY: {"GIROPAY": "YES"}
  • IDEAL: {"IDEAL": "YES"}
  • FINNISHONLINEBANKING: {"FINNISHONLINEBANKING": "YES"}
  • BANCONTACT: {"BANCONTACT": "YES"}
  • ALIPAY: {"ALIPAY": "YES"}
  • MULTIBANCO: {"MULTIBANCO": "YES"}
  • TRUSTPAY: {"TRUSTPAY": "YES"}
  • EPS: {"EPS": "YES"}
  • MYBANK: {"MYBANK": "YES"}
  • P24: {"P24": "YES"}
  • BOLETO: {"BOLETO": "YES"}
  • ELO: {"ELO": "YES"}
  • SEPA: {"SEPA": "YES"}
  • UPOP: {"UPOP": "YES"}
• ISBANK - include in extra like below to send agriculture template info to Isbank when doing imece card operations.
  {"IMCKOD":"imckod", "FDONEM":"fdonem"}
• SEKERBANK - can also take these extra parameters:
  {"HASATKARTSATIS", "VADEKODU", "VADEADEDI", "URUNKODU", "PLASIYERNO", "FATURANO"}

• ISBANK_LOAN - The following fields must be used for Kuveytturk shopping credit and all fields are required. ISBANK_LOAN parameter must be sent "YES".
  {"ISBANK_LOAN":"YES", "ISBANK_LOAN.maximum_term":"5"}
• KUVEYTTURK_LOAN - The following fields must be used for Kuveytturk shopping credit and all fields are required. KUVEYTTURK_LOAN parameter must be sent "YES".
  {"KUVEYTTURK_LOAN":"YES", "KUVEYTTURK_LOAN.softDescriptor":"Finansman islem bilgisi", "KUVEYTTURK_LOAN.commissionAmount":"0", "KUVEYTTURK_LOAN.orderItemCount":"1", "KUVEYTTURK_LOAN.categoryCode":"1101", "KUVEYTTURK_LOAN.unitPrice":"100", "KUVEYTTURK_LOAN.count":"1", "KUVEYTTURK_LOAN.channel":"WM"}
• NKOLAY_LOAN - The following fields must be used for NKolay shopping credit and all fields are required. NKolay parameter must be sent "YES".
  {"NKOLAY_LOAN":"YES", "NKolay.identityNumber":"11920171664", "NKolay.products": {"NKolay.name": "phone","NKolay.categoryId": 1,"NKolay.categoryName": "Cep Telefonu", "NKolay.quantity": 1,"NKolay.totalPrice": 8000.0}
• FIBABANKA_LOAN - The following fields must be used for Fibabanka shopping credit and all fields are required. FIBABANKA_LOAN parameter must be sent "YES".
  {"FIBABANKA_LOAN":"YES", "FIBABANKA_LOAN.productType":"5"}

Refund

A Refund transaction returns funds to a customer’s credit card for an existing order on the system. To perform a refund, you need the transaction number, which you can find in your reports. If you perform a return of the full payment amount, the payment amount will be reset to the original amount.Refunds can be made for transactions that have entered the end of the day, if the transaction has not entered the end of the day, the transaction should be canceled.

Request parameters:

ACTION:

REFUND, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

AMOUNT:

decimal, optional Max length: 30 Amount of payment / transaction. Please note that, this amount is tax included, Paratika doesn't consider any other tax calculation.

CURRENCY:

string, optional Max length: 3 ISO Alpha transaction currency code like TRY, EUR, USD, GBP. Please check https://en.wikipedia.org/wiki/ISO_4217#Position_of_ISO_4217_code_in_amounts for details. See all possible values (33)

PGTRANID:

string, conditional Max length: 64 Transaction ID given by payment gateway.

MERCHANTPAYMENTID:

string, conditional Max length: 128 Unique Payment ID given by Merchant.

NOTIFICATIONURL:

string, optional Max length: 255 description

ORDERITEMS:

string, optional Max length: 100000 Order items as array in JSON Format. Order items should be URL encoded. Please see the request samples for valid JSON data format.

REFLECTCOMMISSION:

string, optional Max length: 3 Default value: 'NO' description See all possible values (2)

EXTRA:

string, optional Max length: 1024 Extra Parameter is a custom parameter that is used to pass additional parameters to session token. This parameter is expected to be in JSON(URL-ENCODED) format. If they are mispelled, they will be ignored! Supported parameters are: CardHolderAgreementMode(value: NONE/SHOW/SHOWCHECKED/SHOWCHECKEDDISABLED), AlwaysSaveCard(value: true/false), BuyerType (value: L for logged in customer; A for anonymous, F for the first shopping with memebership. OR it can be 0, 1, 2 for those cases), IsbankBolumKodu(string), IframeDomainUrl indicates from which URL address payment will be proceesed., PREAUTH=YES parameter indicates that payment will be processed as pre-authorization even if is started as sale., IGNORECUSTOMERCOMMISSION(values : YES/NO).
EXTRA: {"AlwaysSaveCard": "true", "BuyerType": "L", "IsbankBolumKodu": 12, "CardHolderAgreementMode": "SHOWCHECKED", "IGNORECUSTOMERCOMMISSION" : "YES"}

Other bank parameters

• MAXIMUMMOBIL - include Maximum Mobil payment system name like below to have Maximum Mobil tab on Default HPP
  {"MaximumMobilPaymentSystem":"PaymentSystemName"}
• GIROGATE payment methods. If one of payment methods is sent as "Yes", authentication will be done using GiroGate payment methods. Possible values: YES/NO.
  • SOFORT: {"SOFORT": "YES"}
  • SAFETYPAY: {"SAFETYPAY": "YES"}
  • QIWI: {"QIWI": "YES"}
  • GIROPAY: {"GIROPAY": "YES"}
  • IDEAL: {"IDEAL": "YES"}
  • FINNISHONLINEBANKING: {"FINNISHONLINEBANKING": "YES"}
  • BANCONTACT: {"BANCONTACT": "YES"}
  • ALIPAY: {"ALIPAY": "YES"}
  • MULTIBANCO: {"MULTIBANCO": "YES"}
  • TRUSTPAY: {"TRUSTPAY": "YES"}
  • EPS: {"EPS": "YES"}
  • MYBANK: {"MYBANK": "YES"}
  • P24: {"P24": "YES"}
  • BOLETO: {"BOLETO": "YES"}
  • ELO: {"ELO": "YES"}
  • SEPA: {"SEPA": "YES"}
  • UPOP: {"UPOP": "YES"}
• ISBANK - include in extra like below to send agriculture template info to Isbank when doing imece card operations.
  {"IMCKOD":"imckod", "FDONEM":"fdonem"}
• SEKERBANK - can also take these extra parameters:
  {"HASATKARTSATIS", "VADEKODU", "VADEADEDI", "URUNKODU", "PLASIYERNO", "FATURANO"}

• ISBANK_LOAN - The following fields must be used for Kuveytturk shopping credit and all fields are required. ISBANK_LOAN parameter must be sent "YES".
  {"ISBANK_LOAN":"YES", "ISBANK_LOAN.maximum_term":"5"}
• KUVEYTTURK_LOAN - The following fields must be used for Kuveytturk shopping credit and all fields are required. KUVEYTTURK_LOAN parameter must be sent "YES".
  {"KUVEYTTURK_LOAN":"YES", "KUVEYTTURK_LOAN.softDescriptor":"Finansman islem bilgisi", "KUVEYTTURK_LOAN.commissionAmount":"0", "KUVEYTTURK_LOAN.orderItemCount":"1", "KUVEYTTURK_LOAN.categoryCode":"1101", "KUVEYTTURK_LOAN.unitPrice":"100", "KUVEYTTURK_LOAN.count":"1", "KUVEYTTURK_LOAN.channel":"WM"}
• NKOLAY_LOAN - The following fields must be used for NKolay shopping credit and all fields are required. NKolay parameter must be sent "YES".
  {"NKOLAY_LOAN":"YES", "NKolay.identityNumber":"11920171664", "NKolay.products": {"NKolay.name": "phone","NKolay.categoryId": 1,"NKolay.categoryName": "Cep Telefonu", "NKolay.quantity": 1,"NKolay.totalPrice": 8000.0}
• FIBABANKA_LOAN - The following fields must be used for Fibabanka shopping credit and all fields are required. FIBABANKA_LOAN parameter must be sent "YES".
  {"FIBABANKA_LOAN":"YES", "FIBABANKA_LOAN.productType":"5"}

Session

Session Token

Session token can be used both for browser based integrations and API integrations. System return a key which has an access to API in a limited time (default 7 days, it is configurable). Generally session token action expect that each session should have an unique merchantPaymentId parameter. In case when you redirect your customer with same parameter set you can use same session token unless it is obeying the below criteria :

Threat Metrix Fraud Tool

In order to integrate ThreatMetrix device intelligence with your website, you need to insert profiling tags on web pages where you will profile visitor devices and check page integrity. To do that, you will need:

• UNIQUE_SESSION_ID, you can get it from making a QUERYSESSION, in response you will have this value stored in threatMetrixSessionId,
• ORG_ID, contact PF to get this information

				
<!--
    NOTE
    * Replace UNIQUE_SESSION_ID with a uniquely generated handle
    * PAGEID is only needed for TDCloud, replace PAGEID with an unique ID for that page, if omitted, default is 1 for production
    * For production replace h.online-metrix.net with a local URL and configure your web server to redirect to h.online-metrix.net. When using whitewolf, if a web server is configured, HOST should be the host of your web server, if not configured the HOST should be h.online-metrix.net
    * Replace PF_HOST with the appropriate host
        Test:       test/paratika
        Production: prod/paratika
-->
<script type="text/javascript" src="https://PF_HOST/paratika/static/external/whitewolf-v3.js"></script>
<script type="text/javascript">
	whitewolf.run(HOST, ORG_ID, UNIQUE_SESSION_ID);
</script>
<noscript>
    <iframe
        style="width: 100px; height: 100px; border: 0; position: absolute; top: -5000px;"
        src="https://h.online-metrix.net/tags?org_id=ORG_ID&session_id=UNIQUE_SESSION_ID&pageid=PAGEID">
    </iframe>
</noscript>
				
			

Request parameters:

ACTION:

SESSIONTOKEN, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

SESSIONTYPE:

string, required Max length: 30 Session type is a session for payment or wallet (PAYMENTSESSION or WALLETSESSION) See all possible values (3)

RETURNURL:

string, required Max length: 256 Return URL after successful / failed payment.

MERCHANTPAYMENTID:

string, conditional Max length: 128 Unique Payment ID given by Merchant.

AMOUNT:

decimal, conditional Max length: 30 Amount of payment / transaction. Please note that, this amount is tax included, Paratika doesn't consider any other tax calculation.

CURRENCY:

string, conditional Max length: 3 ISO Alpha transaction currency code like TRY, EUR, USD, GBP. Please check https://en.wikipedia.org/wiki/ISO_4217#Position_of_ISO_4217_code_in_amounts for details. See all possible values (33)

CUSTOMER:

string, conditional Max length: 128 The Merchant System ID for customer. It must be unique within a Merchant.

CUSTOMEREMAIL:

string, conditional Max length: 64 Customer e-mail. This information should be passed correctly if the customer information services are used.

CUSTOMERNAME:

string, conditional Max length: 128 Name of the Customer. This information should be passed correctly if the customer information services are used.

CUSTOMERPHONE:

string, conditional Max length: 64 Customer phone / mobile number. This information should be passed correctly if the customer information services are used.

CUSTOMERBIRTHDAY:

date, optional Max length: 16 Format: [dd-MM-yyyy] Customer Birthday.

CUSTOMERIP:

string, optional Max length: 39 Customer IP Address

CUSTOMERUSERAGENT:

string, optional Max length: 512 Customer User Agent

ORDERITEMS:

string, conditional Max length: 100000 Order items as array in JSON Format. Order items should be URL encoded. Please see the request samples for valid JSON data format.

TCKN:

string, optional Max length: 16 Customer Identity Number.

SESSIONEXPIRY:

string, optional Max length: 5 Default value: '168h' Session expiry time, default value is 7 days ( 7x24 hours ).

LANGUAGE:

string, optional Max length: 2 Default value: 'tr' Locale of pages displayed during payment.

BILLTOADDRESSLINE:

string, optional Max length: 255 Bill To Address Line

BILLTOCITY:

string, optional Max length: 32 Bill To City

BILLTOPOSTALCODE:

string, optional Max length: 16 Bill To Postal Code

BILLTOCOUNTRY:

string, optional Max length: 32 Bill To Country
An alpha-3 code in ISO 3166-1 standard should be sent.

SHIPTOADDRESSLINE:

string, optional Max length: 255 Ship To Address Line

SHIPTOCITY:

string, optional Max length: 32 Ship To City

SHIPTOPOSTALCODE:

string, optional Max length: 32 Ship To Postal Code

SHIPTOCOUNTRY:

string, optional Max length: 32 Ship To Country
An alpha-3 code in ISO 3166-1 standard should be sent.

FASTSHIPPING:

string, optional Max length: 3 Default value: 'NO' This param indicates that the shipping option is selected as fast, urgent, quick etc. If fast shipment is the option, then the merchant should send this parameter with "yes" value. See all possible values (2)

EXTRA:

string, optional Max length: 1024 Extra Parameter is a custom parameter that is used to pass additional parameters to session token. This parameter is expected to be in JSON(URL-ENCODED) format. If they are mispelled, they will be ignored! Supported parameters are: CardHolderAgreementMode(value: NONE/SHOW/SHOWCHECKED/SHOWCHECKEDDISABLED), AlwaysSaveCard(value: true/false), BuyerType (value: L for logged in customer; A for anonymous, F for the first shopping with memebership. OR it can be 0, 1, 2 for those cases), IsbankBolumKodu(string), IframeDomainUrl indicates from which URL address payment will be proceesed., PREAUTH=YES parameter indicates that payment will be processed as pre-authorization even if is started as sale., IGNORECUSTOMERCOMMISSION(values : YES/NO).
EXTRA: {"AlwaysSaveCard": "true", "BuyerType": "L", "IsbankBolumKodu": 12, "CardHolderAgreementMode": "SHOWCHECKED", "IGNORECUSTOMERCOMMISSION" : "YES"}

Other bank parameters

• MAXIMUMMOBIL - include Maximum Mobil payment system name like below to have Maximum Mobil tab on Default HPP
  {"MaximumMobilPaymentSystem":"PaymentSystemName"}
• GIROGATE payment methods. If one of payment methods is sent as "Yes", authentication will be done using GiroGate payment methods. Possible values: YES/NO.
  • SOFORT: {"SOFORT": "YES"}
  • SAFETYPAY: {"SAFETYPAY": "YES"}
  • QIWI: {"QIWI": "YES"}
  • GIROPAY: {"GIROPAY": "YES"}
  • IDEAL: {"IDEAL": "YES"}
  • FINNISHONLINEBANKING: {"FINNISHONLINEBANKING": "YES"}
  • BANCONTACT: {"BANCONTACT": "YES"}
  • ALIPAY: {"ALIPAY": "YES"}
  • MULTIBANCO: {"MULTIBANCO": "YES"}
  • TRUSTPAY: {"TRUSTPAY": "YES"}
  • EPS: {"EPS": "YES"}
  • MYBANK: {"MYBANK": "YES"}
  • P24: {"P24": "YES"}
  • BOLETO: {"BOLETO": "YES"}
  • ELO: {"ELO": "YES"}
  • SEPA: {"SEPA": "YES"}
  • UPOP: {"UPOP": "YES"}
• ISBANK - include in extra like below to send agriculture template info to Isbank when doing imece card operations.
  {"IMCKOD":"imckod", "FDONEM":"fdonem"}
• SEKERBANK - can also take these extra parameters:
  {"HASATKARTSATIS", "VADEKODU", "VADEADEDI", "URUNKODU", "PLASIYERNO", "FATURANO"}

• ISBANK_LOAN - The following fields must be used for Kuveytturk shopping credit and all fields are required. ISBANK_LOAN parameter must be sent "YES".
  {"ISBANK_LOAN":"YES", "ISBANK_LOAN.maximum_term":"5"}
• KUVEYTTURK_LOAN - The following fields must be used for Kuveytturk shopping credit and all fields are required. KUVEYTTURK_LOAN parameter must be sent "YES".
  {"KUVEYTTURK_LOAN":"YES", "KUVEYTTURK_LOAN.softDescriptor":"Finansman islem bilgisi", "KUVEYTTURK_LOAN.commissionAmount":"0", "KUVEYTTURK_LOAN.orderItemCount":"1", "KUVEYTTURK_LOAN.categoryCode":"1101", "KUVEYTTURK_LOAN.unitPrice":"100", "KUVEYTTURK_LOAN.count":"1", "KUVEYTTURK_LOAN.channel":"WM"}
• NKOLAY_LOAN - The following fields must be used for NKolay shopping credit and all fields are required. NKolay parameter must be sent "YES".
  {"NKOLAY_LOAN":"YES", "NKolay.identityNumber":"11920171664", "NKolay.products": {"NKolay.name": "phone","NKolay.categoryId": 1,"NKolay.categoryName": "Cep Telefonu", "NKolay.quantity": 1,"NKolay.totalPrice": 8000.0}
• FIBABANKA_LOAN - The following fields must be used for Fibabanka shopping credit and all fields are required. FIBABANKA_LOAN parameter must be sent "YES".
  {"FIBABANKA_LOAN":"YES", "FIBABANKA_LOAN.productType":"5"}

SHIPTOPHONE:

string, optional Max length: 32 Phone number of shipment information

BILLTOPHONE:

string, optional Max length: 32 Phone number of billment information

DISCOUNTAMOUNT:

decimal, optional Max length: 30 The amount to be discounted from ORDERITEMS total amount. When provided, the AMOUNT field should be equal to the subtraction of ORDERITEMS total amount with DISCOUNTAMOUNT. (AMOUNT = ORDERITEMS - DISCOUNTAMOUNT)

SELLERID:

string, optional Max length: 1024 Unique value per seller.

COMMISSIONAMOUNT:

string, optional Max length: 512 description

SELLERPAYMENTAMOUNT:

string, optional Max length: 512 description

TOTALSELLERCOMMISSIONAMOUNT:

decimal, optional Max length: 30 description

TOTALSELLERPAYMENTAMOUNT:

decimal, optional Max length: 30 description

THREATMETRIXSESSIONID:

string, optional Max length: 128 description

TMXSESSIONQUERYINPUT:

string, optional Max length: 100000 Session query input that can be retrieved from Threat Metrix. A request needs to be sent at https://h-api.online-metrix.net/api/session-query, with those parameters: org_id (provided by Paratika), api_key (provided by Paratika), session_id (unique identifier, stored in the session, can be retrieved from QUERYSESSION), service_type (value should be 'session-policy'), event_type (value should be 'payment'), policy (provided by Paratika). e.g. https://h-api.online-metrix.net/api/session-query?org_id=[org_id]&api_key=[api_key]&session_id=[session_id]&service_type=session-policy&event_type=payment&policy=[policy]

CUSTOMERTYPE:

string, optional Max length: 32 description See all possible values (5)

CHECKOUTPAGEURL:

string, optional Max length: 512 description

MERCHANTNOTE:

string, optional Max length: 50 If the merchant has a note regarding payment, it should be written to this parameter.

CARDPANTYPE:

string, optional Max length: 32 The Card Pan Type parameter is used to determine the type of card we will use in the transaction See all possible values (1)

ISSPLITPAYMENTTRANSACTION:

string, optional Max length: 3 Default value: 'NO' description See all possible values (2)

ALLOWEDINSTALLMENTS:

string, optional Max length: 64 description

ALLOWEDDEFERRALMONTHCOUNTS:

string, optional Max length: 64 description

Pay by Link Payment Actions

Add Pay by Link Payment

See Description

Note: If Pay By Link Payment is created with existing customer just parameter CUSTOMER should be sent, otherwise if it's new customer parameters CUSTOMERNAME, CUSTOMERPHONE and CUSTOMEREMAIL are required and should be sent on request.

Request parameters:

ACTION:

PAYBYLINKPAYMENT, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONEXPIRY:

string, required Max length: 10 Default value: '168h' Session expiry time, default value is 7 days ( 7x24 hours ).

MERCHANTPAYMENTID:

string, required Max length: 128 Unique Payment ID given by Merchant.

AMOUNT:

decimal, required Max length: 30 Amount of payment / transaction. Please note that, this amount is tax included, Paratika doesn't consider any other tax calculation.

CURRENCY:

string, required Max length: 3 ISO Alpha transaction currency code like TRY, EUR, USD, GBP. Please check https://en.wikipedia.org/wiki/ISO_4217#Position_of_ISO_4217_code_in_amounts for details. See all possible values (33)

CUSTOMER:

string, required Max length: 128 The Merchant System ID for customer. It must be unique within a Merchant.

RETURNURL:

string, optional Max length: 512 Return URL after successful / failed payment.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

CUSTOMEREMAIL:

string, conditional Max length: 64 Customer e-mail. This information should be passed correctly if the customer information services are used.

CUSTOMERNAME:

string, conditional Max length: 128 Name of the Customer. This information should be passed correctly if the customer information services are used.

CUSTOMERPHONE:

string, optional Max length: 64 Customer phone / mobile number. This information should be passed correctly if the customer information services are used.

TCKN:

string, optional Max length: 11 Customer Identity Number.

LANGUAGE:

string, optional Max length: 2 Default value: 'tr' Locale of pages displayed during payment.

ORDERITEMS:

string, optional Max length: 100000 Order items as array in JSON Format. Order items should be URL encoded. Please see the request samples for valid JSON data format.

NOTIFICATIONCHANNELS:

string, optional Max length: 16 The NOTIFICATIONCHANNELS parameter is used to specify notification channels. If more than one channel is to be notified, the channel must be combined (with a comma). Ex: EMAIL,SMS

BILLTOADDRESSLINE:

string, optional Max length: 255 Bill To Address Line

BILLTOCITY:

string, optional Max length: 32 Bill To City

BILLTOPOSTALCODE:

string, optional Max length: 16 Bill To Postal Code

BILLTOCOUNTRY:

string, optional Max length: 32 Bill To Country
An alpha-3 code in ISO 3166-1 standard should be sent.

BILLTOPHONE:

string, optional Max length: 32 Phone number of billment information

SHIPTOADDRESSLINE:

string, optional Max length: 255 Ship To Address Line

SHIPTOCITY:

string, optional Max length: 32 Ship To City

SHIPTOPOSTALCODE:

string, optional Max length: 32 Ship To Postal Code

SHIPTOCOUNTRY:

string, optional Max length: 32 Ship To Country
An alpha-3 code in ISO 3166-1 standard should be sent.

SHIPTOPHONE:

string, optional Max length: 32 Phone number of shipment information

EXTRA:

string, optional Max length: 1024 Extra Parameter is a custom parameter that is used to pass additional parameters to session token. This parameter is expected to be in JSON(URL-ENCODED) format. If they are mispelled, they will be ignored! Supported parameters are: CardHolderAgreementMode(value: NONE/SHOW/SHOWCHECKED/SHOWCHECKEDDISABLED), AlwaysSaveCard(value: true/false), BuyerType (value: L for logged in customer; A for anonymous, F for the first shopping with memebership. OR it can be 0, 1, 2 for those cases), IsbankBolumKodu(string), IframeDomainUrl indicates from which URL address payment will be proceesed., PREAUTH=YES parameter indicates that payment will be processed as pre-authorization even if is started as sale., IGNORECUSTOMERCOMMISSION(values : YES/NO).
EXTRA: {"AlwaysSaveCard": "true", "BuyerType": "L", "IsbankBolumKodu": 12, "CardHolderAgreementMode": "SHOWCHECKED", "IGNORECUSTOMERCOMMISSION" : "YES"}

Other bank parameters

• MAXIMUMMOBIL - include Maximum Mobil payment system name like below to have Maximum Mobil tab on Default HPP
  {"MaximumMobilPaymentSystem":"PaymentSystemName"}
• GIROGATE payment methods. If one of payment methods is sent as "Yes", authentication will be done using GiroGate payment methods. Possible values: YES/NO.
  • SOFORT: {"SOFORT": "YES"}
  • SAFETYPAY: {"SAFETYPAY": "YES"}
  • QIWI: {"QIWI": "YES"}
  • GIROPAY: {"GIROPAY": "YES"}
  • IDEAL: {"IDEAL": "YES"}
  • FINNISHONLINEBANKING: {"FINNISHONLINEBANKING": "YES"}
  • BANCONTACT: {"BANCONTACT": "YES"}
  • ALIPAY: {"ALIPAY": "YES"}
  • MULTIBANCO: {"MULTIBANCO": "YES"}
  • TRUSTPAY: {"TRUSTPAY": "YES"}
  • EPS: {"EPS": "YES"}
  • MYBANK: {"MYBANK": "YES"}
  • P24: {"P24": "YES"}
  • BOLETO: {"BOLETO": "YES"}
  • ELO: {"ELO": "YES"}
  • SEPA: {"SEPA": "YES"}
  • UPOP: {"UPOP": "YES"}
• ISBANK - include in extra like below to send agriculture template info to Isbank when doing imece card operations.
  {"IMCKOD":"imckod", "FDONEM":"fdonem"}
• SEKERBANK - can also take these extra parameters:
  {"HASATKARTSATIS", "VADEKODU", "VADEADEDI", "URUNKODU", "PLASIYERNO", "FATURANO"}

• ISBANK_LOAN - The following fields must be used for Kuveytturk shopping credit and all fields are required. ISBANK_LOAN parameter must be sent "YES".
  {"ISBANK_LOAN":"YES", "ISBANK_LOAN.maximum_term":"5"}
• KUVEYTTURK_LOAN - The following fields must be used for Kuveytturk shopping credit and all fields are required. KUVEYTTURK_LOAN parameter must be sent "YES".
  {"KUVEYTTURK_LOAN":"YES", "KUVEYTTURK_LOAN.softDescriptor":"Finansman islem bilgisi", "KUVEYTTURK_LOAN.commissionAmount":"0", "KUVEYTTURK_LOAN.orderItemCount":"1", "KUVEYTTURK_LOAN.categoryCode":"1101", "KUVEYTTURK_LOAN.unitPrice":"100", "KUVEYTTURK_LOAN.count":"1", "KUVEYTTURK_LOAN.channel":"WM"}
• NKOLAY_LOAN - The following fields must be used for NKolay shopping credit and all fields are required. NKolay parameter must be sent "YES".
  {"NKOLAY_LOAN":"YES", "NKolay.identityNumber":"11920171664", "NKolay.products": {"NKolay.name": "phone","NKolay.categoryId": 1,"NKolay.categoryName": "Cep Telefonu", "NKolay.quantity": 1,"NKolay.totalPrice": 8000.0}
• FIBABANKA_LOAN - The following fields must be used for Fibabanka shopping credit and all fields are required. FIBABANKA_LOAN parameter must be sent "YES".
  {"FIBABANKA_LOAN":"YES", "FIBABANKA_LOAN.productType":"5"}

MERCHANTNOTE:

string, optional Max length: 50 If the merchant has a note regarding payment, it should be written to this parameter.

INSTALLMENTSUPPORT:

string, optional Max length: 10000 description

Cancel Pay by Link Payment

The PAYBYLINKPAYMENTCANCEL action is used for cancelling a Pay By Link Payment

Request parameters:

ACTION:

PAYBYLINKPAYMENTCANCEL, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

PAYBYLINKTOKEN:

string, required Max length: 48 description

Resend Pay by Link Payment

The PAYBYLINKPAYMENTRESEND action is used for resending a remainder email to Card Holder to complete the payment

Request parameters:

ACTION:

PAYBYLINKPAYMENTRESEND, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

PAYBYLINKTOKEN:

string, required Max length: 48 description

NOTIFICATIONCHANNELS:

string, optional Max length: 16 The NOTIFICATIONCHANNELS parameter is used to specify notification channels. If more than one channel is to be notified, the channel must be combined (with a comma). Ex: EMAIL,SMS

Recurring Plan Actions

Add Recurring Plan

The RECURRINGPLAN action is a group of payments which will be executed separately in specified / scheduled time with defined amount(s).

Request parameters:

ACTION:

RECURRINGPLANADD, required Max length: 128 Core parameter which specifies the main action for the API call.

INSTANTPAYMENT:

string, optional Max length: 3 Default value: 'NO' description See all possible values (2)

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

CARDTOKEN:

string, conditional Max length: 64 Secure alphanumeric value replacing card number & expiry date. Required when none of the other card information are provided.

CARDPAN:

string, conditional Max length: 19 PAN (Primary account number), card number. Please check https://en.wikipedia.org/wiki/Bank_card_number for details.

CARDEXPIRY:

string, conditional Max length: 7 Expiry date of the card. Format should be [mm.yy].

NAMEONCARD:

string, conditional Max length: 64 Name on the card.

CARDSAVENAME:

string, optional Max length: 64 Given name for the saved card.

CUSTOMER:

string, conditional Max length: 128 The Merchant System ID for customer. It must be unique within a Merchant.

CUSTOMERNAME:

string, optional Max length: 128 Name of the Customer. This information should be passed correctly if the customer information services are used.

CUSTOMEREMAIL:

string, required Max length: 64 Customer e-mail. This information should be passed correctly if the customer information services are used.

CUSTOMERPHONE:

string, optional Max length: 64 Customer phone / mobile number. This information should be passed correctly if the customer information services are used.

RECURRINGPLANCODE:

string, required Max length: 16 Unique code of a recurring plan.

FIRSTAMOUNT:

decimal, optional Max length: 30 Amount of the first payment of recurring plan.

RECURRINGAMOUNT:

decimal, required Max length: 30 Amount of the recurring payments.

RECURRENCECOUNT:

decimal, required Max length: 2 Default value: '1' Recurrence count of a recurring plan.

FREQUENCY:

string, required Max length: 4 Frequency of a payment. D for day, M for month, Y should be used for years. (Ex. 5D, 3M, 1Y)

STARTDATE:

date, optional Max length: 16 Format: [dd-MM-yyyy] Start date of the transaction query.

CURRENCY:

string, conditional Max length: 3 ISO Alpha transaction currency code like TRY, EUR, USD, GBP. Please check https://en.wikipedia.org/wiki/ISO_4217#Position_of_ISO_4217_code_in_amounts for details. See all possible values (33)

PAYMENTSYSTEM:

string, optional Max length: 128 Name of the payment system (bank payment gateway / vPOS account). Specified name should match the one given in Paratika. If not provided, Paratika smart switch feature will be used.

FORGROUP:

string, optional Max length: 3 Default value: 'YES' Specifies the for group featured usages. Available values are 'yes' and 'no'.

ORDERITEMS:

string, optional Max length: 100000 Order items as array in JSON Format. Order items should be URL encoded. Please see the request samples for valid JSON data format.

TOTALSELLERCOMMISSIONAMOUNT:

decimal, optional Max length: 30 description

TOTALSELLERPAYMENTAMOUNT:

decimal, optional Max length: 30 description

Edit Recurring Plan

Edit Recurring Plan

The RECURRINGPLANEDIT is an action that allows you to change some properties of Recurring Plans and Recurring Payments. You can change STATUS, CARD INFORMATION, RECURRING AMOUNT and PAYMENT SYSTEM of recurring plan and STATUS, START DATE and AMOUNT of a specific recurring payment.

Request parameters:

ACTION:

RECURRINGPLANEDIT, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

RECURRINGPLANCODE:

string, required Max length: 16 Unique code of a recurring plan.

RECURRINGSTATUS:

string, optional Max length: 16 Recurring Plan and Recurring Payment status.

RECURRINGAMOUNT:

decimal, optional Max length: 30 Amount of the recurring payments.

PAYMENTSYSTEM:

string, optional Max length: 128 Name of the payment system (bank payment gateway / vPOS account). Specified name should match the one given in Paratika. If not provided, Paratika smart switch feature will be used.

RECURRENCE:

decimal, optional Max length: 2 Recurring Payment order which will be edited.

STARTDATE:

date, optional Max length: 16 Format: [dd-MM-yyyy] Start date of the transaction query.

AMOUNT:

decimal, optional Max length: 30 Amount of payment / transaction. Please note that, this amount is tax included, Paratika doesn't consider any other tax calculation.

Recurring Plan Card Actions

Add Recurring Plan Card

RECURRINGPLANCARDADD action lets you to add card and relate it to recurring plan.

Request parameters:

ACTION:

RECURRINGPLANCARDADD, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

RECURRINGPLANCODE:

string, required Max length: 16 Unique code of a recurring plan.

CARDTOKEN:

string, conditional Max length: 64 Secure alphanumeric value replacing card number & expiry date. Required when none of the other card information are provided.

CARDPAN:

string, conditional Max length: 19 PAN (Primary account number), card number. Please check https://en.wikipedia.org/wiki/Bank_card_number for details.

CARDEXPIRY:

string, conditional Max length: 7 Expiry date of the card. Format should be [mm.yy].

NAMEONCARD:

string, conditional Max length: 64 Name on the card.

CARDSAVENAME:

string, optional Max length: 64 Given name for the saved card.

Delete RecurringPlan Card

RECURRINGPLANCARDDELETE action lets you to remove relation between card and recurring plan.

Request parameters:

ACTION:

RECURRINGPLANCARDDELETE, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

RECURRINGPLANCODE:

string, required Max length: 16 Unique code of a recurring plan.

CARDTOKEN:

string, required Max length: 64 Secure alphanumeric value replacing card number & expiry date. Required when none of the other card information are provided.

e-Wallet actions

Edit Card

The EWALLETEDITCARD request lets you edit the existing cards by providing their token value. The only fields that are allowed to be edited are the card’s expiry date and the saved card name.

Request parameters:

ACTION:

EWALLETEDITCARD, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

CARDTOKEN:

string, required Max length: 64 Secure alphanumeric value replacing card number & expiry date. Required when none of the other card information are provided.

CUSTOMER:

string, conditional Max length: 128 The Merchant System ID for customer. It must be unique within a Merchant.

CARDEXPIRY:

string, optional Max length: 7 Expiry date of the card. Format should be [mm.yy].

NAMEONCARD:

string, optional Max length: 64 Name on the card.

CARDSAVENAME:

string, optional Max length: 64 Given name for the saved card.

Delete Card

The EWALLETDELETECARD request allows you to remove customer cards from Paratika system. Once a card is removed it cannot be queried, edited or used for any kind of payment. The ewalletremove request can be sent to Paratika using the following fields:

Request parameters:

ACTION:

EWALLETDELETECARD, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

CARDTOKEN:

string, required Max length: 64 Secure alphanumeric value replacing card number & expiry date. Required when none of the other card information are provided.

Seller Actions

Add Seller

The SELLERADD action lets you add a seller. You should give the required parameters also optional parameters like TCKN.

Request parameters:

ACTION:

SELLERADD, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

SELLERID:

string, required Max length: 32 Unique value per seller.

NAME:

string, required Max length: 512 Name

LASTNAME:

string, required Max length: 512 description

EMAIL:

string, required Max length: 512 description

MOBILENUMBER:

string, required Max length: 64 description

TCKN:

string, conditional Max length: 11 Customer Identity Number.

VKN:

string, conditional Max length: 10 Tax identification number

IBAN:

string, required Max length: 34 description

IBANUSD:

string, optional Max length: 34 description

IBANEUR:

string, optional Max length: 34 description

IBANGBP:

string, optional Max length: 34 description

SELLERPAYMENTDAYS:

string, required Max length: 32 Seller payment days should be sent in index format, separated with semicolon. Indexes for days are as follow: Monday(0), Tuesday(1), Wednesday(2), Thursday(3), Friday(4). Example for seller payment days to be on Monday and Friday, the value of SELLERPAYMENTDAYS parameter should be sent as follow: 0;4;

ACCOUNTOWNERNAME:

string, conditional Max length: 512 description

ACCOUNTOWNERLASTNAME:

string, conditional Max length: 512 description

SELLERPAYMENTDUEDAY:

integer, optional Max length: 2 description

COMMERCIALTITLE:

string, conditional Max length: 512 description

STATUS:

string, optional Max length: 2 Status information. See all possible values (4)

COMMISSIONAPPLYTYPE:

string, conditional Max length: 3 Only CA parameter is available for COMMISSIONAPPLYTYPE. Other parameters are not applicable See all possible values (3)

COMMISSIONAPPLIERTYPE:

string, conditional Max length: 3 Only CA parameter is available for COMMISSIONAPPLIERTYPE. Other parameters are not applicable See all possible values (3)

COMMISSIONVALUE:

decimal, optional Max length: 30 description

ONBEHALFOFMERCHANT:

string, optional Max length: 16 description

SELLERURL:

string, optional Max length: 256 description

ISDEFAULT:

string, optional Max length: 3 Default value: 'NO' description

Edit Seller

The SELLEREDIT action lets you edit an existing seller. You should provide seller id and merchant and you can update name, last name, mobile number, email, TCKN and status.

Request parameters:

ACTION:

SELLEREDIT, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

SELLERID:

string, required Max length: 32 Unique value per seller.

NAME:

string, optional Max length: 512 Name

LASTNAME:

string, optional Max length: 512 description

EMAIL:

string, optional Max length: 512 description

MOBILENUMBER:

string, optional Max length: 64 description

STATUS:

string, optional Max length: 2 Status information. See all possible values (4)

TCKN:

string, conditional Max length: 11 Customer Identity Number.

VKN:

string, conditional Max length: 10 Tax identification number

IBAN:

string, required Max length: 34 description

IBANUSD:

string, optional Max length: 34 description

IBANEUR:

string, optional Max length: 34 description

IBANGBP:

string, optional Max length: 34 description

SELLERPAYMENTDAYS:

string, required Max length: 32 Seller payment days should be sent in index format, separated with semicolon. Indexes for days are as follow: Monday(0), Tuesday(1), Wednesday(2), Thursday(3), Friday(4). Example for seller payment days to be on Monday and Friday, the value of SELLERPAYMENTDAYS parameter should be sent as follow: 0;4;

ACCOUNTOWNERNAME:

string, conditional Max length: 512 description

ACCOUNTOWNERLASTNAME:

string, conditional Max length: 512 description

SELLERPAYMENTDUEDAY:

integer, optional Max length: 2 description

COMMERCIALTITLE:

string, conditional Max length: 512 description

COMMISSIONAPPLYTYPE:

string, conditional Max length: 3 Only CA parameter is available for COMMISSIONAPPLYTYPE. Other parameters are not applicable See all possible values (3)

COMMISSIONAPPLIERTYPE:

string, conditional Max length: 3 Only CA parameter is available for COMMISSIONAPPLIERTYPE. Other parameters are not applicable See all possible values (3)

COMMISSIONVALUE:

decimal, optional Max length: 30 description

ONBEHALFOFMERCHANT:

string, optional Max length: 16 description

SELLERURL:

string, optional Max length: 256 description

ISDEFAULT:

string, optional Max length: 3 Default value: 'NO' description

Seller Payment Date Update

Update the payment date of a seller transaction

Request parameters:

ACTION:

UPDATEPAYMENTDATE, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANTPAYMENTID:

string, conditional Max length: 128 Unique Payment ID given by Merchant.

PGTRANID:

string, conditional Max length: 64 Transaction ID given by payment gateway.

ORDERITEMS:

string, required Max length: 4096 Order items as array in JSON Format. Order items should be URL encoded. Please see the request samples for valid JSON data format.

Application Actions

Add Application

The APPLICATIONADD action lets you add a application. You should give the required parameters.

Request parameters:

ACTION:

APPLICATIONADD, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

APPLICATIONNAME:

string, required Max length: 256 description

APPLICATIONEMAIL:

string, required Max length: 64 description

APPLICATIONPHONE:

string, required Max length: 64 description

APPLICATIONWEBADDRESS:

string, optional Max length: 256 description

APPLICATIONTURNOVER:

string, required Max length: 256 description

APPLICATIONCOMPANYTYPE:

string, optional Max length: 16 description See all possible values (4)

APPLICATIONSHAREHOLDERS:

string, optional Max length: 100000 description

APPLICATIONMERCHANT:

string, optional Max length: 100000 description

APPLICATIONFINANCIALDATA:

string, optional Max length: 100000 description

APPLICATIONSALESUPPORTDATA:

string, optional Max length: 100000 description

APPLICATIONRISKMANAGEMENTDATA:

string, optional Max length: 100000 description

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

Edit Application

The APPLICATIONEDIT option lets you edit an application. You should give the required parameters name and email and send the optional parameters that you want to edit.

Request parameters:

ACTION:

APPLICATIONEDIT, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

APPLICATIONNAME:

string, conditional Max length: 256 description

APPLICATIONEMAIL:

string, conditional Max length: 64 description

APPLICATIONCODE:

string, optional Max length: 64 Application code

APPLICATIONPHONE:

string, optional Max length: 64 description

APPLICATIONWEBADDRESS:

string, optional Max length: 256 description

APPLICATIONTURNOVER:

string, optional Max length: 256 description

APPLICATIONCOMPANYTYPE:

string, optional Max length: 16 description See all possible values (4)

APPLICATIONSTATUS:

string, optional Max length: 16 description See all possible values (24)

APPLICATIONSHAREHOLDERS:

string, optional Max length: 100000 description

APPLICATIONSIGNAUTHORITIES:

string, optional Max length: 100000 description

APPLICATIONMERCHANT:

string, optional Max length: 100000 description

APPLICATIONDOCUMENTDATA:

string, optional Max length: 10000000 description

APPLICATIONFINANCIALDATA:

string, optional Max length: 100000 description

APPLICATIONSALESUPPORTDATA:

string, optional Max length: 100000 description

APPLICATIONRISKMANAGEMENTDATA:

string, optional Max length: 100000 description

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

SALESSUPPORTOPINION:

string, optional Max length: 256 description

Query Application

The QUERYAPPLICATION action lets you query a application. You should give the required parameters.

Request parameters:

ACTION:

QUERYAPPLICATION, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

APPLICATIONNAME:

string, optional Max length: 256 description

APPLICATIONEMAIL:

string, optional Max length: 64 description

APPLICATIONCODE:

string, optional Max length: 64 Application code

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

Approve Application

The APPLICATIONAPPROVE action lets you approve a application. You should give the required parameters.

Request parameters:

ACTION:

APPLICATIONAPPROVE, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

APPLICATIONEMAIL:

string, required Max length: 64 description

APPLICATIONNAME:

string, required Max length: 256 description

APPLICATIONCODE:

string, optional Max length: 64 Application code

APPLICATIONSTATUS:

string, required Max length: 4 description See all possible values (24)

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

APPLICATIONREJECTMSG:

string, optional Max length: 256 description

Currency Actions

Currency Exchange

Currency Exchange

Request parameters:

ACTION:

CURRENCYEXCHANGE, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

FROMCURRENCY:

string, required Max length: 3 description See all possible values (33)

TOCURRENCY:

string, required Max length: 3 description See all possible values (33)

AMOUNT:

decimal, optional Max length: 30 Amount of payment / transaction. Please note that, this amount is tax included, Paratika doesn't consider any other tax calculation.

Edit Seller

The SELLEREDIT action lets you edit an existing seller. You should provide seller id and merchant and you can update name, last name, mobile number, email, TCKN and status.

Request parameters:

ACTION:

SELLEREDIT, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

SELLERID:

string, required Max length: 32 Unique value per seller.

NAME:

string, optional Max length: 512 Name

LASTNAME:

string, optional Max length: 512 description

EMAIL:

string, optional Max length: 512 description

MOBILENUMBER:

string, optional Max length: 64 description

STATUS:

string, optional Max length: 2 Status information. See all possible values (4)

TCKN:

string, conditional Max length: 11 Customer Identity Number.

VKN:

string, conditional Max length: 10 Tax identification number

IBAN:

string, required Max length: 34 description

IBANUSD:

string, optional Max length: 34 description

IBANEUR:

string, optional Max length: 34 description

IBANGBP:

string, optional Max length: 34 description

SELLERPAYMENTDAYS:

string, required Max length: 32 Seller payment days should be sent in index format, separated with semicolon. Indexes for days are as follow: Monday(0), Tuesday(1), Wednesday(2), Thursday(3), Friday(4). Example for seller payment days to be on Monday and Friday, the value of SELLERPAYMENTDAYS parameter should be sent as follow: 0;4;

ACCOUNTOWNERNAME:

string, conditional Max length: 512 description

ACCOUNTOWNERLASTNAME:

string, conditional Max length: 512 description

SELLERPAYMENTDUEDAY:

integer, optional Max length: 2 description

COMMERCIALTITLE:

string, conditional Max length: 512 description

COMMISSIONAPPLYTYPE:

string, conditional Max length: 3 Only CA parameter is available for COMMISSIONAPPLYTYPE. Other parameters are not applicable See all possible values (3)

COMMISSIONAPPLIERTYPE:

string, conditional Max length: 3 Only CA parameter is available for COMMISSIONAPPLIERTYPE. Other parameters are not applicable See all possible values (3)

COMMISSIONVALUE:

decimal, optional Max length: 30 description

ONBEHALFOFMERCHANT:

string, optional Max length: 16 description

SELLERURL:

string, optional Max length: 256 description

ISDEFAULT:

string, optional Max length: 3 Default value: 'NO' description

Customer Commission Actions

Edit Customer Commission

The EDITCUSTOMERCOMMISSION request can be used to edit customer cost commission schema. On the "CURRENCYCOMMISSIONS" object you need to give which installment is being updated in the field commissionKey with format as an example below : 2 Installment AS CR2, or 4 Installment as CR4, or ON_NETWORK_DEBIT , and you set the value like : "commissionKey":"ON_NETWORK_DEBIT" or "commissionKey":"CR4". In the "commissionValue" - you set the value for that installment. If you want to add values for Payment Systems you need to fulfill the object "paymentSystemCurrencyCommissions" and add paymentSystemId for which you want to add values.

Request parameters:

ACTION:

EDITCUSTOMERCOMMISSION, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

CURRENCYCOMMISSIONS:

string, required Max length: 200000 description

ACTIVATIONDATE:

date, required Max length: 32 Format: [dd-MM-yyyy HH:mm] Activation date in Coordinated Universal Time (UTC) standard

OTP Actions

Add OTP

The OTPADD request can be used to generate and add a new OTP (One time password)

Request parameters:

ACTION:

OTPADD, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

SESSIONTOKEN:

string, optional Max length: 48 Session token.

EMAIL:

string, required Max length: 64 description

Edit OTP

The OTPEDIT request can be used to generate and edit OTP (One time password)

Request parameters:

ACTION:

OTPEDIT, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

SESSIONTOKEN:

string, optional Max length: 48 Session token.

OTPCODE:

string, required Max length: 6 description

OTPSTATUS:

string, required Max length: 2 description See all possible values (4)

EMAIL:

string, required Max length: 64 description

Bin Rule Actions

Add Bin Rule

The BINRULEADD request can be used to generate and add a new Bin Rule

Request parameters:

ACTION:

BINRULEADD, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, optional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

RULENAME:

string, required Max length: 128 Bin Rule

CARDBRAND:

string, conditional Max length: 8 description See all possible values (9)

CARDTYPE:

string, conditional Max length: 8 description See all possible values (6)

CARDNETWORK:

string, conditional Max length: 8 description See all possible values (10)

ISSUER:

string, conditional Max length: 128 description

COUNTRYISOA3:

string, conditional Max length: 3 description

LOWERLIMIT:

decimal, optional Max length: 22 description

UPPERLIMIT:

decimal, optional Max length: 22 description

STATUS:

string, required Max length: 2 Status information. See all possible values (4)

INSTALLMENTTYPE:

string, optional Max length: 64 description See all possible values (2)

INSTALLMENTCOUNT:

integer, conditional Max length: 2 description

FOREIGN:

string, optional Max length: 3 If select foreign no need to spesific country See all possible values (2)

UNDEFINEDBIN:

string, optional Max length: 3 Undefined Bin See all possible values (2)

Query Bin Rule

The QUERYBINRULE Query bin rule can be used to get all bin rules on the system

Request parameters:

ACTION:

QUERYBINRULE, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, optional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

RULENAME:

string, optional Max length: 128 Bin Rule

Delete Bin Rule

The BINRULEDELETE request can be used to delete an existing Bin Rule

Request parameters:

ACTION:

BINRULEDELETE, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, optional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

RULENAME:

string, required Max length: 128 Bin Rule

Edit Bin Rule

The BINRULEEDIT request can be used to edit an existing Bin Rule

Request parameters:

ACTION:

BINRULEEDIT, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, optional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

RULENAME:

string, required Max length: 128 Bin Rule

CARDBRAND:

string, conditional Max length: 8 description See all possible values (9)

CARDTYPE:

string, conditional Max length: 8 description See all possible values (6)

CARDNETWORK:

string, conditional Max length: 8 description See all possible values (10)

ISSUER:

string, conditional Max length: 128 description

COUNTRYISOA3:

string, conditional Max length: 3 description

LOWERLIMIT:

decimal, optional Max length: 22 description

UPPERLIMIT:

decimal, optional Max length: 22 description

STATUS:

string, optional Max length: 2 Status information. See all possible values (4)

INSTALLMENTTYPE:

string, optional Max length: 64 description See all possible values (2)

INSTALLMENTCOUNT:

integer, conditional Max length: 2 description

FOREIGN:

string, optional Max length: 3 If select foreign no need to spesific country See all possible values (2)

UNDEFINEDBIN:

string, optional Max length: 3 Undefined Bin See all possible values (2)

Bin Rule, Payment System Pool Association Actions

Add Bin Rule, Payment System Pool Association

The BINRULEPSPASSOCADD request can be used to add a new Bin Rule, Payment System Pool Association

Request parameters:

ACTION:

BINRULEPSPASSOCADD, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

RULENAME:

string, required Max length: 128 Bin Rule

PAYMENTSYSTEMPOOLNAME:

string, required Max length: 255 Payment system pool

PAYMENTSYSTEM:

string, required Max length: 128 Name of the payment system (bank payment gateway / vPOS account). Specified name should match the one given in Paratika. If not provided, Paratika smart switch feature will be used.

STATUS:

string, required Max length: 2 Status information. See all possible values (4)

Edit Bin Rule, Payment System Pool Association

The BINRULEPSPASSOCEDIT request can be used to edit an existing Bin Rule, Payment System Pool Association

Request parameters:

ACTION:

BINRULEPSPASSOCADD, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

RULENAME:

string, required Max length: 128 Bin Rule

PAYMENTSYSTEMPOOLNAME:

string, required Max length: 255 Payment system pool

PAYMENTSYSTEM:

string, required Max length: 128 Name of the payment system (bank payment gateway / vPOS account). Specified name should match the one given in Paratika. If not provided, Paratika smart switch feature will be used.

STATUS:

string, required Max length: 2 Status information. See all possible values (4)

Query Bin Rule, Payment System Pool Association

The QUERYBINRULEPSPASSOC Request can be used to query Bin Rule and Payment System Pool Relations

Request parameters:

ACTION:

QUERYBINRULEPSPASSOC, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, optional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

Delete Bin Rule, Payment System Pool Association

The BINRULEPSPASSOCDELETE request can be used to delete an existing Bin Rule, Payment System Pool Association

Request parameters:

ACTION:

BINRULEPSPASSOCDELETE, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

BINRULEPSPOOLASSOCNAME:

string, required Max length: 128 Association Name, unique and is autogenerated

Shopping Loan Actions

Start Online Shopping Loan

The STARTONLINESHOPPINGLOAN request can be used to start the loan and get the redirection URL to finish the payment

Request parameters:

ACTION:

STARTONLINESHOPPINGLOAN, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, required Max length: 48 Session token.

PAYMENTSYSTEM:

string, conditional Max length: 128 Name of the payment system (bank payment gateway / vPOS account). Specified name should match the one given in Paratika. If not provided, Paratika smart switch feature will be used.

PAYMENTSYSTEMTYPE:

string, conditional Max length: 128 Name of payment system type. Available types for loans: ISBANK_LOAN, KUVEYTTURK_LOAN, AKTIFBANK_LOAN, FIBABANKA_LOAN

Kuveyt Türk Loan Result Notification

Once Primary Transaction is performed with KuveytTürk Loan payment system, we will set transaction status for every transaction to IN PROGRESS. Once Transaction is completed (failed or approved) in KuveytTürk side, KuveytTürk will notify us via this endpoint.

Request parameters:

ACQUIRERID:

string, required Max length: 50 description

ACQUIRERPASSWORD:

string, required Max length: 50 description

TRANSACTIONID:

string, required Max length: 64 description

api call will be used to validate user.

The VALIDATEUSER api call will be used to validate user.

Request parameters:

ACTION:

VALIDATEUSER, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

USEREMAIL:

string, required Max length: 128 Parameter will be used to see if the user exist with the mail in the system

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

Api call will be used to see providers shared by enqura

The OPENBANKINGPROVIDERLIST Api call will be used to see providers shared by enqura

Request parameters:

ACTION:

OPENBANKINGPROVIDERLIST, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANT:

string, conditional Max length: 16 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

Open Banking Actions

The OPENBANKINGGETREFERENCEINFO The API call is used to get a reference information from Enqura. This reference information will be used during the account payment process.

ACTION:

OPENBANKINGGETREFERENCEINFO, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANT:

string, conditional Max length: 16 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

IDENTIFIERNUMBER:

string, required Max length: 40 Customer Identity Number (TCKN or VKN value should be entered).

Open Banking Actions

The OPENBANKINGACCOUNTLIST Api is used to obtain account information regarding the entered customer identification number from Enqura.

ACTION:

OPENBANKINGGETREFERENCEINFO, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANT:

string, conditional Max length: 16 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

IDENTIFIERNUMBER:

string, required Max length: 40 Customer Identity Number (TCKN or VKN value should be entered).

Query Actions

Query Transaction

The Query Transaction request will return the details of successful transaction(s) for a specified order/payment (using MerchantPaymentID) or transaction (using PGTRANID) including the status of payment, the bank (payment system / vpos) that processed the transaction, number of installments and the interest rate.

Response time to transactions from bank is maximum 90 seconds. As a merchant, QUERYTRANSACTION service must be used to check the status of the transaction in the bank. If there is a late response from the bank or there is no response from the bank about transaction, it is important that you must integrate QUERYTRANSACTION service. Through this service, transaction status is acknowledged in MSU. Based on this acknowledgement you can either update your ERP or cancel the transaction.

Request parameters:

ACTION:

QUERYTRANSACTION, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANT:

string, required Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, required Max length: 128 API User.

MERCHANTPASSWORD:

string, required Max length: 128 API User password.

PGTRANID:

string, optional Max length: 64 Transaction ID given by payment gateway.

TRANSACTIONSTATUS:

string, optional Max length: 18 Status of Transaction.

STARTDATE:

date, optional Max length: 16 Format: [dd-MM-yyyy HH:mm] Start date of the transaction query.

ENDDATE:

date, optional Max length: 16 Format: [dd-MM-yyyy HH:mm] End date of the transaction query.

OFFSET:

string, optional Max length: 4 Default value: '0' Specifies the number from which the transactions will start for paginated data.

LIMIT:

string, optional Max length: 4 Default value: '1000' The maximum number of transactions in response.

MERCHANTPAYMENTID:

string, optional Max length: 128 Unique Payment ID given by Merchant.

CUSTOMER:

string, optional Max length: 128 The Merchant System ID for customer. It must be unique within a Merchant.

CUSTOMEREMAIL:

string, optional Max length: 64 Customer e-mail. This information should be passed correctly if the customer information services are used.

CUSTOMERNAME:

string, optional Max length: 128 Name of the Customer. This information should be passed correctly if the customer information services are used.

CUSTOMERPHONE:

string, optional Max length: 64 Customer phone / mobile number. This information should be passed correctly if the customer information services are used.

MERCHANTNOTE:

string, optional Max length: 50 If the merchant has a note regarding payment, it should be written to this parameter.

SELLERID:

string, optional Max length: 32 Unique value per seller.

FORGROUP:

string, optional Max length: 3 Default value: 'YES' Specifies the for group featured usages. Available values are 'yes' and 'no'.

Query Installment

The QUERYINSTALLMENT request will return the available installments which can be used by card holder.

Request parameters:

ACTION:

QUERYINSTALLMENT, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

BIN:

string, optional Max length: 8 BIN value (first 8 PAN digits). Please check https://en.wikipedia.org/wiki/Bank_card_number for details.

PAYMENTSYSTEM:

string, optional Max length: 128 Name of the payment system (bank payment gateway / vPOS account). Specified name should match the one given in Paratika. If not provided, Paratika smart switch feature will be used.

PAYMENTSYSTEMTYPE:

string, optional Max length: 32 Name of payment system type. Available types for loans: ISBANK_LOAN, KUVEYTTURK_LOAN, AKTIFBANK_LOAN, FIBABANKA_LOAN See all possible values (35)

Query Card

The QUERYCARD request can be used to get all the card tokens saved for a particular cardholder (customer) or the details of the card based on the given token value.

Request parameters:

ACTION:

QUERYCARD, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

CARDTOKEN:

string, optional Max length: 64 Secure alphanumeric value replacing card number & expiry date. Required when none of the other card information are provided.

CARDSAVENAME:

string, optional Max length: 64 Given name for the saved card.

CUSTOMER:

string, optional Max length: 128 The Merchant System ID for customer. It must be unique within a Merchant.

FORGROUP:

string, optional Max length: 3 Default value: 'YES' Specifies the for group featured usages. Available values are 'yes' and 'no'.

OFFSET:

integer, optional Max length: 4 Default value: '0' Specifies the number from which the transactions will start for paginated data.

LIMIT:

integer, optional Max length: 4 Default value: '1000' The maximum number of transactions in response.

Query Card Expiry

The QUERYCARDEXPIRY request can be used to get all the cards that will be expired in this and the next month.

Request parameters:

ACTION:

QUERYCARDEXPIRY, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANT:

string, required Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, required Max length: 128 API User.

MERCHANTPASSWORD:

string, required Max length: 128 API User password.

CUSTOMER:

string, required Max length: 128 The Merchant System ID for customer. It must be unique within a Merchant.

OFFSET:

string, optional Max length: 4 Default value: '0' Specifies the number from which the transactions will start for paginated data.

LIMIT:

string, optional Max length: 4 Default value: '1000' The maximum number of transactions in response.

FORGROUP:

string, optional Max length: 3 Default value: 'YES' Specifies the for group featured usages. Available values are 'yes' and 'no'.

Query Session

The QUERYSESSION request can be used to get merchant, customer and session information of a valid session.

Request parameters:

ACTION:

QUERYSESSION, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, required Max length: 48 Session token.

INCLUDELOGO:

string, optional Max length: 3 Whether the logo should be returned or no. See all possible values (2)

Query Bin

The QUERYBIN Request can be used to get BIN information

Request parameters:

ACTION:

QUERYBIN, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

BIN:

string, conditional Max length: 8 BIN value (first 8 PAN digits). Please check https://en.wikipedia.org/wiki/Bank_card_number for details.

CARDTOKEN:

string, conditional Max length: 64 Secure alphanumeric value replacing card number & expiry date. Required when none of the other card information are provided.

Payment Systems

Payment Systems QUERYPAYMENTSYSTEMS Request can be used to get all available payment systems

Request parameters:

ACTION:

QUERYPAYMENTSYSTEMS, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

BIN:

string, conditional Max length: 8 BIN value (first 8 PAN digits). Please check https://en.wikipedia.org/wiki/Bank_card_number for details.

CARDTOKEN:

string, conditional Max length: 64 Secure alphanumeric value replacing card number & expiry date. Required when none of the other card information are provided.

Query Pay By Link Payment

Query Pay By Link Payment The request will return pay by link payments according to request filters. Date attributes in response are returned in merchant's timezone and formatted in ISO_8601

Request parameters

ACTION:

QUERYPAYBYLINKPAYMENT, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

PAYBYLINKTOKEN:

string, conditional Max length: 48 description

MERCHANTNOTE:

string, optional Max length: 50 If the merchant has a note regarding payment, it should be written to this parameter.

STARTDATE:

date, conditional Max length: 32 Format: [dd-MM-yyyy HH:mm] Start date of the transaction query.

ENDDATE:

date, conditional Max length: 32 Format: [dd-MM-yyyy HH:mm] End date of the transaction query.

DUEDATE:

date, optional Max length: 16 Format: [dd-MM-yyyy HH:mm] description

CUSTOMEREMAIL:

string, optional Max length: 64 Customer e-mail. This information should be passed correctly if the customer information services are used.

PAYBYLINKSTATUS:

string, optional Max length: 2 description See all possible values (5)

Query PAN

The QUERYPAN request can be used to get BIN information for the specified card pan.

Request parameters:

ACTION:

QUERYPAN, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

CARDPAN:

string, required Max length: 19 PAN (Primary account number), card number. Please check https://en.wikipedia.org/wiki/Bank_card_number for details.

Query Merchant Content

The QUERYMERCHANTCONTENT request can be used to get MERCHANT CONTENTS.

Request parameters:

ACTION:

QUERYMERCHANTCONTENT, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANTCONTENTID:

string, optional Max length: 16 Unique Merchant Content ID given by Merchant.

Query Points

The QUERYPOINTS request can be used to get MERCHANT's points. Query made from bank side and a financial transaction.

Request parameters:

ACTION:

QUERYPOINTS, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANTPAYMENTID:

string, conditional Max length: 128 Unique Payment ID given by Merchant.

AMOUNT:

decimal, conditional Max length: 30 Amount of payment / transaction. Please note that, this amount is tax included, Paratika doesn't consider any other tax calculation.

CUSTOMER:

string, conditional Max length: 128 The Merchant System ID for customer. It must be unique within a Merchant.

CURRENCY:

string, conditional Max length: 3 ISO Alpha transaction currency code like TRY, EUR, USD, GBP. Please check https://en.wikipedia.org/wiki/ISO_4217#Position_of_ISO_4217_code_in_amounts for details. See all possible values (33)

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

CARDTOKEN:

string, conditional Max length: 64 Secure alphanumeric value replacing card number & expiry date. Required when none of the other card information are provided.

CARDPAN:

string, conditional Max length: 19 PAN (Primary account number), card number. Please check https://en.wikipedia.org/wiki/Bank_card_number for details.

CARDEXPIRY:

string, conditional Max length: 7 Expiry date of the card. Format should be [mm.yy].

NAMEONCARD:

string, conditional Max length: 64 Name on the card.

CARDCVV:

string, optional Max length: 4 Security number of the card, CVV value.

INSTALLMENTS:

integer, optional Max length: 2 Default value: '1' Number of installments. Specified number should exist in the payment system as defined.

PAYMENTSYSTEM:

string, optional Max length: 128 Name of the payment system (bank payment gateway / vPOS account). Specified name should match the one given in Paratika. If not provided, Paratika smart switch feature will be used.

FORGROUP:

string, optional Max length: 3 Default value: 'YES' Specifies the for group featured usages. Available values are 'yes' and 'no'.

Query Recurring Plan

Request parameters:

ACTION:

QUERYRECURRINGPLAN, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANT:

string, optional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, optional Max length: 128 API User.

MERCHANTPASSWORD:

string, optional Max length: 128 API User password.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

STARTDATE:

date, conditional Max length: 16 Format: [dd-MM-yyyy] Start date of the transaction query.

ENDDATE:

date, conditional Max length: 16 Format: [dd-MM-yyyy] End date of the transaction query.

RECURRINGPLANCODE:

string, conditional Max length: 16 Unique code of a recurring plan.

CARDPAN:

string, optional Max length: 19 PAN (Primary account number), card number. Please check https://en.wikipedia.org/wiki/Bank_card_number for details.

CUSTOMER:

string, optional Max length: 128 The Merchant System ID for customer. It must be unique within a Merchant.

Query Recurring Plan Card

Request parameters:

ACTION:

QUERYRECURRINGPLANCARD, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

RECURRINGPLANCODE:

string, required Max length: 16 Unique code of a recurring plan.

Query Campaign

The QUERYCAMPAIGN request can be used to get campaigns.

Request parameters:

ACTION:

QUERYCAMPAIGN, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

BIN:

string, conditional Max length: 8 BIN value (first 8 PAN digits). Please check https://en.wikipedia.org/wiki/Bank_card_number for details.

CARDTOKEN:

string, conditional Max length: 64 Secure alphanumeric value replacing card number & expiry date. Required when none of the other card information are provided.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

Query Campaign Online

The QUERYCAMPAIGNONLINE request can be used to get card holders' campaigns if they are available to merchants. Query made from bank side and a financial transaction.

Request parameters:

ACTION:

QUERYCAMPAIGNONLINE, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANTPAYMENTID:

string, conditional Max length: 128 Unique Payment ID given by Merchant.

AMOUNT:

decimal, conditional Max length: 30 Amount of payment / transaction. Please note that, this amount is tax included, Paratika doesn't consider any other tax calculation.

INSTALLMENTS:

integer, required Max length: 2 Number of installments. Specified number should exist in the payment system as defined.

CURRENCY:

string, conditional Max length: 3 ISO Alpha transaction currency code like TRY, EUR, USD, GBP. Please check https://en.wikipedia.org/wiki/ISO_4217#Position_of_ISO_4217_code_in_amounts for details. See all possible values (33)

CUSTOMER:

string, conditional Max length: 128 The Merchant System ID for customer. It must be unique within a Merchant.

CARDTOKEN:

string, conditional Max length: 64 Secure alphanumeric value replacing card number & expiry date. Required when none of the other card information are provided.

CARDCVV:

string, optional Max length: 4 Security number of the card, CVV value.

CARDPAN:

string, conditional Max length: 19 PAN (Primary account number), card number. Please check https://en.wikipedia.org/wiki/Bank_card_number for details.

CARDEXPIRY:

string, conditional Max length: 7 Expiry date of the card. Format should be [mm.yy].

NAMEONCARD:

string, conditional Max length: 64 Name on the card.

CUSTOMERIP:

string, optional Max length: 39 Customer IP Address

CUSTOMERUSERAGENT:

string, optional Max length: 512 Customer User Agent

EXTRA:

string, optional Max length: 1024 Extra Parameter is a custom parameter that is used to pass additional parameters to session token. This parameter is expected to be in JSON(URL-ENCODED) format. If they are mispelled, they will be ignored! Supported parameters are: CardHolderAgreementMode(value: NONE/SHOW/SHOWCHECKED/SHOWCHECKEDDISABLED), AlwaysSaveCard(value: true/false), BuyerType (value: L for logged in customer; A for anonymous, F for the first shopping with memebership. OR it can be 0, 1, 2 for those cases), IsbankBolumKodu(string), IframeDomainUrl indicates from which URL address payment will be proceesed., PREAUTH=YES parameter indicates that payment will be processed as pre-authorization even if is started as sale., IGNORECUSTOMERCOMMISSION(values : YES/NO).
EXTRA: {"AlwaysSaveCard": "true", "BuyerType": "L", "IsbankBolumKodu": 12, "CardHolderAgreementMode": "SHOWCHECKED", "IGNORECUSTOMERCOMMISSION" : "YES"}

Other bank parameters

• MAXIMUMMOBIL - include Maximum Mobil payment system name like below to have Maximum Mobil tab on Default HPP
  {"MaximumMobilPaymentSystem":"PaymentSystemName"}
• GIROGATE payment methods. If one of payment methods is sent as "Yes", authentication will be done using GiroGate payment methods. Possible values: YES/NO.
  • SOFORT: {"SOFORT": "YES"}
  • SAFETYPAY: {"SAFETYPAY": "YES"}
  • QIWI: {"QIWI": "YES"}
  • GIROPAY: {"GIROPAY": "YES"}
  • IDEAL: {"IDEAL": "YES"}
  • FINNISHONLINEBANKING: {"FINNISHONLINEBANKING": "YES"}
  • BANCONTACT: {"BANCONTACT": "YES"}
  • ALIPAY: {"ALIPAY": "YES"}
  • MULTIBANCO: {"MULTIBANCO": "YES"}
  • TRUSTPAY: {"TRUSTPAY": "YES"}
  • EPS: {"EPS": "YES"}
  • MYBANK: {"MYBANK": "YES"}
  • P24: {"P24": "YES"}
  • BOLETO: {"BOLETO": "YES"}
  • ELO: {"ELO": "YES"}
  • SEPA: {"SEPA": "YES"}
  • UPOP: {"UPOP": "YES"}
• ISBANK - include in extra like below to send agriculture template info to Isbank when doing imece card operations.
  {"IMCKOD":"imckod", "FDONEM":"fdonem"}
• SEKERBANK - can also take these extra parameters:
  {"HASATKARTSATIS", "VADEKODU", "VADEADEDI", "URUNKODU", "PLASIYERNO", "FATURANO"}

• ISBANK_LOAN - The following fields must be used for Kuveytturk shopping credit and all fields are required. ISBANK_LOAN parameter must be sent "YES".
  {"ISBANK_LOAN":"YES", "ISBANK_LOAN.maximum_term":"5"}
• KUVEYTTURK_LOAN - The following fields must be used for Kuveytturk shopping credit and all fields are required. KUVEYTTURK_LOAN parameter must be sent "YES".
  {"KUVEYTTURK_LOAN":"YES", "KUVEYTTURK_LOAN.softDescriptor":"Finansman islem bilgisi", "KUVEYTTURK_LOAN.commissionAmount":"0", "KUVEYTTURK_LOAN.orderItemCount":"1", "KUVEYTTURK_LOAN.categoryCode":"1101", "KUVEYTTURK_LOAN.unitPrice":"100", "KUVEYTTURK_LOAN.count":"1", "KUVEYTTURK_LOAN.channel":"WM"}
• NKOLAY_LOAN - The following fields must be used for NKolay shopping credit and all fields are required. NKolay parameter must be sent "YES".
  {"NKOLAY_LOAN":"YES", "NKolay.identityNumber":"11920171664", "NKolay.products": {"NKolay.name": "phone","NKolay.categoryId": 1,"NKolay.categoryName": "Cep Telefonu", "NKolay.quantity": 1,"NKolay.totalPrice": 8000.0}
• FIBABANKA_LOAN - The following fields must be used for Fibabanka shopping credit and all fields are required. FIBABANKA_LOAN parameter must be sent "YES".
  {"FIBABANKA_LOAN":"YES", "FIBABANKA_LOAN.productType":"5"}

PAYMENTSYSTEMTYPENAME:

string, optional Max length: 100 description

FORGROUP:

string, optional Max length: 3 Default value: 'YES' Specifies the for group featured usages. Available values are 'yes' and 'no'.

Query Payment System Data

The Query Payment System Data QueryPSData

Request parameters:

ACTION:

QUERYPAYMENTSYSTEMDATA, required Max length: 128 Core parameter which specifies the main action for the API call.

INSTALLMENTS:

integer, required Max length: 2 Default value: '1' Number of installments. Specified number should exist in the payment system as defined.

EFTCODE:

string, optional Max length: 4 description

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

SESSIONTOKEN:

string, optional Max length: 48 Session token.

BIN:

string, conditional Max length: 8 BIN value (first 8 PAN digits). Please check https://en.wikipedia.org/wiki/Bank_card_number for details.

PAYMENTSYSTEMTYPE:

string, conditional Max length: 32 Name of payment system type. Available types for loans: ISBANK_LOAN, KUVEYTTURK_LOAN, AKTIFBANK_LOAN, FIBABANKA_LOAN See all possible values (35)

CURRENCY:

string, optional Max length: 3 ISO Alpha transaction currency code like TRY, EUR, USD, GBP. Please check https://en.wikipedia.org/wiki/ISO_4217#Position_of_ISO_4217_code_in_amounts for details. See all possible values (33)

Query Merchant Commission

The QUERYMERCHANTCOMMISSION request can be used to get transaction hosting commission

Request parameters:

ACTION:

QUERYMERCHANTCOMMISSION, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, optional Max length: 128 Merchant business code defined in the system.

SESSIONTOKEN:

string, optional Max length: 48 Session token.

Query Customer Commission

The QUERYCUSTOMERCOMMISSION request can be used to get customer commission schema.

Request parameters:

ACTION:

QUERYCUSTOMERCOMMISSION, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

ACTIVATIONDATE:

date, optional Max length: 32 Format: [dd-MM-yyyy HH:mm] Activation date in Coordinated Universal Time (UTC) standard

ACTIVATIONDATEINMILLISECONDS:

string, optional Max length: 19 description

Query Order Item

Request parameters:

ACTION:

QUERYORDERITEM, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

PGTRANID:

string, conditional Max length: 64 Transaction ID given by payment gateway.

MERCHANTPAYMENTID:

string, conditional Max length: 128 Unique Payment ID given by Merchant.

Query Seller

The QUERYSELLER request can be used to get all the sellers saved for a particular merchant or the details of specific seller based on the given sellerId value.

Request parameters:

ACTION:

QUERYSELLER, required Max length: 128 Core parameter which specifies the main action for the API call.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

SELLERID:

string, optional Max length: 32 Unique value per seller.

ONBEHALFOFMERCHANT:

string, optional Max length: 64 description

STATUS:

string, optional Max length: 2 Status information.

Query Recon Transaction

The Query Recon Transaction request can be used to get transaction details for reconciliation purposes.

Request parameters:

ACTION:

RECONTRANSACTION, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, required Max length: 128 API User.

MERCHANTPASSWORD:

string, required Max length: 128 API User password.

MERCHANT:

string, optional Max length: 128 Merchant business code defined in the system.

PAYMENTSYSTEMTYPE:

string, optional Max length: 32 Name of payment system type. Available types for loans: ISBANK_LOAN, KUVEYTTURK_LOAN, AKTIFBANK_LOAN, FIBABANKA_LOAN See all possible values (35)

PGORDERID:

string, optional Max length: 64 description

PGTRANID:

string, optional Max length: 64 Transaction ID given by payment gateway.

PGTRANAPPRCODE:

string, optional Max length: 64 description

STARTDATE:

date, conditional Max length: 19 Format: [dd-MM-yyyy HH:mm:ss] Start date of the transaction query.

ENDDATE:

date, conditional Max length: 19 Format: [dd-MM-yyyy HH:mm:ss] End date of the transaction query.

OFFSET:

string, optional Max length: 6 Default value: '0' Specifies the number from which the transactions will start for paginated data.

LIMIT:

string, optional Max length: 4 Default value: '1000' The maximum number of transactions in response.

MERCHANTPAYMENTID:

string, optional Max length: 128 Unique Payment ID given by Merchant.

TRANSACTIONTYPE:

string, optional Max length: 32 description See all possible values (12)

ENDOFDAYDATE:

string, optional Max length: 3 description See all possible values (2)

Query Payment System Pool

The QUERYPAYMENTSYSTEMPOOL Request can be used to get payment system pools

Request parameters:

ACTION:

QUERYPAYMENTSYSTEMPOOL, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

STATUS:

string, optional Max length: 2 Status information. See all possible values (4)

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

MERCHANT:

string, optional Max length: 128 Merchant business code defined in the system.

Query Agriculture Template

The QUERYAGRICULTURETEMPLATE request can be used to get agriculture template information from bank side.

Request parameters:

ACTION:

QUERYAGRICULTURETEMPLATE, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

MERCHANT:

string, conditional Max length: 128 Merchant business code defined in the system.

SESSIONTOKEN:

string, conditional Max length: 48 Session token.

CURRENCY:

string, conditional Max length: 3 ISO Alpha transaction currency code like TRY, EUR, USD, GBP. Please check https://en.wikipedia.org/wiki/ISO_4217#Position_of_ISO_4217_code_in_amounts for details. See all possible values (33)

PAYMENTSYSTEM:

string, optional Max length: 128 Name of the payment system (bank payment gateway / vPOS account). Specified name should match the one given in Paratika. If not provided, Paratika smart switch feature will be used.

INSTALLMENTS:

integer, optional Max length: 2 Default value: '1' Number of installments. Specified number should exist in the payment system as defined.

CUSTOMER:

string, conditional Max length: 128 The Merchant System ID for customer. It must be unique within a Merchant.

CUSTOMEREMAIL:

string, optional Max length: 64 Customer e-mail. This information should be passed correctly if the customer information services are used.

CUSTOMERNAME:

string, optional Max length: 128 Name of the Customer. This information should be passed correctly if the customer information services are used.

CARDTOKEN:

string, conditional Max length: 64 Secure alphanumeric value replacing card number & expiry date. Required when none of the other card information are provided.

CARDPAN:

string, conditional Max length: 19 PAN (Primary account number), card number. Please check https://en.wikipedia.org/wiki/Bank_card_number for details.

CARDEXPIRY:

string, conditional Max length: 7 Expiry date of the card. Format should be [mm.yy].

NAMEONCARD:

string, conditional Max length: 64 Name on the card.

FORGROUP:

string, optional Max length: 3 Default value: 'YES' Specifies the for group featured usages. Available values are 'yes' and 'no'.

Query Application Document

Request parameters:

ACTION:

QUERYAPPLICATIONDOCUMENT, required Max length: 128 Core parameter which specifies the main action for the API call.

MERCHANTUSER:

string, conditional Max length: 128 API User.

MERCHANTPASSWORD:

string, conditional Max length: 128 API User password.

APPLICATIONCODE:

string, required Max length: 64 Application code

APPLICATIONDOCUMENTTYPE:

string, optional Max length: 64 Application document type See all possible values (14)

SESSIONTOKEN:

string, conditional Max length: 48 Session token.