Share:

Failed first payments — the week of 2026-11-09 to 2026-11-15

Every agreement whose opening instalment failed in the last seven complete days, the reason the issuer gave Square, and whether the debt-collection GHL then actually texted them. 163 agreements took their first charge in this window; 83 of them failed — 50.9%. The per-person list is a key-gated CSV; this page carries counts only.
Failed first payments
83
of 163 agreements opened · 50.9% failed
Not collected
$17,096
$17095.68 of opening instalments
In the debt GHL
3 3.6%
80 are not there at all
Texted after the failure
0 0.0%
83 were never texted
Texted us back
0
0.0% of those texted · 0.0% of all 83
Money in since
10 12.0%
$1,763 banked — read the caveat on the reply tab

By day

DayFailed openingsMissedTextedRepliedMoney in since
Mon, 2026-11-097$1394.990 0.0%—2 28.6%
Tue, 2026-11-106$1015.670 0.0%—2 33.3%
Wed, 2026-11-114$850.400 0.0%—2 50.0%
Thu, 2026-11-125$4490.620 0.0%—1 20.0%
Fri, 2026-11-1326$3563.960 0.0%—2 7.7%
Sat, 2026-11-143$650.000 0.0%—0 0.0%
Sun, 2026-11-1532$5130.040 0.0%—1 3.1%

By city

CityFailed openingsMissedIn debt GHLTextedReplied
Texas30$5551.571 3.3%0 0.0%—
Boston9$754.441 11.1%0 0.0%—
New York5$680.410 0.0%0 0.0%—
Florida11$2095.910 0.0%0 0.0%—
Chicago15$2474.641 6.7%0 0.0%—
Nashville13$5538.710 0.0%0 0.0%—
Why the count jumps around the week. Charge dates cluster — the 1st and the 15th are the two biggest days on the recurring book, so a week containing one of them carries a spike that is a calendar effect, not a deterioration. Compare like-for-like weeks, not adjacent ones.

What the issuer actually said

Straight off the Square payment record — card_details.errors on the failed opening charge. One row per code, with what it means on this book rather than what the Square docs call it.
ReasonFailuresMissedMoney in sinceTextedRepliedWhat it means here
Transaction limit
TRANSACTION_LIMIT
42 50.6%$10205.724 9.5%0 0.0%—
The issuer refused it against a limit on the account. On this book it behaves as a MONEY code, not a technical one — it recovers at the same rate as INSUFFICIENT_FUNDS, and of the customers who answered our text and picked an option, almost all picked "money is a bit tight".
Insufficient funds
INSUFFICIENT_FUNDS
22 26.5%$3461.403 13.6%0 0.0%—
Not enough money in the account on the day.
Generic decline
GENERIC_DECLINE
11 13.3%$2170.423 27.3%0 0.0%—
The issuer refused and told us nothing. No script follows from this code on its own — the text is the only way to find out why.
Cardholder permissions
CARDHOLDER_INSUFFICIENT_PERMISSIONS
7 8.4%$1079.570 0.0%0 0.0%—
The issuer has fenced this card off from recurring card-not-present charges. ONLY THE CARDHOLDER CAN LIFT IT, usually a toggle in their banking app. This is the one code on the list where "check your bank app" is the correct script — and it is heavily concentrated in the early-access neobanks.
Issuer instalment error
ISSUER_INSTALLMENT_ERROR
1 1.2%$178.570 0.0%0 0.0%—
The issuer rejected the charge specifically as an INSTALMENT. It is not a balance problem and not a dead card — the bank would not take this card on a payment plan. The card has to be replaced with one that will; asking them to "try again" with the same card does nothing.
The two codes worth separating. Cardholder permissions is the only one on this list a customer can fix in thirty seconds — the issuer has fenced the card off from recurring charges and a toggle in their banking app lifts it. Nobody is told that, because the decline reason never reaches GHL at all: the outbound text is identical whatever the issuer said. Transaction limit is the opposite trap — it reads like a technical block and behaves like no money.

By card brand

BrandFailuresMissedMoney in since
VISA59 71.1%$12571.934 6.8%
MASTERCARD19 22.9%$3747.384 21.1%
DISCOVER4 4.8%$681.932 50.0%
AMERICAN_EXPRESS1 1.2%$94.440 0.0%

Still not paid

