Product Updates

Charges API Deprecation and Introduction of the New Payments API

Staff

28 Jul 2024 — 2 min read

Here at 4Geeks, we're constantly striving to improve your experience and provide the most secure and efficient payment processing tools. As part of this commitment, we're announcing the deprecation of the Charges API in favor of our brand new Payments API.

This update offers several exciting benefits for you.

The Payments API offers a more streamlined and powerful way to handle your payments. It allows you to:

Create payment intents: This simplifies the payment flow by letting you define the payment details upfront, including amount, currency, and customer information.
Enhanced security with 3DS by default: The Payments API enforces 3D Secure (3DS) for all new payment intents. This industry-standard protocol adds an extra layer of security by requiring cardholder authentication during the payment process, reducing the risk of fraudulent transactions.
Improved documentation and support: We've created comprehensive documentation for the Payments API, making it easier for you to integrate it into your applications. Additionally, our new customer support packages offer dedicated assistance for any questions you may have.

Deprecation of the Charges API

The Charges API will be deprecated on July 1, 2026. This means that while it will continue to function for a limited time, we strongly recommend transitioning to the Payments API as soon as possible.

What You Need to Do:

To ensure a smooth transition, we encourage you to:

Review the Payments API documentation: Full details on using the Payments API, including code samples and integration guides, can be found here: Link to Payments API Documentation.
Start migrating your applications: Migrate your existing code using the Charges API to the Payments API. This will ensure your applications continue to function seamlessly after the deprecation date.
Reach out to our support team: Our customer support team is here to help you with any questions or concerns you may have during the migration process.

Why We're Making This Change

The Payments API represents a significant step forward for 4Geeks payment processing. It provides a more secure,streamlined, and future-proof solution for your business needs. By adopting the Payments API, you'll benefit from enhanced security, a more efficient development process, and ongoing support from 4Geeks.

We're here to help!

We understand that transitioning to a new API can take some time. Our team is committed to making this process as smooth as possible. Don't hesitate to reach out to our support team with any questions you may have. We're confident that the Payments API will become a valuable tool for your business, and we appreciate your continued partnership.

Happy Processing!

How to Build Your Own Internal Developer Platform (IDP) Using Crossplane

In the modern cloud-native landscape, the friction between operation stability and developer velocity remains a critical bottleneck. As organizations scale, the manual ticketing systems traditionally used to provision infrastructure become unsustainable. The solution lies in platform engineering: building an Internal Developer Platform (IDP) that enables self-service capabilities without sacrificing governance

Orchestrating State: Building and Deploying Stateful Applications on Kubernetes with Operators

While Kubernetes excels at managing stateless microservices via standard Deployments and ReplicaSets, managing stateful applications—such as databases, message queues, and distributed caches—introduces significant complexity. These applications require stable network identities, persistent storage, and ordered deployment and termination. To solve this in an automated, scalable manner, high-performing engineering teams

Automating Cloud Security Remediation with Policy-as-Code: A Blueprint for CTOs

In the modern cloud-native era, manual security reviews are a bottleneck that stifles velocity. As infrastructure scales, the "click-ops" approach to security management becomes untenable. For Chief Technology Officers and Senior Engineers, the transition to Policy-as-Code (PaC) is not merely a compliance exercise; it is an architectural imperative.

Deconstructing the Monolith: Implementing the Strangler Fig Pattern for High-Availability Migrations

Modernizing legacy systems is rarely a "rip-and-replace" operation. For Chief Technology Officers and Senior Architects, the risk of downtime, data inconsistency, and operational paralysis makes big-bang rewrites a non-starter. The Strangler Fig Pattern, named after the biological behavior of fig trees that grow around a host tree until