You can click for ParamPOS application process: https://param.com.tr/param-sanal-pos
Whether a company will work with Param is determined only after the relevant departments evaluate the application. However, generally, virtual POS services cannot be provided to businesses in the categories of gambling, betting sites, sale of alcoholic beverages, sale of tobacco products, sale of firearms, services/products with erotic and/or pornographic content, sites supporting political views, sites promoting violence and/or crime, sale of live animals, sale of prescription drugs and/or narcotics, firms selling through call centers, sites selling listening devices, forex services, auction sites, sale of replica or counterfeit products, and dating sites.
https://kurumsal.param.com.tr you can reach from the internet branch.
Customer Satisfaction and Increased Transaction Volume
Virtual POS enables e-commerce companies to convert individual buyers into loyal customers with membership systems and card storage features, instilling trust. In an environment where credit card or bank card information is shared, and high limits and large personal accounts are discussed, customers must primarily feel secure. The more secure they feel about their information and cards, the more frequently they will shop from that e-commerce company, turning it into a habit. Additionally, e-commerce companies without an SSL certificate may be liable to pay substantial damages if customers' card information is maliciously copied and used by third parties.
What is SSL?
SSL (Secure Sockets Layer) is a security protocol that encrypts the transfer of information entered into an internet browser. Data traffic is encrypted, making it unreadable to others, and personal information such as credit card details cannot be intercepted while in transit.
For anyone concerned about data security in the digital world, SSL is essential. With online shopping, the security and protection of personal data such as names, addresses, and emails, along with card information, become even more crucial.
Prevents Malicious Use
E-commerce websites with an SSL certificate can be identified as secure by using https:// instead of http:// in the address bar. This is because a trusted company has verified the SSL certificate, allowing the site to use https://. During transactions on sites with this certificate, credit card information is encrypted and sent to the payment processor, making it extremely difficult to intercept and misuse the encrypted combination of passwords and personal data, thereby preventing sharing or copying with third parties for malicious purposes.
Who Can I Get Support From for SSL Installation?
SSL installation can be easily done. If you have no previous experience with this:
· If you use a ready-made e-commerce infrastructure, you can get support from your
infrastructure provider.
· If you have an open-source or custom software website, you can get support from your
hosting provider. The hosting company will assist you with SSL installation for your
site.
· If you plan to complete the SSL setup on your site yourself, you can find detailed
information at https://movingtohttps.com.
Due to the necessity of updating our web services to the latest TLS version, HTTPS connections to our web services must use TLS 1.2.
The security protocol should be set to Tls 1.2 before calling the web service as follows:
System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;
st_odeme = ws.TP_Islem_Odeme(st, SanalPOS_ID, ....)
The security protocol should be set to Tls 1.2 before calling the web service as follows:
$mode = array
(
'soap_version' => 'SOAP_1_1',
'trace' => 1,
'stream_context' => stream_context_create(array(
'ssl' => array(
'crypto_method' => STREAM_CRYPTO_METHOD_TLSv1_2_CLIENT,
)
))
);
$client = new SoapClient($Webservis_WSDL_URL, $mode);
If you encounter any issues, please send your request to [email protected].
Payment Card Industry Security Standards, established by a council known as the PCI Security Standards Council, which includes members such as Visa, American Express, MasterCard, and Discover Financial Services, refer to the security standard set to ensure data security in payment card systems.
It aims to prevent losses and data breaches (theft and misuse of data) typically occurring in e-commerce transactions conducted through virtual POS providers and banking institutions. It involves processes such as Network Security, Vulnerability Scanning, and Access Control to detect non-compliance with security standards on servers and software where credit card transactions are processed. PCI DSS compliance scanning must be repeated four times a year at three-month intervals, and the scan results must be reported to the relevant financial institution.
Organizations conducting credit card transactions over the Internet are obligated to perform PCI DSS compliance scans to verify that their environments meet PCI standards. Comodo's PCI DSS Scanning service conducts remote security scans for your e-commerce system to check if your application and server, where your e-commerce system operates, comply with the standards set by PCI CSS, and provides reports. In systems where a specific volume of transactions occurs, the financial institution acting as the virtual POS provider often requires PCI DSS scanning.
3D Secure system is a system supported by international card organizations that enables secure e-commerce transactions. With 3D Secure, transaction security is ensured, and merchants are protected from cardholders' claims that transactions are not authorized by them. It is a three-dimensional security protocol that verifies and protects the flow of information between the cardholder, the website (merchant), and the bank using special codes and keys.
With ParamPOS assurance, your payments are credited to your account the next day.
22 banks and 8 card brands Axess-Bonus-Combo-Finans/Advantage-Maximum-Paraf-SağlamKart-World
After logging into your Param panel, you can access the receipt information from the “Finance > Accounting > Report > Receipt Inquiry” screen.
The lower limit varies from bank to bank. We recommend that you make transactions with at least 5 TL in payment transactions.
After logging in to your money panel, you can set the notification option from My Card > Contact tab.
You can access the param logo and images at https://param.com.tr/basin-medya-kiti
Occasionally, during payment transactions with banks, a timeout error may be returned as a response. We return this response from the bank to our member merchants within the Response.
Since a transaction timeout from the bank may or may not be processed by the bank, it is necessary to check the current status of the transaction from the bank and initiate cancellation if needed.
With the auto-cancel feature, we monitor this process on your behalf, and if the transaction is successful, it will be canceled after 180 seconds. This feature is optional, and member merchants suitable for this business model can request its setup from our sales support team.
No, canceled or auto-canceled transactions are not reflected on the statement.
You can perform your tests with the test cards in the https://dev.param.com.tr/tr/test-kartlari tab. Test cards only work in the test environment. You can access the test environment information from the integration document.
After integrating with test environment information, we recommend checking the integration test scenarios. You can access the test scenarios at https://dev.param.com.tr/en/api .
After integrating with test environment information, we recommend checking the integration test scenarios. Then, you can email [email protected] to obtain live information.
Google Chrome Browser SameSite Update
With the update in Google Chrome browsers, cookies not defined as
SameSite=None; Secure
will
default to SameSite=Lax
(first-party cookie). This means that first-party
cookies can only be
accessed from the defined domain/host. If there is a cross-site request (e.g., a POST
request from a different
domain), cookie access in the browser will be restricted for security reasons.
Chrome Update Timeline:
This update will continue gradually to cover all Chrome browsers. While a specific date is not set, Chrome considers feedback and issues during this process. Similar updates are expected from other browsers as well.
Example Scenario for SameSite Issue:
A customer visits the checkout page on a merchant's website (the merchant has set a cookie
for the customer).
The merchant initiates a 3D Secure (3DS) request and prints the HTML content received to
redirect the customer to
the bank's page (which changes the domain). The customer completes SMS verification. The
bank redirects the
customer to param, and param redirects to the merchant's result page. Meanwhile,
payment-related information is
sent to this address via POST method. At this stage, the merchant's system queries the
cookie information to
recognize the customer or check the cart. If the cookie is not defined as
SameSite=None; Secure
,
Chrome will not allow these cookies to be read. The merchant cannot process the payment or
create the order.
Solution for SameSite Issue:
If your param redirects and completes the process with cookie access at the
callbackUrl
where
the result is POSTed, you need to define the relevant cookie as
SameSite=None; Secure
.
Example Cookie Definition for ASP.NET 4.7.2+:
Response.Cookies.Add(new HttpCookie("key", "value")
{
SameSite = SameSiteMode.None,
Secure = true,
});
Example Cookie Definition for ASP.NET Core 2.1+
Response.Cookies.Append("Key", "Value", new CookieOptions()
{
SameSite = SameSiteMode.None,
Secure = true,
});
Example Cookie Definition for ASP.NET 4.7.2+
Response.Cookies.Add(new HttpCookie("key", "value")
{
SameSite = SameSiteMode.None,
Secure = true,
});
Example Cookie Definition for PHP 7.3
setcookie('same-site-cookie', 'foo', ['samesite' => 'Lax']);
setcookie('cross-site-cookie', 'bar', ['samesite' => 'None', 'secure' => true]);
Sample Cookie Definition for Versions Prior to PHP 7.3:
header('Set-Cookie: same-site-cookie=foo; SameSite=Lax');
header('Set-Cookie: cross-site-cookie=bar; SameSite=None; Secure');