NetValve Documentation
NetValve is a payment gateway that lets you accept credit card payments, manage subscriptions, and process refunds through a single integration. We handle the complexity of processor connectivity, 3D Secure authentication, and PCI-compliant card storage so you can focus on your product.
This documentation covers everything you need to integrate NetValve into your application — from accepting your first payment to managing recurring billing.
Start with the Quick Start guide to make your first test transaction, then come back here to choose the integration path that fits your needs.
Choose Your Integration Path
NetValve offers several ways to accept payments. The right choice depends on your platform, your PCI compliance requirements, and how much control you need over the checkout experience.
Hosted Payment Page (HPP)
Best for: Merchants who want to start accepting payments quickly with minimal development effort.
NetValve hosts the entire payment form for you. Your site redirects the customer to our payment page (or loads it in an iframe), we collect card details, process the payment, and redirect the customer back to your site with the result.
- No card data touches your servers — simplest PCI compliance path
- Supports credit cards, Apple Pay, and Google Pay
- Customizable styling via CSS overrides
- Available as a full-page redirect or embedded iframe (
slim_mode)
Payment API with Token Fields
Best for: Merchants who want a custom checkout experience while keeping card data off their servers.
You build your own payment form using NetValve Token Fields — secure iframe-based input fields that embed directly into your page. The fields collect and tokenize card data client-side, giving you a payment token that your server sends to the NetValve Sale API.
This gives you full control over the look and feel of your checkout while maintaining PCI compliance.
- Card fields render as iframes within your page — sensitive data never hits your server
- Full CSS customization to match your branding
- JavaScript SDK with events, validation callbacks, and form control
- Combine with 3D Secure for SCA compliance
- Supports token storage for returning customers and recurring payments
Payment API (Direct)
Best for: PCI Level 1 certified merchants who handle card data server-side.
If your infrastructure is already PCI DSS certified to handle raw card numbers, you can call the NetValve Payment API directly with card details in the request body. This gives you maximum flexibility and control over the entire payment flow.
- Full access to all transaction types: Sale, Auth, Capture, Refund, Void
- Token creation for card-on-file and recurring billing
- 3D Secure integration via standalone APIs
- Smart Routing across multiple processors
- Webhook notifications for async transaction events
API Integration Guide → | API Reference →
WooCommerce Plugin
Best for: WordPress merchants running WooCommerce.
Install our plugin to add NetValve as a payment method in your WooCommerce store. The plugin uses Token Fields under the hood for PCI-compliant card collection and supports Apple Pay, Google Pay, 3D Secure, and WooCommerce Subscriptions out of the box.
- One-click install via WordPress plugin upload
- Supports credit cards, Apple Pay, and Google Pay
- WooCommerce Subscriptions compatible
- 3D Secure enabled
Common Guides
Once you've chosen your integration path, these guides apply across all methods:
- API Authentication — Setting up your API credentials
- Environments — Sandbox and production URLs, merchant identifiers
- Test Cards — Card numbers for sandbox testing
- Error Codes — Understanding response codes and handling failures
- Webhooks — Receiving async transaction notifications
- 3D Secure — Adding cardholder authentication
- Tokens & Card Storage — Saving cards for future payments
- Recurring Payments — Subscriptions and merchant-initiated billing