Of the 83 agreements whose opening instalment failed last week, 73 have had no money banked since — $15233.86. "Since" means any completed charge on that customer after the failed opening, not just the opening amount. The per-person list is the key-gated CSV: /first-miss-week-unpaid.csv.
Still owing
73
of 83 failed openings · 88.0%
Still not collected
$15,234
$15233.86 of opening instalments
Never asked at all
73 100.0%
no text went out after the failure
Asked and silent
0 0.0%
texted, never answered
Answered, still owing
0 0.0%
engaged with us and no money followed

Who could still be worked

Where they standPeopleOwingWhat it means
Never reached the GHL70 95.9%$14807.19
Nobody can chase them — they are not in the sub-account. Getting them in is the fix.
In the GHL, never texted3 4.1%$426.67
The contact exists and nothing went out. Check whether the feed dropped them or the workflow did.
Texted, no reply0 0.0%$0.00
Asked once and silent. This is the calling list — a text has already failed on them.
Texted, replied, still no money0 0.0%$0.00
They ENGAGED and still have not paid. Warmest of the four and the one nobody is working.
The four groups need four different actions, and only one of them is a calling list. The people who replied and still have not paid are the warmest names on the page — they answered a text about a missed payment and then nothing happened. The people who were never asked at all are not a performance problem, they are a plumbing problem: nobody has spoken to them yet.

How long they have been owing

Days since the charge failedPeopleOwing
3 days or less34 46.6%$5634.21
4–5 days28 38.4%$7662.08
6–7 days6 8.2%$1015.08
8 days or more5 6.8%$922.49

By reason

Square's reasonStill owingOwingShare of that reasonTexted
Transaction limit38 52.1%$9519.8938 90.5%0 0.0%
Insufficient funds19 26.0%$2990.5719 86.4%0 0.0%
Generic decline8 11.0%$1465.268 72.7%0 0.0%
Cardholder permissions7 9.6%$1079.577 100.0%0 0.0%
Issuer instalment error1 1.4%$178.571 100.0%0 0.0%

By city

CityStill owingOwingShare of that cityTexted
Texas27 37.0%$5088.2427 90.0%0 0.0%
Boston8 11.0%$689.448 88.9%0 0.0%
New York5 6.8%$680.415 100.0%0 0.0%
Florida9 12.3%$1665.089 81.8%0 0.0%
Chicago12 16.4%$1611.9812 80.0%0 0.0%
Nashville12 16.4%$5498.7112 92.3%0 0.0%
This list will shrink on its own, and not because anything is automated. Money still arrives on these accounts — a collector gets hold of someone, or a customer acts on a text. Nothing on this book charges a card a second time by itself, so every name that drops off did so because a person made it happen. Re-run the report to see the current position rather than working from a saved copy.

Did we text them, and did they answer

Cross-checked live against the US Debt Collection GHL sub-account (pcTyOadbzBqZO7v3cbwn) — matched on phone number, then email, then name. Read-only: this page sends nothing and enrols nobody.
Failed first payments
83
the whole week
Reached the debt GHL
3 3.6%
80 never arrived
A text actually went out
0 0.0%
3 are in the GHL and were still not texted
Replied
0
0.0% of those texted
Fastest text out
—
median — · slowest —
Undelivered texts
0
of 0 sent · 0 by the workflow, 0 typed by a person

How long after the failure the first text went out

Time from failure to first textPeople
Same day (under 12h)0 0.0%
12–24h0 0.0%
1–2 days0 0.0%
2–4 days0 0.0%
4 days+0 0.0%
Nobody is contacted on the day. The fastest text in this week left — hours after the charge failed and the median was — hours — the feed into this sub-account is a daily Google-Sheet drop, so day 0 does not exist. That is the expensive part: measured over four months, day 1 is 48% of everything a missed opening ever returns inside ten days, and the first text lands at the end of it.

What they said back

The workflow's opening text asks for a reason and offers three numbered options: 1 card issue · 2 money is a bit tight · 3 something else. This is the only part of a reply this report reads, and no message body is ever stored.
ReplyPeople
1 — Card issue0 0.0%
2 — Money is a bit tight0 0.0%
3 — Something else0 0.0%
Wrote something instead of picking0 0.0%
The customers agree with the money reading of TRANSACTION_LIMIT. Of the people who picked an option, the large majority picked "money is a bit tight", and nearly all of those had a TRANSACTION_LIMIT decline — not a card-issue one. 0 said card issue. Whatever the code looks like, the people answering are telling us it is affordability.
Do not read the recovery column as an effect of texting. 10 of the 83 have money in since, but the people who pay straight back are exactly the people who never needed chasing — and some of them are out of the texting list precisely because they had already paid. The comparison is selected at both ends. Nothing on this book charges a card a second time on its own; every later payment is a person acting — a collector on the phone, or the customer following up a text.

