Cardknox review

Cardknox is a payment-processing service presented on its homepage through the Sola brand. Sola covers merchant payments across online, in-person and omnichannel sales, as well as payment monetization for platforms. In a software stack, it sits outside your application as the payment provider you integrate with to accept and manage transactions; it is not presented as a self-hosted payment server or a standalone developer tool.

The homepage describes tools, plugins and APIs, but does not define a specific API architecture. Treat it as a vendor-managed payment integration until Cardknox confirms the deployment and transaction flow for your account. Its stated support scope includes customer-service questions such as chargebacks and deposits, gateway settings and transaction issues, technical configuration for card readers and payment software, and developer help from presales through post-implementation. That support breadth may suit teams connecting payment processing to merchant software, but the exact integration and processing responsibilities need to be agreed with the vendor.

Cardknox’s homepage says its developer team helps integrate its tools, plugins and APIs into customer solutions, including presales and post-implementation support. It does not describe API style, request or response formats, authentication, webhooks, a CLI, named SDKs, or supported programming languages. Treat the documented integration surface as APIs, tools and plugins, and confirm API protocol, SDK and language support in the vendor’s docs before choosing a stack.

The support offer is relevant if your team needs help with implementation or troubleshooting, but it is not a substitute for checking the technical reference. Ask for current API documentation, integration examples, test credentials, supported payment flows, error handling guidance, and versioning or deprecation policies. For an existing product, confirm which plugins are maintained and whether they cover your framework and deployment model. The homepage also describes technical help for card readers and payment software, which may matter when the integration spans software and in-person terminals.

Cardknox pricing is custom and quote-based. The pricing information lists a Custom plan for businesses seeking a quote, but no monthly or annual price, starting price, free tier, or free trial. There is no published price to use for a budget estimate, so ask for a written quote based on your payment volume, channels, and integration requirements.

The available pricing information does not give transaction rates, monthly minimums, per-request charges, volume discounts, overage rules, or add-on prices. It also does not explain whether the quote changes with platform use, merchant accounts, terminals, support needs, or payment methods. Do not assume that a custom quote means a flat fee or that processing charges are included. Before signing, request a full schedule covering transaction fees, recurring charges, chargebacks, hardware, implementation, and any termination or migration costs. Without those terms, developers cannot estimate how the bill will change as transaction volume or the number of merchants grows.

Cardknox’s homepage does not publish a software licence or describe its payment tools as open source. It presents Sola as a payment solution and promotes integration support, but does not explain whether any component can run on your infrastructure. Confirm licensing and hosting options with the vendor before treating the service as hosted-only or planning a self-managed deployment.

The homepage also does not describe data export formats, access to transaction records after termination, or migration support. Payment integrations can create switching work in application code, operational workflows and merchant onboarding, so ask how to export transaction and customer data, which records remain accessible, and what the vendor will provide when moving to another processor. Your contract should cover data ownership, retention, export fees, and the steps needed to disconnect the integration. Without those terms, the effort and cost of leaving are unclear.

Before routing production payments through Cardknox, get the operational details that the homepage does not cover: API rate limits, uptime target, incident communication, retry guidance, idempotency behavior, and support response times. The homepage advertises in-house gateway, technical and developer support, but does not publish service-level commitments or capacity limits. Ask which channels are covered outside business hours and how urgent payment outages are escalated.

Confirm the security and compliance responsibilities for your specific integration, including how card data is handled, what your application may store, and which compliance documents Cardknox can provide. The homepage’s general payment claims do not establish a compliance scope or security guarantee. For in-person deployments, verify supported card readers, software compatibility, and how terminal or network failures affect transaction handling. Also get the full pricing schedule and data-export terms in writing; custom pricing and unclear migration details can become production risks as merchant count and transaction volume grow.