GlobiancePay vs. Kadkon Limited: What to Do When Your Payment Processor Stops Withdrawals?

In the world of international business, a reliable payment gateway is the backbone of operations. However, as the recent case of Kadkon Limited shows, even established fintech names can face significant challenges. If you are experiencing GlobiancePay withdrawal problems or looking for a GlobiancePay review, this case study provides crucial insights into what happens when a platform stops processing outgoing funds.

The Timeline of the Conflict: Funds Stuck "IN_PROGRESS"

The issues for Kadkon Limited began in the summer of 2025. It wasn't just a minor delay or a routine AML check; instead, multiple high-value transactions began hanging indefinitely in the IN_PROGRESS status.

According to reports, individual stuck withdrawals amounted to tens of thousands of dollars, with one specific transaction reaching $164,000. Despite the funds remaining "active" in the interface, they were never credited to the recipient and were not returned to the sender’s balance.

A One-Way Street: Deposits Work, Withdrawals Don't

One of the most concerning aspects of this situation is the selective functionality of the platform. While Kadkon Limited found it impossible to withdraw their capital, other parts of the GlobiancePay ecosystem continued to operate normally:

• Incoming payments were processed and credited without issues.
• Internal balances updated correctly.
• Monthly service fees were automatically deducted from the account and marked as "COMPLETED".

This creates a scenario where the payment processor remains functional only for accepting money and collecting fees, while the essential function of moving funds out of the system remains blocked.

Technical Red Flags: The v3.globiance Connection

During their investigation, Kadkon Limited discovered a technical overlap within the Globiance infrastructure. They found that their login credentials for GlobiancePay also worked on v3.globiance.com, a domain positioned as a cryptocurrency product.

The account data, transaction history, and interface were identical across both domains. This suggests that GlobiancePay and the crypto-focused v3 site share the same internal accounting system and infrastructure. This is particularly noteworthy because Kadkon Limited never invested in or intended to use cryptocurrency assets.

Communication Breakdown with Support

Despite GlobiancePay's public image—boasting a global team of over 150 employees and a visible management presence on LinkedIn—Kadkon was unable to get a concrete response.

Support interactions followed a frustrating pattern:

1. Silence or generic replies: Initial tickets received no specific information regarding the status or resolution time.
2. Unfulfilled promises: Technical representatives on LinkedIn and Telegram acknowledged the issue and promised to escalate it, but no progress followed.
3. Indefinite waiting: To this day, the status of the funds remains unchanged.

Conclusion: A Warning for Fintech Users

Kadkon Limited emphasizes that they are not making a formal legal claim of fraud, as they do not yet have court rulings or regulatory findings. However, their goal is to share this "anti-case" to warn other businesses.

If your international transactions are stuck or your payment provider stops responding, the Kadkon experience suggests that public pressure and documenting the timeline are essential first steps. As of now, the funds remain unrecovered.                

---

Date of Incident	Affected Company	Service Provider	Transaction Status	Total Amount Involved (USD)	Issue Description	Support Response Status	Reported Domain Discrepancies	Source
Summer 2024	Kadkon Limited	GlobiancePay	IN_PROGRESS	$164,000	Withdrawals blocked and hanging in progress for weeks/months, while incoming payments and service fees (marked as COMPLETED) continue to process normally.	Official support provided no concrete answers or timelines. LinkedIn and Telegram contacts acknowledged the issue but offered no resolution or specific dates.	Kadkon's credentials worked on v3.globiance.com (a crypto domain) showing an identical interface and transaction history despite the company never investing in crypto.

Operational Risk Analysis: Indicators of Systemic Failure in International Payment Services

Case Study: The GlobiancePay and Kadkon Limited Conflict

1. Strategic Context: The Vulnerability of International Capital Mobility

In the contemporary landscape of global finance, the reliability of a payment intermediary is a critical pillar of institutional stability. For international firms, these service providers are not merely vendors but essential gateways for corporate liquidity. When an intermediary counterparty experiences an operational failure, the result is not just a delay—it is a strategic paralysis that traps working capital and disrupts entire supply chains.

The conflict between Kadkon Limited and GlobiancePay serves as a quintessential case study in the sudden emergence of counterparty risk. This report deconstructs the specific technical and operational anomalies observed in this case to provide CFOs and Risk Committees with a forensic framework for identifying systemic failure. By transforming these specific incidents into a broader risk-assessment model, organizations can recognize the early warning signs of a provider’s "systemic stall" before a total loss of access occurs. The first step in mitigating this risk is identifying the subtle technical symptoms of service degradation.

2. Deconstructing the "In-Progress" Trap: Symptoms of Systemic Withdrawal Failure

Real-time transaction transparency is the bedrock of corporate trust. When a provider’s interface shifts into a state of "operational purgatory"—where transactions remain in an indefinite, un-executable status—it is rarely a localized technical glitch. For a risk manager, these frozen statuses are primary indicators of technical insolvency or what we term Predatory Liquidity Management: a state where a provider halts outflows to maintain its own liquidity ratios while continuing to ingest client deposits.

Technical Breakdown of the GlobiancePay Anomaly

Between July and September 2025, Kadkon Limited observed a definitive failure in the withdrawal architecture of GlobiancePay. The system transitioned into a state of operational paralysis characterized by:

• The "IN_PROGRESS" Stagnation: Multiple outgoing transfers, including a single significant transaction of $164,000, remained stuck in IN_PROGRESS status for months.
• The Compliance Silence (Critical Red Flag): In a standard operational delay, funds are held pending AML (Anti-Money Laundering) or KYC (Know Your Customer) documentation. Critically, in the GlobiancePay case, no AML requests or verification inquiries were ever issued. The absence of regulatory-driven inquiries during an operational stall is a definitive indicator that the delay is systemic or liquidity-based rather than compliance-related.
• The Anomaly of Non-Rejection: These transactions were neither executed, rejected, nor returned to the client's balance. By maintaining a status of "active but un-executed," the provider traps capital in a state of unrealized liquidity, preventing the client from reallocating the funds or pursuing immediate legal reclamation.

