Can DenizBank Virtual POS be added to Wix?

Whether DenizBank Virtual POS could be integrated into Wix was a question of interest for many businesses, especially those wishing to conduct e-commerce in Türkiye. Now, Wix supports DenizBank's virtual POS infrastructure. This allows businesses to receive payments with DenizBank's fast processing structure, robust 3D Secure verification system, and favorable commission rates.

Is Wix integration possible with DenizBank Virtual POS?

Yes, DenizBank Virtual POS can be integrated with the Wix platform. This integration is carried out through a custom backend structure via the Velo by Wix development environment. Once the API information, security keys, and callback URLs received from the bank are defined in the system, DenizBank Virtual POS can work fully compatibly on Wix.

The advantages of the integration include DenizBank's reliable payment infrastructure, fast authorization and transaction confirmation, secure payments with 3D Secure 2.0 support, installment payment options, Bonus card ecosystem advantages, and competitive commission rates.

When the technical structure of the integration is examined, it is seen that Wix uses the Velo development environment for custom POS integrations in addition to its standard payment systems. A connection is established to the DenizBank API with the backend code. 3D Secure redirects and callback processes are managed. Order status updates are performed automatically.

What is DenizBank Virtual POS?

DenizBank Virtual POS is an online payment solution developed for e-commerce websites. Leveraging the technological infrastructure of DenizBank, one of Türkiye's established banks, it offers a reliable and fast payment experience.

The key features of DenizBank Virtual POS include: transaction security enhanced with 3D Secure 2.0, support for Visa, Mastercard, Troy, and American Express cards, Bonus card program advantages and points system, flexible installment options from 2 to 12 months, fast authorization and low transaction times, advanced fraud protection systems, and 24/7 technical support.

When evaluating the advantages of DenizBank POS, access to the Bonus card customer base offers significant opportunities. Customer loyalty can be increased through Bonus points integration. Special advantageous commission rates are available for SMEs. A fast application and approval process is offered. A strong digital banking infrastructure is in place.

Application Process and Required Documents

Before integrating with DenizBank Virtual POS, you need to apply for and receive approval for a POS terminal from the bank. The application process is usually completed within 5-10 business days.

The required documents for the application include a current tax certificate, a notarized signature circular, a copy of the trade registry gazette, a certificate of activity, a photocopy of the company official's ID, the website URL and content information, and DenizBank account information (an advantage for existing customers).

Application evaluation criteria include the company's operating duration and registration status, estimated monthly e-commerce turnover, sector risk assessment, website content and security compliance, and existing relationship with DenizBank.

Application channels may include DenizBank branches, the DenizBank online application portal, a business banking representative, and the DenizBank business banking hotline.

Information that will be collected after application approval includes ShopCode (Merchant Code), UserCode (User Code), UserPass (User Password), MBRP (Merchant Code), and StoreKey (3D Secure Key).

API Information Required for Integration

After receiving virtual POS approval from DenizBank, the API information provided by the bank is used for integration. This information is critical and must be stored securely.

The basic API parameters collected are ShopCode (Merchant Code), UserCode (User Code), UserPass (User Password), MBRP (Merchant Reference Number), and StoreKey (3D Secure encryption key).

This information is extremely sensitive and should absolutely not be found in frontend code. Wix Secrets Manager offers the ideal solution for securely storing such confidential information.

For API endpoint information , testsanalpos.est.com.tr is used for the test environment and sanalpos.est.com.tr for the production environment. For 3D Secure redirection, testsanalpos.est.com.tr/servlet/est3Dgate is used in the test environment and sanalpos.est.com.tr/servlet/est3Dgate is used in the production environment.

Technical Integration on Wix Velo

Integration is performed via the Velo by Wix development environment. A secure connection is established to the DenizBank API using the backend code.

The Velo installation steps are as follows: Activate Dev Mode in the Wix Editor. Create a denizbankPOS.jsw file in the backend folder. Securely store API information in the Secrets Manager. Define callback endpoints using HTTP functions.

The backend service file content includes a payment initiation function, a hash calculation function, a DenizBank API communication function, a 3D Secure callback verification function, and an order update function.

Hash calculation is a critical component of the integration. DenizBank requires a hash value to ensure transaction security. Hash calculation parameters are combined in a specific order and encrypted using the SHA-512 algorithm.

3D Secure Payment Process

3D Secure is a security protocol that provides cardholder verification for online payments. DenizBank's 3D Secure 2.0 infrastructure offers advanced security features and Bonus card integration.

The payment process works as follows: The customer clicks the payment button on the shopping cart page and enters their card information into the secure form fields. The system calculates the necessary hash values in the background. The customer is automatically redirected to the DenizBank 3D Secure page. The transaction is verified with an SMS code or DenizBank Mobile confirmation. After successful verification, the bank POSTs the transaction result to the callback URL. The backend parses the incoming data and performs hash verification. The authorization process is completed, and the order is changed to confirmed status. The customer is redirected to the successful payment page.

