A payout was deposited on March 15, 2026 — PayPal only. CC withholding continues

Payments + Shipping & Fulfilment
1

Store: 47077a.myshopify.com
Ticket: 63238430

I am posting this because my active support ticket has gone unanswered since Tuesday despite a formal response deadline, and I need visibility from someone with authority to resolve this.

THE ISSUE

Shopify Payments has withheld all credit card payouts since December 23, 2025. PayPal settlements have continued to process normally throughout this period. As of March 19, 2026, the total withheld CC balance is $7,584.92.

The explanation I was given is that my available balance is negative. My own transaction data — exported directly from my Shopify admin — contradicts this. A day-by-day simulation of my running available balance shows it has been consistently positive throughout the entire withholding period.

WHAT SHOPIFY’S OWN ADVISOR DOCUMENTED

In a prior ticket (63073907), Shopify advisor Ricky Salac reviewed the account and documented in writing that the issue appeared to be a “technical desynchronization on the backend.” No fix was applied. The withholding has continued.

In a separate instance, Shopify’s system generated a written confirmation that a specific amount from Order #11573 would be added to the March 16, 2026 payout. That payout occurred. The promised amount was not included.

CURRENT STATUS

I submitted a detailed, evidence-based message to ticket 63238430 on Tuesday, March 17, requesting either a data-based explanation that reconciles with my exported transaction data, or immediate release of the withheld balance by end of business March 19. The assigned advisor, Mercedes, has not responded.

A payout was deposited on March 15, 2026 — PayPal only. CC withholding continues.

WHAT I AM ASKING FOR

I am not asking for a workaround or a generic response. I am asking for:

  1. A data-based explanation of why CC payouts are being withheld that reconciles with my exported transaction data showing a positive available balance throughout the withholding period.
  2. OR immediate release of the $7,584.92 in withheld CC charges.

If a Shopify staff member or someone with escalation authority can engage on this thread or through ticket 63238430, I am ready to provide full transaction documentation.

Rick Wallace
Angler’s Pro Tackle & Outdoors

1 Like
2

Hi Rick,

That’s a very detailed breakdown, and I can understand why this is frustrating — especially with that level of discrepancy between your exported data and what’s actually being paid out.

When Shopify Payments (which is built on infrastructure related to providers like Stripe) shows a negative balance while your own transaction data remains positive, it’s often because the internal “available balance” calculation includes factors that aren’t always visible in standard exports.

In cases like the one you described, the mismatch can sometimes be caused by things such as:

• rolling reserves or temporary risk holds applied to certain transactions
• delayed adjustments related to refunds, disputes, or fees not yet reflected in exports
• timing differences between authorization, capture, and settlement cycles
• or, as previously noted by support, a backend synchronization issue between ledger systems

The fact that an advisor already mentioned a “technical desynchronization” is particularly relevant — that’s not something frontline support can resolve, and it typically requires intervention from the payments engineering or risk team.

At this point, a couple of things that may help move this forward:

• ask support to explicitly confirm whether a reserve, adjustment, or hold is currently applied to your account
• request that they provide a reconciled ledger breakdown (not just standard reports) showing how the negative balance is calculated
• reference the previous ticket where the desynchronization was acknowledged, so it’s clear this isn’t a new issue
• keep communication tied to the same ticket (63238430) so the full history remains visible to whoever escalates it internally

If the issue is truly a backend desync, it usually requires a manual correction on their side rather than something that can be fixed through standard support workflows.

Hopefully someone from the payments team can take a closer look, because with the documentation you’ve provided, it definitely seems like something that should be reconcilable.