Operational Asymmetry Analysis

A forensic review reveals a sharp contrast between modules that generate revenue and those that fulfill obligations.

Module Type	Operational Scope	System Status	Forensic Risk Metric
Inbound Payments	Receiving external capital	Fully Functional	Sustains provider liquidity.
Fee Collection	Monthly maintenance/service charges	COMPLETED	Prioritizes provider revenue over client service.
Outbound Withdrawals	Fulfilling client fiduciary obligations	Systemic Stall	Indicates potential insolvency or capital entrapment.

Technological opacity in the user interface is frequently the first outward expression of a deeper infrastructure collapse.

3. Infrastructure Anomalies: The Risk of Shared Backend Systems

In institutional fintech, "Product Segregation" is a fundamental requirement for risk mitigation. Professional standards dictate that regulated payment processing must remain architecturally distinct from speculative activities, such as cryptocurrency exchanges. The discovery of shared infrastructures is a critical signal of potential fund commingling.

Anatomy of the Cross-Domain Vulnerability

During the conflict, Kadkon Limited discovered that their corporate payment credentials provided unauthorized access to v3.globiance.com, a domain dedicated to cryptocurrency products—a sector in which Kadkon had no involvement. The implications of these "Universal Credentials" are a primary risk factor:

1. Corporate Veil Piercing & Asset commingling: The use of identical login data and transaction histories across different product "wrappers" (Payment vs. Crypto) suggests a shared backend. In an insolvency event, this lack of segregation makes it nearly impossible to identify the "debtor of record," complicating asset recovery and inviting the risk of funds being used to cover losses in the provider’s speculative crypto arms.
2. Lack of Institutional-Grade Fiduciary Guardrails: Shared architectures indicate that the provider may be treating all client funds as a single, homogenous liquidity pool rather than maintaining the strict legal and technical silos required for international financial services.

Technological opacity of this nature is almost universally accompanied by a strategic withdrawal from professional accountability.

4. The Communication Breakdown Model: Support as a Reliability Indicator

In high-stakes financial partnerships, responsiveness is a proxy for solvency and professional integrity. We define the shift from transparency to silence as Communication Insolvency.

The "Support Vacuum" Framework

The Kadkon case highlights a three-stage model of communication failure that serves as a lead indicator of imminent service halt:

1. Stage 1: Substantive Evasion: Support tickets are met with generic, non-substantive replies that fail to address the specific "why" of the stalled funds or the lack of AML/KYC requests.
2. Stage 2: Soft Assurances via Non-Official Channels: Direct outreach to technical representatives on LinkedIn or Telegram results in empty promises (e.g., "passed to the responsible party"). These are stalling tactics intended to provide a false sense of progress.
3. Stage 3: The Deadline Absence: The most critical red flag is the refusal to provide a verifiable execution date. "Promises without dates" are the final indicator that a provider has lost the ability or intent to meet its obligations.

Public Persona vs. Operational Reality

The disconnect between Globiance’s public footprint—boasting 150+ employees and a global management structure—and its inability to resolve a single transaction is a significant warning. A large public footprint often provides a false sense of security; however, if an organization of that scale cannot provide a technical explanation for a months-long stall, the failure is systemic, not administrative.

5. Framework for Assessing Untrustworthy Financial Partners

Risk Managers must adopt a structured, evidence-based model to evaluate the ongoing viability of their payment lanes.

Prioritized Indicators of Non-Reliability

• Selective Operationality: The system remains "open" for incoming deposits and fee deductions while "closing" for outgoing withdrawals.
• Status Stagnation (Operational Purgatory): Transactions remain in IN_PROGRESS or "Processing" states with no option for user-initiated cancellation.
• Infrastructure Leakage: Corporate credentials grant access to unrelated, high-risk product domains (e.g., crypto backends).
• Regulatory Silence: Stalls occur without any associated AML, KYC, or compliance-driven data requests.

Risk Manager’s Support Evaluation Checklist

• [ ] Specificity of Explanation: Does the provider cite a specific technical or regulatory reason for the delay?
• [ ] Verifiable Deadlines: Has the provider committed to a hard date for fund release?
• [ ] Regulatory Transparency: Has the support team referred to a specific regulatory hold, or have they remained silent on compliance? (Silence is a red flag).
• [ ] Transactional Autonomy: Does the client retain the ability to cancel a stalled transaction and return funds to the internal balance?

6. Conclusion: Strategic Takeaways for Risk Management

The conflict between GlobiancePay and Kadkon Limited underscores that international payment services require constant, proactive monitoring that extends far beyond initial due diligence. A "systemic stall" is often the quiet precursor to a total functional blackout.

Final Directives for CFOs

1. Audit Technical Boundaries: Demand transparency regarding backend segregation. Shared credentials with speculative products represent an unacceptable risk of asset commingling.
2. Identify Predatory Liquidity Management: If a provider continues to deduct service fees while halting outbound obligations, it is no longer a partner; it is a liability. Cease all inbound transfers immediately upon the first instance of a "non-compliance" stall.
3. Benchmark Communication Clarity: Treat "promises without dates" as a signal of imminent counterparty insolvency.

Immediate diversification of payment lanes is the only effective defense against the "In-Progress" trap. When a provider enters a systemic stall, the window for capital recovery is narrow; recognizing these forensic indicators early is the difference between a minor operational delay and a total strategic liquidity crisis.