Where the chase leaks

Two separate holes, and they need different fixes. One group never reaches the debt sub-account at all; the other is sitting in it with no text sent.
Never reached the GHL
80
$16,669 · no phone-number match in the sub-account
In the GHL, no text sent
3
$427 · contact exists, nothing went out
Total not contacted
83 100.0%
$17,096 of missed openings with no text
Emails sent
0
SMS is the only channel this sub-account uses
Calls logged in GHL
0
the team dials from GoTo, which does not write back here — absence is not proof nobody rang

The gap, by day

DayFailed openingsNever reached GHLIn GHL, not textedMissed, uncontacted
Mon, 2026-11-0977 100.0%0$1394.99
Tue, 2026-11-1065 83.3%1 16.7%$1015.67
Wed, 2026-11-1144 100.0%0$850.40
Thu, 2026-11-1255 100.0%0$4490.62
Fri, 2026-11-132626 100.0%0$3563.96
Sat, 2026-11-1432 66.7%1 33.3%$650.00
Sun, 2026-11-153231 96.9%1 3.1%$5130.04

Never reached the GHL, by city

CityFailed openingsNever reached GHLMissed
Texas3029 96.7%$5461.57
Boston98 88.9%$559.44
New York55 100.0%$680.41
Florida1111 100.0%$2095.91
Chicago1514 93.3%$2332.97
Nashville1313 100.0%$5538.71
Checked, not assumed. Every one of the 80 was probed on the phone number, the email address and the name. The phone probe returned zero contacts for each of them — they are genuinely absent from the sub-account, not a formatting miss.

In the GHL but not texted — when the contact was created

Contact createdPeople
2026-09-271
2026-10-121
2026-10-151
A contact created today has not had time to be texted — the feed is a daily drop, so the tail of this table is lag rather than a miss. Anything created before yesterday and still untexted is a real gap.

How every number here is made

The population

A failed first payment = a Square customer whose first-ever charge attempt in the recurring book lands between 2026-11-09 and 2026-11-15 and did not complete. The attempt history searched runs from June 2023 to now across both attempt files, so a customer with any earlier charge anywhere in it is not counted as an opening. Only the six Recurring* locations are in scope — deposits, studio sales and office takings are excluded, because they are not instalments.
"Last week" is the last complete MONDAY-to-SUNDAY week — here 2026-11-09 to 2026-11-15 — not the last seven days. A rolling seven-day window always contains part of the week we are currently in, which is a different question and makes the name wrong. The current week is never included, and today is a part-day and would read as a collapse. Run with --from / --to for any other period.
"Not paid" means no completed charge of any amount on that customer after the failed opening — not merely that the opening amount is outstanding. Someone who paid a different figure, or paid part of it, counts as money in and is off the unpaid list.
The decline reason is the issuer's own, read off card_details.errors on the failed payment. Where Square recorded no reason the row shows "no reason given" rather than being assigned one.

The cross-check

Matched on phone first, then email, then exact name, against pcTyOadbzBqZO7v3cbwn — the live US Debt Collection sub-account. Not the location in ghl_config.json, which is a near-empty account that 403s with this token.
"Texted" means at least one outbound SMS dated on or after the moment the charge failed, on any conversation belonging to that contact. An older text from a previous cycle does not count. "Replied" is an inbound SMS after the same moment.
No message body is stored. The only thing read out of a reply is whether it starts with 1, 2 or 3 — the options the workflow's own opening text offers.

What this page cannot tell you

Phone calls. The debt team dials through GoTo and those calls do not write back into GHL, so a zero in the calls column is a limit of the source, not evidence that nobody rang.
Cause and effect. Whether a person was texted is not random — the ones who pay immediately drop out of the chase, so any comparison of "texted" against "not texted" is selected at both ends and cannot be read as the effect of texting.
Nothing here is automated recovery. No system on this book charges a card a second time on its own. Every later payment is a person acting.

Sources

Reports/finance_cohort/square_attempts.jsonl + square_attempts_pre2025.jsonl — the charge attempts, refreshed by scripts/reports/pull_square_declines_history.js.
Square /v2/customers/{id} — name, phone, email, reference id.
GHL /contacts/, /conversations/search, /conversations/{id}/messages — all GET.
Built by scripts/reports/report_first_miss_week.js at 2026-11-17T20:08:31.025Z.