3D Secure response parameters are evaluated as follows: The Response value can be Approved or Declined. A ProcReturnCode value of 00 indicates a successful transaction. AuthCode is the authorization code for successful transactions. TransId is the transaction reference number. ErrMsg is a descriptive message in case of an error.

Installment Payment Options and Bonus Advantages

DenizBank Virtual POS offers comprehensive installment options and Bonus card program advantages. Special campaigns for Bonus cardholders increase conversion rates.

Installment parameters : The Installment parameter specifies the number of installments. For single payments, this value is left blank or entered as 1. For installment transactions, the values 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12 are used.

Bonus card advantages include special installment payment options for Bonus cardholders. Bonus points can be earned and spent. Special campaigns are available with Bonus Flash. It is compatible with Axess, Maximum, and Cardfinans cards.

BIN-based campaign inquiry allows you to search for available campaigns and installment options using the first 6 digits of your card number. This search enables you to view personalized offers.

Error Management and Error Codes

Comprehensive error management is critical in payment integrations. Technical details should be logged while displaying clear messages to the user.

Common DenizBank error codes and their explanations are as follows: Code 00 indicates a successful transaction, code 01 requires contacting the card-issuing bank, code 02 requires contacting the card-issuing bank, code 03 indicates an invalid merchant, code 04 indicates card confiscation, code 05 indicates an unapproved transaction, code 12 indicates an invalid transaction, code 13 indicates an invalid amount, code 14 indicates an invalid card number, code 33 indicates an expired card, code 34 indicates suspicion of fraud, code 41 indicates a lost card, code 43 indicates a stolen card, code 51 indicates insufficient balance, code 54 indicates that the card has expired, code 57 indicates an unauthorized transaction by the cardholder, and code 91 indicates that no response was received from the bank.

As a fault management strategy , user-friendly messages should be displayed, technical details should be logged, a notification system should be established for critical errors, and a retry mechanism should be implemented.

Security Measures and PCI DSS Compliance

Security is the highest priority in payment integrations. Compliance with PCI DSS standards is a legal requirement.

Basic security requirements include ensuring API information is never found in frontend code, storing all sensitive data in Secrets Manager, mandatory use of HTTPS protocol, performing hash verification on every transaction, and conducting regular security audits.

To ensure PCI DSS compliance , card information should not be stored on your servers, tokenization services should be used, vulnerability scans should be performed regularly, access logs should be maintained, and personnel should receive security training.

Testing Process and Go-Live

A comprehensive testing process is mandatory after the integration is complete. DenizBank provides separate endpoints and test cards for the test environment.

Test environment information , including the test endpoint address, is provided via testsanalpos.est.com.tr . Test card information will be sent by DenizBank after application approval.

The test scenarios should be checked as a checklist, including successful single-payment, successful installment payments (with different numbers of installments), payment with Bonus card, insufficient balance scenario, invalid card number scenario, expired card scenario, 3D Secure timeout scenario, incorrect SMS code scenario, successful full refund transaction, successful partial refund transaction, and provision cancellation transaction.

The steps for going live are as follows: All test scenarios are successfully completed. Test environment information is replaced with production information. Endpoint URLs are updated with production URLs. The first real transaction is tested with a low amount. The transaction is verified from both the Wix panel and the DenizBank POS panel.

Return and Cancellation Procedures

Post-sales return and pre-authorization cancellation processes can be performed both manually and automatically.

Refund types include full refund (full transaction amount), partial refund (part of the transaction amount), and authorization cancellation (same day, before the end of the day).

For automatic refund integration , DenizBank's refund API is used. The call is made using the original transaction reference number (TransId). The refund amount and currency are specified. Refunds are usually reflected in the cardholder's account within 1-3 business days.

Reporting and Reconciliation

Following a successful integration, payment transactions can be monitored from both the Wix and DenizBank panels. This two-way verification simplifies the reconciliation process.

On the Wix side, orders are tracked and payment statuses are viewed via the Wix Stores Dashboard. Wix Analytics can be used for custom reporting.

Within the monitoring section of the DenizBank POS panel , daily transaction summaries, installment distribution reports, card type-based analysis, Bonus points transaction reports, refund and cancellation reports, reconciliation reports, and commission detail reports can be viewed.

DenizBank Virtual POS can be successfully added to Wix, and the integration is performed via the Velo by Wix development environment. This feature makes the Wix platform much more preferable, especially for businesses working with DenizBank. The bonus card ecosystem, competitive commission rates, and robust technological infrastructure provide significant advantages to businesses. Once the integration is complete, the business owner can monitor all payment processes from both the Wix panel and the DenizBank POS screen. Due to technical complexity and security requirements, it is recommended that this integration be performed by an experienced developer.

For DenizBank Virtual POS integration and Wix e-commerce solutions, contact Blakfy: blakfy.com/iletisim