Sanval Payments – Card Gateway for Payten/NestPay Banks

Any bank running on the Payten/NestPay (Asseco SEE) platform. This plugin includes ready-made presets for Banca Intesa (Serbia), İşbank, Akbank, Ziraat, Halkbank, QNB Finansbank, AIK Banka, NLB Komercijalna banka and more, plus a Custom / Other option for every other NestPay bank (you enter the endpoint manually). All bank presets are included for everyone.

Yes. Every transaction goes through the bank’s 3D Secure page, and card data never passes through your server.

Yes. Enable Test Mode in the settings to use the Asseco sandbox. No real charges are made in test mode.

Yes. Both the classic (shortcode) checkout and the newer checkout block are supported.

This usually means your bank expects a different signature version. Open the gateway settings, go to Advanced (NestPay compatibility) , and switch the Hash Algorithm between ver3 and ver2 (many older banks use ver2), then try again.

The bank confirms a payment by sending your site a POST request to the /sanval-3ds address. Some security tools (firewalls, WAFs, or “password protect” plugins) block or strip this request. If payments authenticate at the bank but customers land back on the checkout instead of the confirmation page, add /sanval-3ds to your firewall’s allowlist and disable any “password protected site” plugin while testing.

In the gateway settings under Advanced , enable Diagnostic Logging , reproduce the issue once, then copy the text from the Diagnostics box and send it to support. It contains only the bank’s callback data (no full card number or CVV). Turn the logging off again afterwards.

The currency must match your virtual POS agreement. Turkish banks typically require TRY (949) and Serbian banks RSD (941). EUR (978) and USD (840) work if your bank contract allows them.